The wiki states that arts and tdelibs require the following:
DCMAKE_SKIP_RPATH=ON
That implies all otehr cmake packages can be/should be set to DCMAKE_SKIP_RPATH=OFF.
With DCMAKE_SKIP_RPATH=OFF tdebase will not build. I receive the following errors:
libtdeinit_kicker.so: undefined reference to `KonqBookmarkManager::s_bookmarkManager' libtdeinit_kicker.so: undefined reference to `KickoffSearch::KickoffSearchInterface::tqt_emit(int, TQUObject*)' libtdeinit_kicker.so: undefined reference to `KickoffSearch::KickoffSearchInterface::tqt_property(int, int, TQVariant*)' libtdeinit_kicker.so: undefined reference to `typeinfo for KickoffSearch::Plugin' libtdeinit_kicker.so: undefined reference to `typeinfo for KickoffSearch::KickoffSearchInterface' libtdeinit_kicker.so: undefined reference to `KickoffSearch::KickoffSearchInterface::KickoffSearchInterface(TQObject*, char const*)' libtdeinit_kicker.so: undefined reference to `KickoffSearch::KickoffSearchInterface::tqt_cast(char const*)' libtdeinit_kicker.so: undefined reference to `KickoffSearch::KickoffSearchInterface::staticMetaObject()' libtdeinit_kicker.so: undefined reference to `KonqPopupMenu::KonqPopupMenu(KBookmarkManager*, TQPtrList<KFileItem> const&, KURL const&, KActionCollection&, KNewMenu*, TQWidget*, unsigned int, unsigned int)' libtdeinit_kicker.so: undefined reference to `KickoffSearch::Plugin::staticMetaObject()' libtdeinit_kicker.so: undefined reference to `vtable for KickoffSearch::KickoffSearchInterface' libtdeinit_kicker.so: undefined reference to `KonqOperations::doDrop(KFileItem const*, KURL const&, TQDropEvent*, TQWidget*)' libtdeinit_kicker.so: undefined reference to `KickoffSearch::KickoffSearchInterface::tqt_invoke(int, TQUObject*)'
Does tdebase require DCMAKE_SKIP_RPATH=ON like arts and tdelibs? Or are these errors indicating a different build bug? Am I doing something wrong?
Darrell
Does tdebase require DCMAKE_SKIP_RPATH=ON like arts and tdelibs? Or are these errors indicating a different build bug? Am I doing something wrong?
I get tdebase to build with DCMAKE_SKIP_RPATH=OFF or not using DCMAKE_SKIP_RPATH at all. Which is best? Explicit declaration or none?
Darrell
On Thursday 18 of October 2012 03:43:42 Darrell Anderson wrote:
Does tdebase require DCMAKE_SKIP_RPATH=ON like arts and tdelibs? Or are these errors indicating a different build bug? Am I doing something wrong?
I get tdebase to build with DCMAKE_SKIP_RPATH=OFF or not using DCMAKE_SKIP_RPATH at all. Which is best? Explicit declaration or none?
Darrell
For Debian / Ubuntu packages is used -DCMAKE_SKIP_RPATH="OFF". But I do not know what is the better :)
Slavek --
For Debian / Ubuntu packages is used -DCMAKE_SKIP_RPATH="OFF". But I do not know what is the better :)
Have you ever tried using DCMAKE_SKIP_RPATH="ON" or deleting the option entirely?
If DCMAKE_SKIP_RPATH= is not listed in the configuration does that mean cmake defaults to DCMAKE_SKIP_RPATH="ON" or DCMAKE_SKIP_RPATH="OFF"?
I have no qualms with using DCMAKE_SKIP_RPATH="OFF", but we should update the wiki if tdebase needs to be built that way.
Darrell
Hello,
On Thursday 18 October 2012, Darrell Anderson wrote:
For Debian / Ubuntu packages is used -DCMAKE_SKIP_RPATH="OFF". But I do not know what is the better :)
Have you ever tried using DCMAKE_SKIP_RPATH="ON" or deleting the option entirely?
CMAKE_SKIP_RPATH="ON" means according to the cmake doc, that all rpath-related options given to cmake are ignored. This means that no rpath is set at all - neither at build nor at install time (see http://www.cmake.org/Wiki/CMake_RPATH_handling)
CMAKE_SKIP_RPATH="OFF" (or not set) means that the rpath-related options given to cmake are used.
When no (other) rpath-options are given, cmakes default is used. This means that cmake adds an rpath during build time (so compiled binaries in the build tree may be called and will work) and removes it at install, so the installed libraries and binaries are without an rpath.
If DCMAKE_SKIP_RPATH= is not listed in the configuration does that mean cmake defaults to DCMAKE_SKIP_RPATH="ON" or DCMAKE_SKIP_RPATH="OFF"?
I have no qualms with using DCMAKE_SKIP_RPATH="OFF", but we should update the wiki if tdebase needs to be built that way.
I do not know why the wiki proposes to use CMAKE_SKIP_RPATH - maybe the author can explain. There may be reasons, setting the rpath has problems in different scenarios and is not always a good idea.
IMHO in most cases it is best to set the rpath at both build and install time and I use CMAKE_INSTALL_RPATH to set the install rpath explicitely to the selected install-lib-dir and the install-qt-lib-dir and this works.
Ulrich
Darrell
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
-
Darrell Anderson -
Slávek Banko -
Ulrich Gemkow