Re: [CMake] Using find_package() portably?

On Monday, December 4, 2017, Carsten Fuchs wrote: > Thanks to all! > > Well, I guess I'm among the people mentioned by Lectem at https://www.mail-archive.com/cmake-developers@cmake.org/msg18267.html > > I'll try to dig my way through it, but at this point I consider staying with SCons under Linux,

Re: [CMake] CPack: Create debian packge for each sub-project

2017-12-04 20:35 GMT+01:00 DKLind : > Domen Vrankar wrote > > I'm a bit confused. Is there something missing in the patch? > > Attached patch only adds per component version override - it doesn't even > > touch the multiple calls to `include(CPack)` and naming of different > > packages (not their

Re: [CMake] INTERFACE libraries and -config.cmake files

2017-12-04 23:17 GMT+01:00 Saad Khattak : > Hi, > > I have an interface library and I am not sure how I would get CMake to > generate the usual -config.cmake file for the library so that I can > then use "find_package" on the interface library from an external project. > > I am adding (and install

[CMake] INTERFACE libraries and -config.cmake files

Hi, I have an interface library and I am not sure how I would get CMake to generate the usual -config.cmake file for the library so that I can then use "find_package" on the interface library from an external project. I am adding (and installing) the library like this: add_library(myLib INTERFAC

[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 j

Re: [CMake] FortranCInterface not working with 3.9.0 with Intel 2015

Can you just send me a zip or tar file of the build tree from your project? Thanks. On 12/2/2017 4:17 AM, JR Cary wrote: Does it work with 3.10? It works with no version from 3.9.0 - 3.10.0. Also, look in the CMakeFiles/CMakeError.log file to find out why this happened: - Detecting For

Re: [CMake] CPack: Create debian packge for each sub-project

Domen Vrankar wrote > I'm a bit confused. Is there something missing in the patch? > Attached patch only adds per component version override - it doesn't even > touch the multiple calls to `include(CPack)` and naming of different > packages (not their components but different package names). > > C

Re: [CMake] CPack: Create debian packge for each sub-project

2017-12-04 19:57 GMT+01:00 DKLind : > Domen Vrankar wrote > > product_1-component_1-1.0.0 > > product_1-component_2-1.0.0 > > product_2-component_1-3.5.7 > > product_2-component_2-3.5.7 > > This too is what my patch fixes. Attached is the patch. > > CPackDeb.patch >

Re: [CMake] CPack: Create debian packge for each sub-project

Domen Vrankar wrote > product_1-component_1-1.0.0 > product_1-component_2-1.0.0 > product_2-component_1-3.5.7 > product_2-component_2-3.5.7 This too is what my patch fixes. Attached is the patch. CPackDeb.patch -- Sent from: ht

[CMake] [CMAKE] - custom compiler for Android

HI All, I am reposting the below email. Any help is highly appreciated. We are working towards creating a toolchain file for an ANDROID compiler We understand that the flow in CMAKE, when CMAKE_SYSTEM_NAME is specified in Android is different when compared to specifying CMAKE_SYSTEM_NA

Re: [CMake] Using find_package() portably?

Thanks to all! Well, I guess I'm among the people mentioned by Lectem at https://www.mail-archive.com/cmake-developers@cmake.org/msg18267.html I'll try to dig my way through it, but at this point I consider staying with SCons under Linux, where finding packages is important and the command l