[CMake] CMake 3.7.1 gui fails to launch

[Daniel Schepler]

Another alternative, which is the one we use here, is to configure the custom Qt build with a "-qtlibinfix" flag - which produces libraries with completely different SONAMEs so there's no conflict.  (We use this in conjunction with an RPATH.)  One thing that could break is that some distributions set QT_PLUGIN_PATH for KDE logins which causes errors on trying to load incompatible plugins, so they might need to unset QT_PLUGIN_PATH in their wrapper script.
-- 
Daniel
________________________________________
From: CMake [cmake-bounces at cmake.org] on behalf of Hendrik Sattler [post at hendrik-sattler.de]
Sent: Saturday, January 07, 2017 12:11 AM
To: cmake at cmake.org; daryl at daryllee.com; Alan W. Irwin
Subject: Re: [CMake] CMake 3.7.1 gui fails to launch

Am 6. Januar 2017 23:37:00 MEZ schrieb daryl at daryllee.com:
>And the answer is...
>
>I recently installed an IDE from a not-to-be-named company that I do a
>
>lot of business with.  The installation of that software places their
>installation directory in LD_LIBRARY_PATH and guess what? their
>installation contains a copy of libQtGui.so and libQtCore.so.  The
>"ldd" tip led me to that discovery.  For now I have put
>/usr/lib/x86_64-linux-gnu in front of their path in LD_LIBRARY_PATH
>and cmake-gui V3.7.1 is working.  I may have to come up with a more
>permanent fix, but for now their stuff seems to work and CMake seems
>to work, so I'm claiming victory.

Maybe as a customer you should tell them about this bad experience. They should either set RPATH in their programs or should set LD_LIBRARY_PATH only in a start wrapper script.
In a program that lets the user start other programs, RPATH should be preferred or  LD_LIBRARY_PATH should be cleaned up for child processes.

HS

--
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.
--

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake