Re: [CMake] unexpected INSTALL problems

2011-06-15 Thread Michael Hertling
On 06/15/2011 09:52 PM, Dominik Szczerba wrote: >> The FILES_MATCHING option of INSTALL(DIRECTORY ...) applies to files >> only, i.e. with the above-noted line and BOOST_RUNTIME_DIR==/usr/lib, >> you'll get the *whole* directory structure under /usr/lib including >> symlinks to directories, but onl

Re: [CMake] unexpected INSTALL problems

2011-06-15 Thread Michael Hertling
On 06/15/2011 11:43 PM, Dominik Szczerba wrote: >> This behavior is really strange and I tested it in the last 10 minutes. >> CMake says: >> boost libs: /usr/lib/libboost_system-mt.so >> >> Compiling and linking with verbose reveals the link command: >> /usr/bin/c++ CMakeFiles/test.dir/test.cp

Re: [CMake] unexpected INSTALL problems

2011-06-15 Thread Dominik Szczerba
> This behavior is really strange and I tested it in the last 10 minutes. > CMake says: > boost libs: /usr/lib/libboost_system-mt.so > > Compiling and linking with verbose reveals the link command: > /usr/bin/c++      CMakeFiles/test.dir/test.cpp.o  -o test -rdynamic > -lboost_system-mt > > But a l

Re: [CMake] unexpected INSTALL problems

2011-06-15 Thread Andreas Naumann
Am 15.06.2011 22:28, schrieb Andreas Naumann: Am 15.06.2011 22:16, schrieb Dominik Szczerba: I use Debian SID 64bit which is similar to Ubuntu, but not the same :) The "problem" (if it really is one) is that debian does ship the libraries with another naming, so FindBoost will select the librar

Re: [CMake] unexpected INSTALL problems

2011-06-15 Thread Andreas Naumann
Am 15.06.2011 22:16, schrieb Dominik Szczerba: I use Debian SID 64bit which is similar to Ubuntu, but not the same :) The "problem" (if it really is one) is that debian does ship the libraries with another naming, so FindBoost will select the library without version number. That's very int

Re: [CMake] unexpected INSTALL problems

2011-06-15 Thread Dominik Szczerba
> I use Debian SID 64bit which is similar to Ubuntu, but not the same :) > The "problem" (if it really is one) is that debian does ship the libraries > with another naming, so FindBoost will select the library without version > number. That's very interesting. My Boost_LIBRARIES according to cmake

Re: [CMake] unexpected INSTALL problems

2011-06-15 Thread Andreas Naumann
Am 15.06.2011 15:12, schrieb Dominik Szczerba: On my system, FindBoost detects the *.so without the version numbers. So, I can update to a new (hopefully binary compatible) version without relinking. That would be ideal, unfortunately for me (Ubuntu 10.10 64 bit cmake 2.8.4) my stuff gets

Re: [CMake] unexpected INSTALL problems

2011-06-15 Thread Dominik Szczerba
> The FILES_MATCHING option of INSTALL(DIRECTORY ...) applies to files > only, i.e. with the above-noted line and BOOST_RUNTIME_DIR==/usr/lib, > you'll get the *whole* directory structure under /usr/lib including > symlinks to directories, but only files and symlinks to files which > match PATTERN/

Re: [CMake] unexpected INSTALL problems

2011-06-15 Thread Michael Hertling
On 06/15/2011 01:58 PM, Dominik Szczerba wrote: > I am trying to copy all libboost* stuff from /usr/lib to > CMAKE_INSTALL_PREFIX just as most users would guess: > > INSTALL(DIRECTORY ${BOOST_RUNTIME_DIR}/ DESTINATION > ${CMAKE_INSTALL_PREFIX}/bin FILES_MATCHING ...) > > Whatever I specify fo

Re: [CMake] unexpected INSTALL problems

2011-06-15 Thread Dominik Szczerba
> On my system, FindBoost detects the *.so without the version numbers. So, I > can update to a new (hopefully binary compatible) version without relinking. That would be ideal, unfortunately for me (Ubuntu 10.10 64 bit cmake 2.8.4) my stuff gets linked to the full name, not the symbolic link. If

Re: [CMake] unexpected INSTALL problems

2011-06-15 Thread Andreas Naumann
Am 15.06.2011 14:58, schrieb Dominik Szczerba: okay, than you could use find_package(Boost YOUR_VERSION EXACT) Problem is boost has very complicated linking scenario. Using FindBoost and linking to it hardcodes the versions, because they are in the filenames! If I need to run on another sy

Re: [CMake] unexpected INSTALL problems

2011-06-15 Thread Dominik Szczerba
> okay, than you could use > find_package(Boost YOUR_VERSION EXACT) Problem is boost has very complicated linking scenario. Using FindBoost and linking to it hardcodes the versions, because they are in the filenames! If I need to run on another system I must have exactly the same boost version, bu

Re: [CMake] unexpected INSTALL problems

2011-06-15 Thread Andreas Naumann
Am 15.06.2011 14:24, schrieb Dominik Szczerba: On Wed, Jun 15, 2011 at 2:22 PM, Andreas Naumann wrote: Am 15.06.2011 13:58, schrieb Dominik Szczerba: I am trying to copy all libboost* stuff from /usr/lib to CMAKE_INSTALL_PREFIX just as most users would guess: Why do you w

Re: [CMake] unexpected INSTALL problems

2011-06-15 Thread Dominik Szczerba
On Wed, Jun 15, 2011 at 2:22 PM, Andreas Naumann wrote: > Am 15.06.2011 13:58, schrieb Dominik Szczerba: >> >> I am trying to copy all libboost* stuff from /usr/lib to >> CMAKE_INSTALL_PREFIX just as most users would guess: >> >> > > Why do you want to copy the boost libraries from /usr/lib to > C

Re: [CMake] unexpected INSTALL problems

2011-06-15 Thread Andreas Naumann
Am 15.06.2011 13:58, schrieb Dominik Szczerba: I am trying to copy all libboost* stuff from /usr/lib to CMAKE_INSTALL_PREFIX just as most users would guess: Why do you want to copy the boost libraries from /usr/lib to CMAKE_INSTALL_PREFIX? And why all of them?? I don't see any reason for t

[CMake] unexpected INSTALL problems

2011-06-15 Thread Dominik Szczerba
I am trying to copy all libboost* stuff from /usr/lib to CMAKE_INSTALL_PREFIX just as most users would guess: INSTALL(DIRECTORY ${BOOST_RUNTIME_DIR}/ DESTINATION ${CMAKE_INSTALL_PREFIX}/bin FILES_MATCHING ...) Whatever I specify for matching I always get half of my system copied instead of th