Re: [CMake] install(EXPORT "XXXTargets" ...) includes target "XXX" which requires target "caffe2_library"...

Does someone know how to generate these missing targets or how to fix this? Thanks for any help! All the best, Mario On 03.03.19 11:28, Mario Emmenlauer wrote: > > Dear all, > > I'm trying to build a C++ project based on PyTorch with cmake package > configuration files. The includes and

[CMake] install(EXPORT "XXXTargets" ...) includes target "XXX" which requires target "caffe2_library"...

Dear all, I'm trying to build a C++ project based on PyTorch with cmake package configuration files. The includes and libs generally seem to work after doing: find_package(Torch 1.0.0 REQUIRED) But when I try to generate package configuration for my library, cmake shows an error: CMake

[CMake] INSTALL EXPORT for Debug and Release

With two build directories -- one for release and one for debug -- using the Makefile generator, it seems like calling one 'make install' replaces out the export files for the other with the message: > Old export file ".cmake" will be replaced. Removing files [-debug.cmake] The INSTALL snippet

Re: [CMake] install EXPORT uses absolute paths on Windows, making libraries not relocatable

I must have missed that, thanks! 2015-09-12 15:30 GMT+02:00 Nils Gladitz : > On 12.09.2015 15:04, Wojciech Mamrak wrote: >> >> install(TARGETS foo >> EXPORT FooTargets >> ARCHIVE DESTINATION "${INSTALL_LIBDIR}") > > > Your target's install DESTINATION is

[CMake] install EXPORT uses absolute paths on Windows, making libraries not relocatable

Hello, based on both wiki and this presentation: https://archive.fosdem.org/2013/schedule/event/moderncmake/attachments/slides/258/export/events/attachments/moderncmake/slides/258/cmake_fosdem_2013.pdf I have made this simple example. Its purpose is to test installing projects and importing them

Re: [CMake] install EXPORT uses absolute paths on Windows, making libraries not relocatable

On 12.09.2015 15:04, Wojciech Mamrak wrote: install(TARGETS foo EXPORT FooTargets ARCHIVE DESTINATION "${INSTALL_LIBDIR}") Your target's install DESTINATION is absolute which is why the exported location is absolute as well. e.g. using "DESTINATION lib" instead of

[CMake] install(EXPORT ...) includes target B which requires target A that is not in the export set

Hi all, One of my projects contains two libraries libA and libB, where libB depends on libA, and both are exporting their configuration through the usual `INSTALL(EXPORT ...)` mechanisms. I'm getting errors of the type ``` CMake Error: install(EXPORT SEACASNemesis-exports ...) includes target

Re: [CMake] install(EXPORT ...) includes target B which requires target A that is not in the export set

On Thursday, September 11, 2014 23:51:21 Nico Schlömer wrote: Hi all, One of my projects contains two libraries libA and libB, where libB depends on libA, and both are exporting their configuration through the usual `INSTALL(EXPORT ...)` mechanisms. I'm getting errors of the type ```

Re: [CMake] install(EXPORT ...) behavior for multi-configuration generators

, another one for release) with multi-conf generators. Regards, Gregoire From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf Of Gregoire Aujay Sent: lundi 7 janvier 2013 18:57 To: cmake@cmake.org Subject: [CMake] install(EXPORT ...) behavior for multi-configuration

[CMake] install(EXPORT ...) behavior for multi-configuration generators

Hello, I am using CMake 2.8.10.2, on windows. I am trying to use install(TARGETS ) and install(EXPORT ) both with NMake makefiles and with the multi-configuration generator Visual studio. I cannot get the same behavior when I want my binaries to be installed in a subfolder that depends on the

Re: [CMake] install export : ignore imported_link_interface_libraries and imported_link_dependents_libraries

On 11/02/2011 04:19 PM, Jaonary Rabarisoa wrote: Hi all, I'm using the command install(EXPORT ) to create a configuration file for my project. This works great but by default cmake fills the IMPORTED_LINK_INTERFACE_LIBRARIES and IMPORTED_LINK_DEPENDENTS_LIBRARIES. I'd like cmake to ignore

[CMake] install export : ignore imported_link_interface_libraries and imported_link_dependents_libraries

Hi all, I'm using the command install(EXPORT ) to create a configuration file for my project. This works great but by default cmake fills the IMPORTED_LINK_INTERFACE_LIBRARIES and IMPORTED_LINK_DEPENDENTS_LIBRARIES. I'd like cmake to ignore these properties because it introduces a hard link to my

[CMake] install(EXPORT) and Mac OS X frameworks

Hi all How would I instruct install(EXPORT) to install the file into my Mac OS X framework elegantly? For source files I can do so using the MACOSX_PACKAGE_LOCATION property, but it would be nice if I didn't have to guess/hard-code the directory inside the framework for the exports-file too.

Re: [CMake] INSTALL(EXPORT) does not honor LINK_INTERFACE_LIBRARIES?

On 04/02/2011 10:52 AM, Rolf Eike Beer wrote: Am Donnerstag, 31. März 2011, 15:26:31 schrieb Brad King: On 03/31/2011 09:14 AM, Rolf Eike Beer wrote: See below. Looks like the only way to prevent this is to set LINK_INTERFACE_LIBRARIES to empty for every lib that uses the static lib. Which

Re: [CMake] INSTALL(EXPORT) does not honor LINK_INTERFACE_LIBRARIES?

Michael Hertling wrote: On 03/30/2011 03:14 PM, Rolf Eike Beer wrote: [...] Only adding INSTALL(TARGETS privstatic EXPORT myexport DESTINATION trash) made CMake complete successfully, resulting in the static stuff showing up in the export, too. Could you provide a minimal but complete

Re: [CMake] INSTALL(EXPORT) does not honor LINK_INTERFACE_LIBRARIES?

On 03/31/2011 09:14 AM, Rolf Eike Beer wrote: See below. Looks like the only way to prevent this is to set LINK_INTERFACE_LIBRARIES to empty for every lib that uses the static lib. Which may be a good idea anyway as that transitive linking is harmful. CMake has always done said transitive

Re: [CMake] INSTALL(EXPORT) does not honor LINK_INTERFACE_LIBRARIES?

On 03/29/2011 11:36 PM, Rolf Eike Beer wrote: Am Dienstag, 29. März 2011, 09:41:36 schrieb Brad King: On 03/29/2011 05:19 AM, Rolf Eike Beer wrote: The basic idea is: any symbols from those private libraries are, well, private. The user only ever sees the symbols from the public library. In

Re: [CMake] INSTALL(EXPORT) does not honor LINK_INTERFACE_LIBRARIES?

On 03/29/2011 11:36 PM, Rolf Eike Beer wrote: Am Dienstag, 29. März 2011, 09:41:36 schrieb Brad King: On 03/29/2011 05:19 AM, Rolf Eike Beer wrote: The basic idea is: any symbols from those private libraries are, well, private. The user only ever sees the symbols from the public library. In

Re: [CMake] INSTALL(EXPORT) does not honor LINK_INTERFACE_LIBRARIES?

On 03/30/2011 02:02 PM, Rolf Eike Beer wrote: However, I still don't understand the relation of that transitive linking and its avoidance, respectively, to your initial complaint about CMake's error message due to the missing library in another library's export set. Unless I'm mistaken,

Re: [CMake] INSTALL(EXPORT) does not honor LINK_INTERFACE_LIBRARIES?

On 03/30/2011 02:02 PM, Rolf Eike Beer wrote: However, I still don't understand the relation of that transitive linking and its avoidance, respectively, to your initial complaint about CMake's error message due to the missing library in another library's export set. Unless I'm mistaken,

Re: [CMake] INSTALL(EXPORT) does not honor LINK_INTERFACE_LIBRARIES?

On 03/30/2011 03:14 PM, Rolf Eike Beer wrote: On 03/30/2011 02:02 PM, Rolf Eike Beer wrote: However, I still don't understand the relation of that transitive linking and its avoidance, respectively, to your initial complaint about CMake's error message due to the missing library in another

Re: [CMake] INSTALL(EXPORT) does not honor LINK_INTERFACE_LIBRARIES?

On 03/28/2011 02:51 PM, Rolf Eike Beer wrote: I try to do an INSTALL(EXPORT) to allow others to link against one of my libraries. That libraries is linked against some other internal libraries the target's don't need to link to as everything in them is purely internal. I tried something

Re: [CMake] INSTALL(EXPORT) does not honor LINK_INTERFACE_LIBRARIES?

On 03/28/2011 02:51 PM, Rolf Eike Beer wrote: I try to do an INSTALL(EXPORT) to allow others to link against one of my libraries. That libraries is linked against some other internal libraries the target's don't need to link to as everything in them is purely internal. I tried something

Re: [CMake] INSTALL(EXPORT) does not honor LINK_INTERFACE_LIBRARIES?

On 03/29/2011 05:19 AM, Rolf Eike Beer wrote: The basic idea is: any symbols from those private libraries are, well, private. The user only ever sees the symbols from the public library. In fact he _can't_ even link to the private libraries on Windows as we never install the .lib files. And

Re: [CMake] INSTALL(EXPORT) does not honor LINK_INTERFACE_LIBRARIES?

Am Dienstag, 29. März 2011, 09:41:36 schrieb Brad King: On 03/29/2011 05:19 AM, Rolf Eike Beer wrote: The basic idea is: any symbols from those private libraries are, well, private. The user only ever sees the symbols from the public library. In fact he _can't_ even link to the private

Re: [CMake] INSTALL(EXPORT) does not honor LINK_INTERFACE_LIBRARIES?

You still need to install that lib even if it is not used by 3rd party application, it is used inernally by your own application. INSTALL(TARGETS publiclib privatelib...) The private libraries are of course installed. If I link against that installed public library by hand everything works

Re: [CMake] Install Export and include

On 22. Apr, 2010, at 14:44 , Nicola Brisotto wrote: Hi, I'm building a library QXmppClient that export properties with INSTALL (EXPORT ...) How can I also export a variable with the include path of the library? In the executable project I use find_package(QXmppClient). The target

[CMake] INSTALL( EXPORT ... requires target that is not in export set

I am trying to use INSTALL( EXPORT ... but failing. I have a project like this ImageMagick/CMakeLists.txt -- 1. ImageMagick/magick/CMakeLists.txt -- 2. ImageMagick/coders/CMakeLists.txt -- 3. 1. calls ADD_SUBDIRECTORY for both 2 and 3 2. has a target magick that is a library 3. has a target

Re: [CMake] INSTALL( EXPORT ... requires target that is not in export set

On 2009-12-08 13:59+1200 Hugh Sorby wrote: I am trying to use INSTALL( EXPORT ... but failing. I have a project like this ImageMagick/CMakeLists.txt -- 1. ImageMagick/magick/CMakeLists.txt -- 2. ImageMagick/coders/CMakeLists.txt -- 3. 1. calls ADD_SUBDIRECTORY for both 2 and 3 2. has a

[CMake] install(EXPORT ...)

The command INSTALL( TARGETS ${PROJ_LIB_NAME} EXPORT proj-targets LIBRARY DESTINATION lib ARCHIVE DESTINATION lib RUNTIME DESTINATION bin ) Works very nicely, when 'make install' is invoked, is there a way of achieving a similar result which is generated in the build directory -

Re: [CMake] install(EXPORT ...)

On 2. Dec, 2009, at 10:09 , Biddiscombe, John A. wrote: The command INSTALL( TARGETS ${PROJ_LIB_NAME} EXPORT proj-targets LIBRARY DESTINATION lib ARCHIVE DESTINATION lib RUNTIME DESTINATION bin ) Works very nicely, when 'make install' is invoked, is there a way of achieving a

Re: [CMake] install(EXPORT ...)

Michael Thank you. That seems to do what I need. JB You can use export(TARGETS target ... [NAMESPACE namespace] [APPEND] FILE output_file ) which you can then include() in your dependent project. Michael ___ Powered by

Re: [CMake] install(EXPORT ...)

I just found out that in the new CMake-2.8 there is also export(PACKAGE package_name) which adds your build-tree to the user's package database and helps CMake finding build-trees when using find_package(package_name) from another project. However, this still requires that you create an

[CMake] install(EXPORT ..) and multiple projects

I've got two projects with one depending on the other. I include the one project as a subdirectory and build it along with my project. Its similar to how ParaView includes VTK. I'm trying to use the install(EXPORT ...) to export my project from an installation tree, but I can't figure out how

Re: [CMake] install(EXPORT ..) and multiple projects

Clinton Stimpson wrote: I've got two projects with one depending on the other. I include the one project as a subdirectory and build it along with my project. Its similar to how ParaView includes VTK. I'm trying to use the install(EXPORT ...) to export my project from an installation tree,

Re: [CMake] INSTALL(EXPORT)

Hi folks, My apologies for cross-posting - I'm hoping this is of interest to the ITK list, and it continues a month-old conversation on the CMake list. Recap: I like to have the debug and optimized versions of my ITK libraries have different names (e.g. ITKCommon.lib, ITKCommond.lib). This way

Re: [CMake] INSTALL(EXPORT)

Thanks Brad, One last question. Is there a way to retrieve the list of objects that have been put in the EXPORT parameter of various install commands? Basically i would like to use EXPORT(TARGETS FILE ...) to get a file in the build directory equivalent to the file i would get from.

Re: [CMake] INSTALL(EXPORT)

Rupert Brooks wrote: One last question. Is there a way to retrieve the list of objects that have been put in the EXPORT parameter of various install commands? Basically i would like to use EXPORT(TARGETS FILE ...) to get a file in the build directory equivalent to the file i would

Re: [CMake] INSTALL(EXPORT)

Thanks Brad, I will either export them as i go, or store them in a variable, and export that list at the end. FYI, I am planning to construct build-tree and install-tree export rules for upstream VTK and ITK once we require CMake 2.6. I guess I am impatient ;-). The reason that I am trying

[CMake] INSTALL(EXPORT)

Hi, Im trying to use the INSTALL(EXPORT) option on a number of libraries to export their dependencies to a file that can then be loaded in my project. I have all the libraries with an EXPORT option in their INSTALL line, and CMake runs and seems to work ok. If I install, the export I wanted is

Re: [CMake] INSTALL(EXPORT)

Rupert Brooks wrote: 1. Does the name of this file appear in a variable somewhere, so that i can use configure file to write it into the ITKConfig.cmake script. Previously, there was this SET(ITK_LIBRARY_DEPENDS_FILE @ITK_LIBRARY_DEPENDS_FILE@) where ITK_LIBRARY_DEPENDS_FILE is set by the