[CMake] Generating libtool file with CMake

2018-11-09 Thread Mathieu Tarral via CMake
Hi ! I'm trying to port the LibVMI project from autotools to CMake: https://github.com/libvmi/libvmi/pull/674 One of the problems I have is to generate a libtool libvmi.la file, like autotools is already doing. So far I have found this module on CMake wiki: https://gitlab.kitware.com/cmake/c

Re: [CMake] INTERFACE_LINK_LIBRARIES/LINK_INTERFACE_LIBRARIES

2018-11-09 Thread Hendrik Greving
In other words, when providing the EXPORT_LINK_INTERFACE_LIBRARIES flag for exported targets (in main project that was changed to CMP0022 NEW), I was expecting the IMPORTED_LINK_INTERFACE_LIBRARIES property set in the .cmake file so that projects that import it (with CMP0022 OLD) can see it. Instea

[CMake] INTERFACE_LINK_LIBRARIES/LINK_INTERFACE_LIBRARIES

2018-11-09 Thread Hendrik Greving
If CMP0022 is set to new, since project is still using LINK_INTERFACE_LIBRARIES I have added EXPORT_LINK_INTERFACE_LIBRARIES to install(EXPORT) and export() calls. Looking at the generated exported cmake files, I only see the INTERFACE_LINK_LIBRARIES link property set. There are downstream projects

Re: [CMake] CPack disable build all

2018-11-09 Thread Eric Noulard
Le ven. 9 nov. 2018 à 17:22, DKLind a écrit : > I have a very large project where each sub-project creates a debian > package. > > When "make/ninja package" is specified, it performs a "make/ninja all" > before packaging. I would prefer to perform a "make/ninja all" myself > before > I doing a "m

[CMake] CPack disable build all

2018-11-09 Thread DKLind
I have a very large project where each sub-project creates a debian package. When "make/ninja package" is specified, it performs a "make/ninja all" before packaging. I would prefer to perform a "make/ninja all" myself before I doing a "make/ninja package". I want to create a package for just one

Re: [CMake] dependencies of cross compiliations

2018-11-09 Thread Miller Henry
There are two options. Each with pros and cons. The first what you are doing now, except you use external project https://cmake.org/cmake/help/v3.12/module/ExternalProject.html to build the host tools instead of add_custom_command. It otherwise has all the cons you mention, but are they signifi

Re: [CMake] [cmake-developers] module proposal: PreventInSourceBuilds

2018-11-09 Thread Rolf Eike Beer
# disallow in-source builds if("${srcdir}" STREQUAL "${bindir}") if(srcdir STREQUAL bindir) HTH Eike -- -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community

[CMake] dependencies of cross compiliations

2018-11-09 Thread Torsten Robitzki
Hi, I hope this question was not asked before. I work in the embedded field and there it is usually to have at least two different build platforms. The Host platform, where unit tests are build (and where CMake is running) and an embedded Target platform, where targets are build with a cross com