Re: [CMake] install(TARGETS ... INCLUDES) has no effect.

> > > Hello! > > Did you try INCLUDES DESTINATION? > > install (TARGETS foo > EXPORT foo_export > ARCHIVE DESTINATION bin > LIBRARY DESTINATION lib > RUNTIME DESTINATION lib > INCLUDES DESTINATION include) > Oops! It works! I have no idea how I miss the DESTINATION keyword. And sadly

[CMake] install(TARGETS ... INCLUDES) has no effect.

Hello, The documentation of the INCLUDES option of install(TARGETS) command says: "This option specifies a list of directories which will be added to the INTERFACE_INCLUDE_DIRECTORIES target property of the when exported by the

Re: [CMake] Install targets and component

On 08/11/2015 09:05 AM, Lars wrote: Hello, The following cmake script appears to work but the target is associated with Unspecified group according to cmake_install.cmake file. INSTALL( TARGETS MyLib RUNTIME DESTINATION ${BIN_PATH} LIBRARY DESTINATION ${LIB_PATH} COMPONENT COMP_APP)

Re: [CMake] Install targets and component

Thank you Nils, that solved the issue. Cannot believe I missed that in the documentation. Regards, Lars Date: Tue, 11 Aug 2015 09:41:22 +0200 From: nilsglad...@gmail.com To: laasu...@hotmail.com; cmake@cmake.org Subject: Re: [CMake] Install targets and component On 08/11/2015 09:05 AM

[CMake] Install targets and component

Hello, The following cmake script appears to work but the target is associated with Unspecified group according to cmake_install.cmake file. INSTALL( TARGETS MyLib RUNTIME DESTINATION ${BIN_PATH} LIBRARY DESTINATION ${LIB_PATH} COMPONENT COMP_APP) By removing the following section the

Re: [CMake] install(TARGETS) does not work with configuration-specific destinations

Ah! Specifying the CONFIGURATIONS argument *before* the DESTINATION ones works as intended. It would really help if the documentation was changed to reflect the importance of parameter ordering here. install(TARGETS ${target} COMPONENT ${component}

Re: [CMake] install(TARGETS) does not work with configuration-specific destinations

Updating the documentation for this would help... Do you have time to propose a patch which updates the wording of the documentation to stress the importance of parameter ordering? On Tue, Jun 9, 2015 at 4:31 AM, Alessio masariello+cmake@gmail.com wrote: Ah! Specifying the CONFIGURATIONS

Re: [CMake] install(TARGETS) does not work with configuration-specific destinations

I forgot to mention that, by contrast, elsewhere I have the following working code. So install(FILES) seems to work fine with multiple calls for different configurations. install( FILES $TARGET_FILE_DIR:corelib/some_file.txt COMPONENT platform DESTINATION

[CMake] install(TARGETS) does not work with configuration-specific destinations

Hi The below CMake code is causing my targets to get installed twice in the same tarball when I invoke cpack with the following command line ${CPACK_COMMAND} -G ${cpack_gen} --config ${CMAKE_CURRENT_BINARY_DIR}/${package_cfg_file} -C $CONFIGURATION The generated cmake_install.cmake in fact

[CMake] Install( Targets ) loses executable permission

Basically this is the command I use to install some plugins... BINARY_OUTPUT_DIR is ${CMAKE_INSTALL_PREFIX}/bin project_target is a argument to the macro and it's 'plugins' install( TARGETS ${proj} · RUNTIME DESTINATION ${BINARY_OUTPUT_DIR}/${project_target} · LIBRARY

Re: [CMake] Install( Targets ) loses executable permission

Am 22. April 2015 04:01:40 MESZ, schrieb J Decker d3c...@gmail.com: the library is built 'tasks.isp' with rwxr-xr-x but it's installed with rw-r--r-- (platform is rasberry pi) Normal libraries on linux don't need any executable bit set. That the linker creates files with that permission has

Re: [CMake] Install( Targets ) loses executable permission

On Tue, Apr 21, 2015 at 9:21 PM, Hendrik Sattler p...@hendrik-sattler.de wrote: Am 22. April 2015 04:01:40 MESZ, schrieb J Decker d3c...@gmail.com: the library is built 'tasks.isp' with rwxr-xr-x but it's installed with rw-r--r-- (platform is rasberry pi) Normal libraries on linux don't

Re: [CMake] Install( Targets ) loses executable permission

You can pass in the below variable to CMake (or set it in you CMake file) and you should get what you want: -DCMAKE_INSTALL_SO_NO_EXE=0 -Caleb On Tue, Apr 21, 2015 at 10:01 PM, J Decker d3c...@gmail.com wrote: Basically this is the command I use to install some plugins... BINARY_OUTPUT_DIR

Re: [CMake] install TARGETS given unknown argument EXPORT. with cmake 2.8.9

Sure it should -- can you edit the wiki page, and correct it? I don't have an account to edit the WIKI, so it might be faster if somebody who already does have an account does so. -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at:

Re: [CMake] install TARGETS given unknown argument EXPORT. with cmake 2.8.9

Sure it should -- can you edit the wiki page, and correct it? I don't have an account to edit the WIKI, so it might be faster if somebody who already does have an account does so. Actually, I never should have sent my request.. :-) Chuck Atkins already had done it and replied that it

Re: [CMake] install TARGETS given unknown argument EXPORT. with cmake 2.8.9

The order of arguments is wrong. Move the 'EXPORT foo-targets' to just after 'TARGETS foo'. That fixed the issue. Shouldn't the WIKI be fixed so the example is correct? -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at:

Re: [CMake] install TARGETS given unknown argument EXPORT. with cmake 2.8.9

David, Indeed it should. Thanks for catching that! I've updated the wiki page with the correct order of arguments. - Chuck On Fri, Feb 21, 2014 at 11:25 AM, david.hag...@gmail.com wrote: The order of arguments is wrong. Move the 'EXPORT foo-targets' to just after 'TARGETS foo'.

Re: [CMake] install TARGETS given unknown argument EXPORT. with cmake 2.8.9

Hi David, What does your install(...) line look like so we can try to help you debug the issue? OK, this is about as simple as it gets: --- file foo.c: extern int foo(void) { return 0; } --- file CMakeLists.txt cmake_minimum_required( VERSION

Re: [CMake] install TARGETS given unknown argument EXPORT. with cmake 2.8.9

david.hag...@gmail.com wrote: install(TARGETS foo RUNTIME DESTINATION bin LIBRARY DESTINATION lib EXPORT foo-targets ) The order of arguments is wrong. Move the 'EXPORT foo-targets' to just after 'TARGETS foo'. I don't know if this is a behavior change since the wiki was written, but

Re: [CMake] install TARGETS given unknown argument EXPORT. with cmake 2.8.9

I've not received any responses on my question as to why the install function was not accepting the EXPORT argument on cmake 2.8.9, as the WIKI (http://www.cmake.org/Wiki/CMake/Tutorials/Packaging) indicates should work. Again: I've seen many hits on the Internet about this error, so it's not

Re: [CMake] install TARGETS given unknown argument EXPORT. with cmake 2.8.9

david.hag...@gmail.com wrote: Does anybody have any suggestions on how to resolve this? Create an http://www.sscce.org/ and post it so that others can try what fails for you. Thanks, Steve. -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at:

Re: [CMake] install TARGETS given unknown argument EXPORT. with cmake 2.8.9

Hi David, What does your install(...) line look like so we can try to help you debug the issue? - Chuck On Wed, Feb 12, 2014 at 4:09 PM, david.hag...@gmail.com wrote: I am trying to set up component registration as per http://www.cmake.org/Wiki/CMake/Tutorials/Packaging but when I run

[CMake] install TARGETS given unknown argument EXPORT. with cmake 2.8.9

I am trying to set up component registration as per http://www.cmake.org/Wiki/CMake/Tutorials/Packaging but when I run Cmake I get the error install TARGETS given unknown argument EXPORT. While I've found many hits on Google with that error string, none that I have found have any resolution

Re: [CMake] CPACK and cmake install(targets

When executing the install target in my projet, the dll goes to the bin folder and the lib goes to the lib folder. That is all good. But when running CPACK only the .lib file is packaged, and not the DLL. Why?? May be because you are doing component packaging and that the COMPONENT part of

[CMake] CPACK and cmake install(targets

Hi, I try to package a built shared library on windows. In the CMAKE file for where the dll and import lib is created I have install(TARGETS ${target} RUNTIME DESTINATION bin LIBRARY DESTINATION lib ARCHIVE DESTINATION lib COMPONENT rr_core ) When executing the

Re: [CMake] CPACK and cmake install(targets

2013/1/18 Totte Karlsson to...@dunescientific.com: Hi, I try to package a built shared library on windows. In the CMAKE file for where the dll and import lib is created I have install(TARGETS ${target} RUNTIME DESTINATION bin LIBRARY DESTINATION lib ARCHIVE

[CMake] install targets

I have split my code up into two dirs, source and tests. The CMakeLists.txt in the source dir does a SUBDIRS to ${PROJECT_SOURCE_DIR}/../tests to get tests. In each CMakeLists file right after I have defined the target via ADD_LIBRARY or ADD_EXECUTABLE and set TARGET_LINK_LIBRARIES I have done

Re: [CMake] install targets

Ok, sorry for the duplication, it was also discussed in: http://www.cmake.org/pipermail/cmake/2011-March/043467.html I changed everything from SUBDIRS to add_subdirectory and it worked. For my tests dir, I specified a second build dir, and everything then installed from those dirs. Matt On Tue,

Re: [CMake] install targets

I have split my code up into two dirs, source and tests. The CMakeLists.txt in the source dir does a SUBDIRS to ${PROJECT_SOURCE_DIR}/../tests to get tests. Reading the documentation may help: subdirs Deprecated. Use the add_subdirectory() command instead. HTH, Eike -- Powered by

Re: [CMake] Install targets

On 07/02/2011 04:34 AM, Tim Gallagher wrote: Hi, We have a project that has a main executable and dozens of utility executables that may or may not be needed. We can add an executable for each util with EXCLUDE_FROM_ALL defined so just typing make only does the main code and something

[CMake] install( TARGETS module ...)

Dear all, I am trying to change the default behavior of cmake which installs MODULE to the LIBRARY destination. For example: ... add_library(test MODULE test.c) install(TARGETS test RUNTIME DESTINATION bin LIBRARY DESTINATION lib ARCHIVE DESTINATION lib/static ) ... Will install

[CMake] Install targets

Hi, We have a project that has a main executable and dozens of utility executables that may or may not be needed. We can add an executable for each util with EXCLUDE_FROM_ALL defined so just typing make only does the main code and something like 'make grid' compiles the grid generator. But,

[CMake] Install targets defined in other directories

does not exist in this directory. Is not possible with cmake install targets defined in other directories? If NO why i can't see the reason. Regards, Daniele ___ Powered by www.kitware.com Visit other Kitware open-source projects at http

Re: [CMake] Install targets defined in other directories

with message. install TARGETS given target core which does not exist in this directory. Is not possible with cmake install targets defined in other directories? No. If NO why i can't see the reason. Targets should have project-global unique names, all the rest is parameters. Not sure

Re: [CMake] INSTALL TARGETS modifies files on some platforms.

Magnus Sirwiö wrote: Hi, I have notices strange behavior when using the INSTALL rule with the TARGETS signature as shown below: It is normal behavior. install strips and relinks your executables before install. This removes useless data like debugging symbols, making your executables

[CMake] INSTALL TARGETS modifies files on some platforms.

Hi, I have notices strange behavior when using the INSTALL rule with the TARGETS signature as shown below: INSTALL ( TARGETS setuptool DESTINATION .) On some platforms the file copy of the above rule modifies the size of the file. ls -l bin/setuptool install/setuptool -rwxrwxr-x 1 bbb

[CMake] INSTALL(TARGETS and custom target

Hello, After reading the documentation of INSTALL, I found out: $ cmake --help INSTALL ... Use the TARGETS form to install targets built within the project. ... Right now I have a custom macro similar in signature to ADD_EXECUTABLE: ADD_PI_EXECUTABLE(target_name filename.py) Basically this