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
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
The following issue has been SUBMITTED.
==
https://cmake.org/Bug/view.php?id=15936
==
Reported By:Erik Hanspers
Assigned To:
_VERSION_MINOR 4)
-set(CMake_VERSION_PATCH 20160126)
+set(CMake_VERSION_PATCH 20160127)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/
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
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
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
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
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
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
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
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;
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
>
>
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
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")
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
Hi Steve,
Zitat von Stephen Kelly :
Benjamin Eikel wrote:
Hi Gregor,
Am Mittwoch, 30. Dezember 2015, 14:33:08 schrieb Gregor Jasny via cmake-
developers:
Hello,
I wonder if any of you CMake Developers go to FOSDEM [1] this year?
I am not a CMake developer, but, more
On 26-Jan-16 12:14 AM, Stephen Kelly wrote:
Vladimir Prus wrote:
http://thread.gmane.org/gmane.comp.programming.tools.cmake.devel/12658/focus=13004
Hi Stephen,
this sounds very much like what I has proposed for Boost.Build, see:
http://vladimirprus.com/talks/boosting-cdt-builds/
Yes,
Dear CMake devs,
please find attached a patch to slightly improve FindGit.cmake.
I did test it, but did not understand why GIT_FOUND was set in the first
place.
Bye
Christoph
>From c29c384565b7d976e36156f9351af8400cd60dc4 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Christoph=20Gr=C3=BCninger?=
19 matches
Mail list logo