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

2017-12-11 Thread John Cary
Thanks for your help. Yes, we do a replacement of MD with MT as we need fully static builds. We do this early in configuration, using The "Dynamic Replace" method described at https://cmake.org/Wiki/CMake_FAQ specifically https://cmake.org/Wiki/CMake_FAQ#Dynamic_Replace This is possible wit

Re: [CMake] add_subdirectory and common libraries

2017-12-11 Thread Craig Scott
On Tue, Dec 12, 2017 at 5:13 AM, Harry Mallon wrote: > Hello all, > > Has anyone got any good recommendations for the following setup? > > “large_repo” contains code for a binary and two git submodules. One is > “library” which is added with add_subdirectory(). The other is some common > library

[CMake] CMake fixup_bundle for ubuntu 16.04

2017-12-11 Thread Waldo Valenzuela via CMake
Dear All, I am working on a multi-platform desktop app with Qt5-VTK8, on Windows and Mac no problem to created the standalone app, but in Ubuntu 16.04 I have several problems. I am using CodeBlocks to compile and run the app, and from CodeBlocks when I run the app there is no problem, it work

[CMake] add_subdirectory and common libraries

2017-12-11 Thread Harry Mallon
Hello all, Has anyone got any good recommendations for the following setup? “large_repo” contains code for a binary and two git submodules. One is “library” which is added with add_subdirectory(). The other is some common library “util_library” (something like gtest which is generally useful) w

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

2017-12-11 Thread John Cary
Yes, we do a replacement of MD with MT as we need fully static builds. We do this early in configuration, using The "Dynamic Replace" method described at https://cmake.org/Wiki/CMake_FAQ specifically https://cmake.org/Wiki/CMake_FAQ#Dynamic_Replace This is possible with 3.8.2.  Is there a wa

Re: [CMake] INTERFACE library and path to source.

2017-12-11 Thread Oleksii Vilchanskyi
> I'm not that sure that this is the "expected" behavior Yes, now it looks like a bug to me, too. Being written as it was in the last message, > target_sources(lib INTERFACE lib.h) can be treated as the equivalent of > target_sources(main PRIVATE lib.h) (and therefore generating an error). Howeve

Re: [CMake] MinGW Compilers on Windows

2017-12-11 Thread Alan W. Irwin
On 2017-12-10 09:18-0500 Kevan Hashemi wrote: Dear Alan, If you need/prefer Unix tools provided by MSYS to build your software, another possible generator you should look at is "MSYS Makefiles". Thank you for this suggestion. The CMake configuration and generation of OpenCV completes withou

Re: [CMake] INTERFACE library and path to source.

2017-12-11 Thread Eric Noulard
2017-12-09 1:37 GMT+01:00 Oleksii Vilchanskyi : > Hello Eric, > > > Why should I do that? > > Is this the expected behavior / way to create header only library? > > Yes, this is the expected behaviour. CMake interprets a relative path to > the file according to the target's add_library() or add_ex