Re: [CMake] What is the best way to handle Boost dependencies in a package config file

2016-01-26 Thread Ruslan Baratov via CMake
On 27-Jan-16 09:54, Johnson, Matt (GE Healthcare) wrote: I like package config files. I want to use more of them. However, I have a dependency on boost. While boost has a Find module, it doesn't have a package config file. I'm not going to be able to depend on the users of my package build

Re: [CMake] What is the best way to handle Boost dependencies in a package config file

2016-01-26 Thread Michi Henning
We use this, which works fine for me on Ubuntu: find_package(Boost COMPONENTS system filesystem regex serialization thread log REQUIRED) Cheers, Michi. > On 27 Jan 2016, at 12:54 , Johnson, Matt (GE Healthcare) > wrote: > > I like package config files. I want to use more of them. However,

[CMake] What is the best way to handle Boost dependencies in a package config file

2016-01-26 Thread Johnson, Matt (GE Healthcare)
I like package config files. I want to use more of them. However, I have a dependency on boost. While boost has a Find module, it doesn't have a package config file. I'm not going to be able to depend on the users of my package building boost via cmake (also, is that still an active thing?).

Re: [CMake] Importing a static library, then adding dependencies. Should the dependencies be transitive? They aren't for me!

2016-01-26 Thread Nils Gladitz
On 26.01.2016 21:25, Johnson, Matt (GE Healthcare) wrote: I'm using the Visual Studio 2013 generator and cmake 3.4.3. Example: add_library(NS::a_lib STATIC IMPORTED) set_target_properties(NS::a_lib PROPERTIES IMPORTED_LOCATION ${a_lib_location}) set_target_properties(NS::a_lib PROPERTIES INTERFAC

[CMake] Importing a static library, then adding dependencies. Should the dependencies be transitive? They aren't for me!

2016-01-26 Thread Johnson, Matt (GE Healthcare)
I'm using the Visual Studio 2013 generator and cmake 3.4.3. Example: add_library(NS::a_lib STATIC IMPORTED) set_target_properties(NS::a_lib PROPERTIES IMPORTED_LOCATION ${a_lib_location}) set_target_properties(NS::a_lib PROPERTIES INTERFACE_LINK_LIBRARIES "/path/to/a/another_lib.lib") set_target_p

Re: [CMake] WINDOWS_EXPORT_ALL_SYMBOLS

2016-01-26 Thread Bill Hoffman
On 1/26/2016 5:12 AM, Micha Renner wrote: It prevents that I can link the library to a program since there is no __local_stdio_printf_options etc. May be there exists an explanation. Greetings Michael cmake 3.4.2 Windows 10 VS Express 15 So, I am able to get this to work with Visual Studio

Re: [CMake] include_external_msproject

2016-01-26 Thread iosif neitzke
No, I do not believe so. https://cmake.org/cmake/help/v3.4/command/include_external_msproject.html Keyword being 'project'. On Tue, Jan 26, 2016 at 8:43 AM, Lars wrote: > Appreciate some help understanding include_external_msproject. > Using Windows 7 and cmake 3.3 > > This is what has been don

[CMake] include_external_msproject

2016-01-26 Thread Lars
Appreciate some help understanding include_external_msproject. Using Windows 7 and cmake 3.3 This is what has been done so far, 1. Opened Visual Studio 2012 and created a new project (Windows Forms Application) and saved it under c:\temp\test. 2. Used the following to an cmake; include_ext

Re: [CMake] CMake 3.4.3 available for download

2016-01-26 Thread Brad King
On 01/25/2016 04:12 PM, Gonzalo Garramuño wrote: > Does this one have the fix for the FLTK_WRAP_UI? No, sorry. 3.4.3 was released only as a quick fix to 3.4.2's problems on Windows 10. 3.5 will have the fltk fix, and the freeze for that is next week. -Brad -- Powered by www.kitware.com Plea

Re: [CMake] errors with add_custom_command and add_custom_target

2016-01-26 Thread Petr Kmoch
Normally, you would want to keep your source tree clean from any build-time modifications (CMake *strongly discourages* in-source builds, with good reason). Therefore, you'd want to generate the files in CMAKE_CURRENT_BINARY_DIR. Assuming the generator always writes them into its current directory,

Re: [CMake] errors with add_custom_command and add_custom_target

2016-01-26 Thread Vania Joloboff
Hi Petr, Thanks, indeed I had unset the property ! Cmake works fine with removing the line. But I have now a doubt. My generator generates the files in the current dir. Should I indicate the working directory in add_custom_command ? so that the generated sources are added in CMAKE_CURRENT_SOURCE_

Re: [CMake] errors with add_custom_command and add_custom_target

2016-01-26 Thread Petr Kmoch
Hi, Vania. You should remove this line: set_property(SOURCE ${GEN_SOURCES} PROPERTY GENERATED ) CMake will mark the files as generated automatically. What your line is actually doing is setting them as *not* generated, because you didn't pass any argument to set the property to, so it's implici

[CMake] errors with add_custom_command and add_custom_target

2016-01-26 Thread Vania Joloboff
Hi I have a generator that generates some, but not all of the source files. My understanding was that I should use add_custom_command for that When I do set(EXIST_SOURCES A.cc B.cc C.cc) set(GEN_SOURCES X.cc Y.cc Z.cc) add_custom_command(OUTPUT ${GEN_SOURCES} COMMAND gener

Re: [CMake] Checking whether particular *linker* flags are supported

2016-01-26 Thread Guy Harris
On Jan 22, 2016, at 12:24 PM, Guy Harris wrote: > CMake has the macros CHECK_C_COMPILER_FLAG and CHECK_CXX_COMPILER_FLAG, which > allow checking for whether a given C or C++ compiler flag is supported by the > compiler being used. > > However, there's no CHECK_LINKER_FLAG macro, so that you ca