[CMake] Creating links / Uninstalling links

Hi all, what's the the correct way to do the following: 1) Compile and install a binary foo to /usr/bin/foo 2) Create a link /usr/bin/bar -> /usr/bin/foo 3) On "make uninstall" remove /usr/bin/foo and /usr/bin/bar For 1+2, I used SET_TARGET_PROPERTIES(foo PROPERTIES POST_INSTALL_SCRIPT make_link

Re: [CMake] creating a shared and static library of the same name

On 5/15/06, Xavier Delannoy <[EMAIL PROTECTED]> wrote: it's possible with CMake greater to 2.3.4. I used two diferent destination directories for the static and shared libs. Thanks Xavier for this detailed (and lengthy) instructions. But they are way too complicated and cumbersome imho. Under

Re: [CMake] creating a shared and static library of the same name

On 5/15/06, William A. Hoffman <[EMAIL PROTECTED]> wrote: At 06:43 AM 5/15/2006, Michael Biebl wrote: >Hi everybody, > >is it possible to create a shared and static library with the same name? >I tried the folllowing: > >ADD_LIBRARY(foo SHARED foo.c) > >ADD_L

[CMake] creating a shared and static library of the same name

Hi everybody, is it possible to create a shared and static library with the same name? I tried the folllowing: ADD_LIBRARY(foo SHARED foo.c) ADD_LIBRARY(foo_static STATIC foo.c) SET_TARGET_PROPERTIES(foo_static PROPERTIES OUTPUT_NAME foo) But if I then add ADD_EXECUTABLE(bar bar.c) TARGET_LIN

[CMake] test files generated by CheckIncludeFile are not ansi conform

The template files for CheckIncludeFile are not ansi conform, this means running with "CFLAGS=-Werror -Wstrict-prototypes" produces failing tests. The template file CheckIncludeFile.c.in and the one for cxx should correctly read #include <${CHECK_INCLUDE_FILE_VAR}> int main(int argc, char *argv

Re: [CMake] cmake 2.2: builddir rpath encoded into installed binary

)? Cheers, Michael On 4/26/06, Brad King <[EMAIL PROTECTED]> wrote: > Michael Biebl wrote: > > Hi all, > > > > I got project where I create a lib (libfoo) and a binary (bar) where > > bar links against libfoo. > > If I run objdump -p bar on the uninstalled

[CMake] cmake 2.2: builddir rpath encoded into installed binary

Hi all, I got project where I create a lib (libfoo) and a binary (bar) where bar links against libfoo. If I run objdump -p bar on the uninstalled binary in $builddir/src I get RPATH=$builddir/src. If I run make install the resulting binary still has RPATH set to $builddir/src. (Note: this does not

[CMake] OPTION variables are not accesible in POST_INSTALL_SCRIPTs

I have OPTION(INSTALL_LINKS "..." ON) in the toplevel CMakeLists.txt file and want to use that variable in a POST_INSTALL_SCRIPT. Depending on INSTALL_LINKS I want to create additional links. Unfortunately the value of INSTALL_LINKS is not propagated to the POST_INSTALL_SCRIPT create_links.cmake. I

Re: [CMake] Run commands after "make install"

On 4/11/06, Filipe Sousa <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Michael Biebl wrote: > > Hi, > > > > after a successfull "make install" run I want to display some messages > > and execute a comm

[CMake] Run commands after "make install"

Hi, after a successfull "make install" run I want to display some messages and execute a command. With automake I used a install-data-hook in the toplevel Makefile.am for this, so the commands were processed at the end of the install run. How can I do this with cmake? I tried to add a custom targe

[CMake] Re: Processing new extensions with cmake

FWIW, this is my solution so far: < MACRO(PROCESS_IIFILES _i_FILES _ii_FILES) SET(_i_FILES) FOREACH(_current_FILE ${ARGN}) GET_FILENAME_COMPONENT(_tmp_FILE ${_current_FILE} ABSOLUTE) GET

[CMake] Processing new extensions with cmake

Hi all, automake has the nice ability, to define handlers for new extensions. I currently use that for a project, which builds a binary called install_service, and this binary is used to process *.ii files and produce *.i files from that. The resulting *.i files will be installed. These rules loo

[CMake] Re: cmake 2.2: make install PREFIX not working with CMAKE_INSTALL_PREFIX set to "/"

On 4/10/06, Michael Biebl <[EMAIL PROTECTED]> wrote: > It's getting stranger and stranger. > As I wanted to avoid that cmake generates "//" at the beginning of the > path name, I used > SET(CMAKE_INSTALL_PREFIX "" CACHE INTERNAL "") > Now

[CMake] Re: cmake 2.2: make install PREFIX not working with CMAKE_INSTALL_PREFIX set to "/"

quot;make install DESTDIR=/tmp" the file into /tmp/usr/local/foo/bar/dir/test1 (note the "/usr/local") whereas INSTALL_FILES(/foo/bar FILES test2) installs as expected to /tmp/foo/bar/test2 This is really getting weird. Hope, someone can help me with this problem. Cheers, Michael O

[CMake] Re: cmake 2.2: make install PREFIX not working with CMAKE_INSTALL_PREFIX set to "/"

I forgot to add: Removing SET(CMAKE_INSTALL_PREFIX / CACHE INTERNAL "") and running cmake .. -DCMAKE_INSTALL_PREFIX=/ works fine. On 4/10/06, Michael Biebl <[EMAIL PROTECTED]> wrote: > With cmake 2.2 I get a very strange behaviour. > I use the following statement in my t

[CMake] cmake 2.2: make install PREFIX not working with CMAKE_INSTALL_PREFIX set to "/"

With cmake 2.2 I get a very strange behaviour. I use the following statement in my toplevel CMakeLists.txt file: SET(CMAKE_INSTALL_PREFIX / CACHE INTERNAL "") because I want to install the binaries to /sbin, /bin etc. by default. A make install works fine, but if I run "make install DESTDIR=/tmp/te

[CMake] Rename files during installation

Hi, I have two text files in one directory: test.foo test.bar test.foo has to be installed as /dir/foo/test (test is the file name) and test.bar to /dir/bar/test (test is the file name) This means that both files have to be renamed during install. How can I do that with INSTALL_FILES? It should ru