Re: [CMake] new RPATH support questions

2006-03-07 Thread Brad King
Alexander Neundorf wrote: Von: Brad King <[EMAIL PROTECTED]> CMake is providing an interface to get whatever RPATHs you want into the installed binary. It is is up to a project's code to produce the proper path for its distribution. Only the project authors know how the binaries will finally

Re: [CMake] new RPATH support questions

2006-03-07 Thread Alexander Neundorf
> Von: Brad King <[EMAIL PROTECTED]> ... > CMake has no way to know what the proper RPATH is for external > libraries > in the installed binaries. Again, take my example of using a separate > Qt build tree. KDE would build and install with an rpath pointing at > the Qt build tree instead

Re: [CMake] new RPATH support questions

2006-03-07 Thread Brad King
Alexander Neundorf wrote: Hi, Von: Brad King <[EMAIL PROTECTED]> Alexander Neundorf wrote: Ok, I tested now the following: set(CMAKE_BUILD_WITH_INSTALL_RPATH TRUE) set(CMAKE_SKIP_BUILD_RPATH TRUE) set(CMAKE_INSTALL_RPATH ${LIBRARY_OUTPUT_PATH}/${CMAKE_CFG_INTDIR}/

Re: [CMake] new RPATH support questions

2006-03-07 Thread Alexander Neundorf
Hi, > Von: Brad King <[EMAIL PROTECTED]> > > Alexander Neundorf wrote: > > Ok, I tested now the following: > > > > set(CMAKE_BUILD_WITH_INSTALL_RPATH TRUE) > > set(CMAKE_SKIP_BUILD_RPATH TRUE) > > > > set(CMAKE_INSTALL_RPATH ${LIBRARY_OUTPUT_PATH}/${CMAKE_CFG_INTDIR}/ > >

Re: [CMake] new RPATH support questions

2006-03-07 Thread Brad King
Alexander Neundorf wrote: Ok, I tested now the following: set(CMAKE_BUILD_WITH_INSTALL_RPATH TRUE) set(CMAKE_SKIP_BUILD_RPATH TRUE) set(CMAKE_INSTALL_RPATH ${LIBRARY_OUTPUT_PATH}/${CMAKE_CFG_INTDIR}/ ${CMAKE_INSTALL_PREFIX}/${LIB_INSTALL_DIR}) Which gives CMAK

Re: [CMake] new RPATH support questions

2006-03-06 Thread Alexander Neundorf
Hi, > Von: Brad King <[EMAIL PROTECTED]> > > Alexander Neundorf wrote: > > I just updated from current cvs. > > > > CMakeLists.txt: > > > > add_library(foo SHARED foo.c) > > > > add_executable(footest main.c) > > > > target_link_libraries(footest foor) > >

Re: [CMake] new RPATH support questions

2006-03-06 Thread Brad King
Alexander Neundorf wrote: I just updated from current cvs. CMakeLists.txt: add_library(foo SHARED foo.c) add_executable(footest main.c) target_link_libraries(footest foor) install_targets(/bin footest) install_targets(/lib foo) This has the effect, that footest is i

Re: [CMake] new RPATH support questions

2006-03-06 Thread William A. Hoffman
At 02:16 PM 3/6/2006, Alexander Neundorf wrote: >Hi, > >I just updated from current cvs. > >CMakeLists.txt: > >add_library(foo SHARED foo.c) > >add_executable(footest main.c) > >target_link_libraries(footest foor) > >install_targets(/bin footest) >install_targets(/lib foo)

[CMake] new RPATH support questions

2006-03-06 Thread Alexander Neundorf
Hi, I just updated from current cvs. CMakeLists.txt: add_library(foo SHARED foo.c) add_executable(footest main.c) target_link_libraries(footest foor) install_targets(/bin footest) install_targets(/lib foo) This has the effect, that footest is initially linked wi