[CMake] Abwesenheitsnachricht: Handling of generated files in POST_BUILD custom commands
Derzeit bin ich nicht im Hause Ihre E-Mail wird nicht weitergeleitet. In dringenden Fällen bitte supp...@ditec-gmbh.de oder Telefonhotline +49-6221-31698-110 oder die Zentrale +49-6221-31698-0 kontaktieren. --- DiTEC Dr. Siegfried Kahlich & Dierk Langer GmbH Im Breitspiel 19 | 69126 Heidelberg | Germany Handelsregister | Mannheim | HRB 341229 Dieses Dokument ist vertraulich zu behandeln. Die Weitergabe, sowie Vervielfältigung, Verwertung und Mitteilung seines Inhalts ist nur mit unserer ausdrücklichen Genehmigung gestattet. Alle Rechte vorbehalten, insbesondere für den Fall der Schutzrechtsanmeldung. This document has to be treated confidentially. Its contents are not to be passed on, duplicated, exploited or disclosed without our express permission. All rights reserved, especially the right to apply for protective rights. -- 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. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake
Re: [CMake] Fixed ProjectGUID
Taking a look at the CMakeCache.txt offers the missing
${target_name}_GUID_CMAKE
variable.
Thus
set_property(CACHE ${target_name}_GUID_CMAKE PROPERTY VALUE ${MY_GUID} )
seems to work.
But how do I get the actual GUID set by CMake? This one was stored in
CMakeCache.txt before. But right know I cannot find the GUID from a generated
project file in any ccmake chache file.
How do I gain the GUID created by CMake. In my project I just store the new
GUIDs created by CMake in a file. Next time I build the project file I'm
looking if a GUID was already generated for that project an will use that one.
Best regards,
SirAnn
Am 08.12.2015 um 11:25 schrieb Dr. Sören Textor:
Hello
I just installed 3.4.1 and the usage of a hardcoded guid does not seem to work
anymore:
set_property(CACHE ${target_name}_GUID_CMAKE PROPERTY VALUE ${MY_GUID} )
Is thre another way to set the project GUID?
best regards
SirAnn
Original-Nachricht
>/Datum: Fri, 7 Jan 2011 22:26:31 +0100 />/Von: Pau Garcia i Quiles <http://www.cmake.org/mailman/listinfo/cmake>> />/An: David Cole <http://www.cmake.org/mailman/listinfo/cmake>> />/CC: "Sören Freudiger" <http://www.cmake.org/mailman/listinfo/cmake>>, cmake at cmake.org
<http://www.cmake.org/mailman/listinfo/cmake> />/Betreff: Re: [CMake] Fixed ProjectGUID /
>/Hello, />//>/In Visual Studio 2010, ProjectGUID is a global. This bug provides a />/patch to add global definitions to CMake, but only up to Visual Studio />/2008. It shouldn't be difficult to update the patch to add support for />/Visual C++ 2010. Setting the ProjectGUID would then be as easy as: />//>/set_target_properties( thetarget PROPERTIES VS_GLOBAL_ProjectGUID />/"{384A545C-A6F2-4833-9260-F05C46557610}" ) />//>/I opened the bug and provided the code almost two years ago, so it's />/not like I expect CMake developers to suddenly implement it... />//>/2011/1/7 David Cole <http://www.cmake.org/mailman/listinfo/cmake>>: />/> The guids should remain constant in a given build tree for the life of />/the />/> CMakeCache.txt file. />/> />/> But after you delete that and start in a fresh build tree, you'll get />/fresh />/> guids. />/> />/> If you want constant guids in your vcproj files, they should be
built by />/> hand, not with CMake. />/> />/> />/> HTH, />/> David />/> />/> />/> 2011/1/7 "Sören Freudiger" <http://www.cmake.org/mailman/listinfo/cmake>> />/>> />/>> Hello />/>> Is it possible to set the ProjectGUID by CMake? Every time I
generate a />/>> vcproj file with CMake the ProjectGUID changes. But we need to have a />/fixed />/>> one (because other projects are including the vcproj). />/>> />/>> Best regards />/>> SirAnn />/>> -- />/>> GMX DSL Doppel-Flat ab 19,99 Euro/mtl.! Jetzt mit />/>> gratis Handy-Flat! http://portal.gmx.net/de/go/dsl />/>> ___ />/>> Powered by www.kitware.com />/>> />/>> Visit other Kitware open-source projects at />/>> http://www.kitware.com/opensource/opensource.html />/>> />/>> Please keep messages on-topic and check the CMake FAQ at: />/>> http://www.cmake.org/Wiki/CMake_FAQ />/>> />/>> Follow this link to subscribe/unsubscribe: />/>> http://www.cmake.org/mailman/listinfo/cmake />/> />/> />/> ___ />/> Powered by www.kitware.com />/> />/> Visit other Kitware open-source projects at />/> http://www.kitware.com/opensource/opensource.html />/> />/> Please keep messages on-topic and check the CMake FAQ at: />/> http://www.cmake.org/Wiki/CMake_FAQ />/> />/> Follow this link to subscribe/unsubscribe: />/> http://www.cmake.org/mailman/listinfo/cmake />/> />//>//>//>/-- />/Pau Garcia i Quiles />/http://www.elpauer.org <http://www.elpauer.org/> />/(Due to my workload, I may need 10 days to answer) /
--
NEU: FreePhone - kostenlos mobil telefonieren und surfen!
Jetzt informieren:http://www.gmx.net/de/go/freephone
--
Dr.-Ing. Sören Textor
Softwareentwicklung
phone | +49 6221 31698 225
fax | +49 6221 31698 399
email | s.tex...@ditec-gmbh.de <mailto:s.tex...@ditec-gmbh.de>
web | http://www.ditec-gmbh.de
DiTEC Dr. Siegfried Kahlich & Dierk Langer GmbH
Im Breitspiel 19 | 69126 Heidelberg | Germany
Handelsregister | Mannheim | HRB 341229
Dieses Dokument ist vertraulich zu behandeln. Die Weitergabe, sowie
Vervielfältigung, Verwertung und Mitteilung seines Inhalts ist nur mit
unserer ausdrücklichen Ge
[CMake] Fixed ProjectGUID
Hello
I just installed 3.4.1 and the usage of a hardcoded guid does not seem to work
anymore:
set_property(CACHE ${target_name}_GUID_CMAKE PROPERTY VALUE ${MY_GUID} )
Is thre another way to set the project GUID?
best regards
SirAnn
Original-Nachricht
/Datum: Fri, 7 Jan 2011 22:26:31 +0100 />/Von: Pau Garcia i Quiles > />/An: David Cole > />/CC: "Sören Freudiger" >, cmake at cmake.org
/>/Betreff: Re: [CMake] Fixed ProjectGUID /
/Hello, />//>/In Visual Studio 2010, ProjectGUID is a global. This bug provides a />/patch to add global definitions to CMake, but only up to Visual Studio />/2008. It shouldn't be difficult to update the patch to add support for />/Visual C++ 2010. Setting the ProjectGUID would then be as easy as: />//>/set_target_properties( thetarget PROPERTIES VS_GLOBAL_ProjectGUID />/"{384A545C-A6F2-4833-9260-F05C46557610}" ) />//>/I opened the bug and provided the code almost two years ago, so it's />/not like I expect CMake developers to suddenly implement it... />//>/2011/1/7 David Cole >: />/ > The guids should remain constant in a given build tree for the life of />/the />/ > CMakeCache.txt file. />/ > />/ > But after you delete that and start in a fresh build tree, you'll get />/fresh />/ > guids. />/ > />/ > If you want constant guids in your vcproj files, they should be built
by />/ > hand, not with CMake. />/ > />/ > />/ > HTH, />/ > David />/ > />/ > />/ > 2011/1/7 "Sören Freudiger" > />/ >> />/ >> Hello />/ >> Is it possible to set the ProjectGUID by CMake? Every time I
generate a />/ >> vcproj file with CMake the ProjectGUID changes. But we need to have a />/fixed />/ >> one (because other projects are including the vcproj). />/ >> />/ >> Best regards />/ >> SirAnn />/ >> -- />/ >> GMX DSL Doppel-Flat ab 19,99 Euro/mtl.! Jetzt mit />/ >> gratis Handy-Flat! http://portal.gmx.net/de/go/dsl />/ >> ___ />/ >> Powered by www.kitware.com />/ >> />/ >> Visit other Kitware open-source projects at />/ >> http://www.kitware.com/opensource/opensource.html />/ >> />/ >> Please keep messages on-topic and check the CMake FAQ at: />/ >> http://www.cmake.org/Wiki/CMake_FAQ />/ >> />/ >> Follow this link to subscribe/unsubscribe: />/ >> http://www.cmake.org/mailman/listinfo/cmake />/ > />/ > />/ > ___ />/ > Powered by www.kitware.com />/ > />/ > Visit other Kitware open-source projects at />/ > http://www.kitware.com/opensource/opensource.html />/ > />/ > Please keep messages on-topic and check the CMake FAQ at: />/ > http://www.cmake.org/Wiki/CMake_FAQ />/ > />/ > Follow this link to subscribe/unsubscribe: />/ > http://www.cmake.org/mailman/listinfo/cmake />/ > />//>//>//>/-- />/Pau Garcia i Quiles />/http://www.elpauer.org
Re: [CMake] Fixed ProjectGUID
Yes, it seems that cmake does not store that ID as befere. Thus I just
create my own UUID ;-)
String( UUID ...)
Am 08.12.2015 um 12:28 schrieb Nils Gladitz:
On 12/08/2015 12:06 PM, Dr. Sören Textor wrote:
Taking a look at the CMakeCache.txt offers the missing
${target_name}_GUID_CMAKE
variable.
Thus
set_property(CACHE ${target_name}_GUID_CMAKE PROPERTY VALUE ${MY_GUID} )
seems to work.
But how do I get the actual GUID set by CMake? This one was stored in
CMakeCache.txt before. But right know I cannot find the GUID from a generated
project file in any ccmake chache file.
How do I gain the GUID created by CMake. In my project I just store the new
GUIDs created by CMake in a file. Next time I build the project file I'm
looking if a GUID was already generated for that project an will use that one.
See https://cmake.org/gitweb?p=cmake.git;a=commit;h=c85367f4
I don't think cmake exposes the GUID that it uses anymore but you
should still be able to provide your own.
Nils
--
Dr.-Ing. Sören Textor
Softwareentwicklung
phone | +49 6221 31698 225
fax | +49 6221 31698 399
email | s.tex...@ditec-gmbh.de <mailto:s.tex...@ditec-gmbh.de>
web | http://www.ditec-gmbh.de
DiTEC Dr. Siegfried Kahlich & Dierk Langer GmbH
Im Breitspiel 19 | 69126 Heidelberg | Germany
Handelsregister | Mannheim | HRB 341229
Dieses Dokument ist vertraulich zu behandeln. Die Weitergabe, sowie
Vervielfältigung, Verwertung und Mitteilung seines Inhalts ist nur mit
unserer ausdrücklichen Genehmigung gestattet. Alle Rechte vorbehalten,
insbesondere für den Fall der Schutzrechtsanmeldung.
This document has to be treated confidentially. Its contents are not to
be passed on, duplicated, exploited or disclosed without our express
permission. All rights reserved, especially the right to apply for
protective rights.
--
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. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake
[CMake] compile flags per configuration in 3.2?
Hello Since cmake 2.0 I would like to have the possibilty to add compile flags for certain configurations. For linker flags it runs very well with set_targer_properties and LINK_FLAGS_CONFIG. But that doesn't wokr for the compile flags. Exits a possibility in 3.2 meanwhile? Best regards, SirAnn -- 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. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
Re: [CMake] compile flags per configuration in 3.2?
No, you are dealing with the global flag. But that's not the way I want to go, because I have several targets and need serveral compile flags for each target Am 23.03.2015 um 14:03 schrieb Parag Chandra: Have you looked at CMAKE_LANG_FLAGS_CONFIG, e.g. http://www.cmake.org/cmake/help/v3.1/variable/CMAKE_LANG_FLAGS_DEBUG.html I’ve been using these for exactly the purpose you describe. *Parag Chandra *Senior Software Engineer, Mobile Team Mobile: +1.919.824.1410 https://ionic.com Ionic Security Inc. 1170 Peachtree St. NE STE 400, Atlanta, GA 30309 From: Dr. Sören Textor soeren.tex...@ditec-gmbh.de mailto:soeren.tex...@ditec-gmbh.de Organization: DiTEC GmbH Date: Monday, March 23, 2015 at 8:39 AM To: cmake@cmake.org mailto:cmake@cmake.org cmake@cmake.org mailto:cmake@cmake.org Subject: [CMake] compile flags per configuration in 3.2? Hello Since cmake 2.0 I would like to have the possibilty to add compile flags for certain configurations. For linker flags it runs very well with set_targer_properties and LINK_FLAGS_CONFIG. But that doesn't wokr for the compile flags. Exits a possibility in 3.2 meanwhile? Best regards, SirAnn -- Dr.-Ing. Sören Textor Softwareentwicklung phone | +49 6221 31698 225 fax | +49 6221 31698 399 email | s.tex...@ditec-gmbh.de mailto:s.tex...@ditec-gmbh.de web | http://www.ditec-gmbh.de DiTEC Dr. Siegfried Kahlich Dierk Langer GmbH Im Breitspiel 19 | 69126 Heidelberg | Germany Handelsregister | Mannheim | HRB 341229 Dieses Dokument ist vertraulich zu behandeln. Die Weitergabe, sowie Vervielfältigung, Verwertung und Mitteilung seines Inhalts ist nur mit unserer ausdrücklichen Genehmigung gestattet. Alle Rechte vorbehalten, insbesondere für den Fall der Schutzrechtsanmeldung. This document has to be treated confidentially. Its contents are not to be passed on, duplicated, exploited or disclosed without our express permission. All rights reserved, especially the right to apply for protective rights. -- 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. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
[CMake] SET_TARGET_PROPERTIES( xx LINK_FLAGS -MAP:mymap.map) vcxproj error
Hello SET_TARGET_PROPERTIES( myProj PROPERTIES LINK_FLAGS -MAP:mymapfile.map) and also SET_TARGET_PROPERTIES( myProj PROPERTIES LINK_FLAGS /MAP:mymapfile.map) results in MapFileName:ficken.amp/MapFileName inside the vcxproj files and leads within VS2012 to compile/link errors, because the leading ':' is incorrect. The error seems to belong since cmake contains a vcxproj generator. I've tested cmake 2.8.9, 2.8.10.2, 2.8.11, 2.8.11.2. Is it a bug (I sumited one to http://www.cmake.org/Bug/view.php?id=14282 or only my fault? Best SirAnn http://www.cmake.org/Bug/view.php?id=14282 -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] add_target_properties( tgt COMPILE_FLAGS_${CONF} abc )
okay, it seems that there's a missunderstanding.
The thing I want to do is this:
add_target_properties( ${tgt} COMPILE_FLAGS_DEBUG /GA )
add_target_properties( ${tgt} COMPILE_FLAGS_RELEASE /GB )
add_target_properties( ${tgt} COMPILE_FLAGS_MYCONFIG1 /GC )
add_target_properties( ${tgt} COMPILE_FLAGS_MYCONFIG1 /GD )
like I do already:
add_target_properties( ${tgt} LINK_FLAGS_DEBUG /Libpath:xxx1 )
add_target_properties( ${tgt} LINK_FLAGS_RELEASE /Libpath:xxx2 )
add_target_properties( ${tgt} LINK_FLAGS_MYCONFIG1 /Libpath:xxx3 )
add_target_properties( ${tgt} LINK_FLAGS_MYCONFIG1 /Libpath:xxx4 )
The latter orks fine. Thus why it's not possible to obtain the same
functionaltity for compile flags?
SirAnn
protective rights.
Am 26.06.2013 00:39, schrieb Leek, Jim:
I was just messing around with this yesterday. On minGW I had to pass the link
flag -static-libgcc to my binary. There were two ways to do this:
1) To add a flag to all link lines:
Shared Libraries:
SET (CMAKE_SHARED_LINKER_FLAGS abc
CACHE STRING Flags used by the linker during the creation of dll's.)
module linker flags:
SET (CMAKE_MODULE_LINKER_FLAGS abc
CACHE STRING Flags used by the linker during the creation of modules.)
binary linker flags:
SET (CMAKE_EXE_LINKER_FLAGS abc
CACHE STRING Flags used by the linker during the creation of binaries.)
2) To add a flag to just a single target:
SET_TARGET_PROPERTIES( target name
PROPERTIES
LINK_FLAGS abc)
If just used if statement to decide if how the link flags should be set. There
may be a better way to do that.
To see how to do configuration based compile flags, see this page:
http://www.cmake.org/Wiki/CMake_Useful_Variables
I added a TESTING build type, and all I had to do was define these variables:
SET(CMAKE_CXX_FLAGS_TESTING -mfpmath=sse -msse2)
SET(CMAKE_C_FLAGS_TESTING -mfpmath=sse -msse2)
SET(CMAKE_Fortran_FLAGS_TESTING -mfpmath=sse -msse2)
-Original Message-
From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf Of
Miller Henry
Sent: Tuesday, June 25, 2013 8:41 AM
To: Sören Textor [Ditec-GmbH]; cmake@cmake.org
Subject: Re: [CMake] add_target_properties( tgt COMPILE_FLAGS_${CONF} abc )
TARGET_LINK_LIBRARIES(${tgt} stdc++)
Should do the trick
-Original Message-
From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf Of Sören
Textor [Ditec-GmbH]
Sent: Tuesday, June 25, 2013 10:15 AM
To: cmake@cmake.org
Subject: [CMake] add_target_properties( tgt COMPILE_FLAGS_${CONF} abc )
Hello
Is it meanwhile possible to add configuration specfic compiler flags analouge
to link flags?
add_target_properties( ${tgt} COMPILE_FLAGS_${CONF} abc )
add_target_properties( ${tgt} LINK_FLAGS_${CONF} abc )
Best regards
SirAnn
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] add_target_properties( tgt COMPILE_FLAGS_${CONF} abc )
sorry my fault.
add_target_properties is a helper macro that I wrote.
Finally this is what I need:
set_target_properties( ${tgt} COMPILE_FLAGS_DEBUG /GA )
set_target_properties( ${tgt} COMPILE_FLAGS_RELEASE /GB )
set_target_properties( ${tgt} COMPILE_FLAGS_MYCONFIG1 /GC )
set_target_properties( ${tgt} COMPILE_FLAGS_MYCONFIG1 /GD )
And this is what already works:
set_target_properties( ${tgt} LINK_FLAGS_DEBUG /Libpath:xxx1 )
set_target_properties( ${tgt} LINK_FLAGS_RELEASE /Libpath:xxx2 )
set_target_properties( ${tgt} LINK_FLAGS_MYCONFIG1 /Libpath:xxx3 )
set_target_properties( ${tgt} LINK_FLAGS_MYCONFIG1 /Libpath:xxx4 )
Am 26.06.2013 09:07, schrieb Sören Textor [Ditec-GmbH]:
okay, it seems that there's a missunderstanding.
The thing I want to do is this:
add_target_properties( ${tgt} COMPILE_FLAGS_DEBUG /GA )
add_target_properties( ${tgt} COMPILE_FLAGS_RELEASE /GB )
add_target_properties( ${tgt} COMPILE_FLAGS_MYCONFIG1 /GC )
add_target_properties( ${tgt} COMPILE_FLAGS_MYCONFIG1 /GD )
like I do already:
add_target_properties( ${tgt} LINK_FLAGS_DEBUG /Libpath:xxx1 )
add_target_properties( ${tgt} LINK_FLAGS_RELEASE /Libpath:xxx2 )
add_target_properties( ${tgt} LINK_FLAGS_MYCONFIG1 /Libpath:xxx3 )
add_target_properties( ${tgt} LINK_FLAGS_MYCONFIG1 /Libpath:xxx4 )
The latter orks fine. Thus why it's not possible to obtain the same
functionaltity for compile flags?
SirAnn
protective rights.
Am 26.06.2013 00:39, schrieb Leek, Jim:
I was just messing around with this yesterday. On minGW I had to pass the link
flag -static-libgcc to my binary. There were two ways to do this:
1) To add a flag to all link lines:
Shared Libraries:
SET (CMAKE_SHARED_LINKER_FLAGS abc
CACHE STRING Flags used by the linker during the creation of dll's.)
module linker flags:
SET (CMAKE_MODULE_LINKER_FLAGS abc
CACHE STRING Flags used by the linker during the creation of modules.)
binary linker flags:
SET (CMAKE_EXE_LINKER_FLAGS abc
CACHE STRING Flags used by the linker during the creation of binaries.)
2) To add a flag to just a single target:
SET_TARGET_PROPERTIES( target name
PROPERTIES
LINK_FLAGS abc)
If just used if statement to decide if how the link flags should be set. There
may be a better way to do that.
To see how to do configuration based compile flags, see this page:
http://www.cmake.org/Wiki/CMake_Useful_Variables
I added a TESTING build type, and all I had to do was define these variables:
SET(CMAKE_CXX_FLAGS_TESTING -mfpmath=sse -msse2)
SET(CMAKE_C_FLAGS_TESTING -mfpmath=sse -msse2)
SET(CMAKE_Fortran_FLAGS_TESTING -mfpmath=sse -msse2)
-Original Message-
From:cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf Of
Miller Henry
Sent: Tuesday, June 25, 2013 8:41 AM
To: Sören Textor [Ditec-GmbH];cmake@cmake.org
Subject: Re: [CMake] add_target_properties( tgt COMPILE_FLAGS_${CONF} abc )
TARGET_LINK_LIBRARIES(${tgt} stdc++)
Should do the trick
-Original Message-
From:cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf Of Sören
Textor [Ditec-GmbH]
Sent: Tuesday, June 25, 2013 10:15 AM
To:cmake@cmake.org
Subject: [CMake] add_target_properties( tgt COMPILE_FLAGS_${CONF} abc )
Hello
Is it meanwhile possible to add configuration specfic compiler flags analouge
to link flags?
add_target_properties( ${tgt} COMPILE_FLAGS_${CONF} abc )
add_target_properties( ${tgt} LINK_FLAGS_${CONF} abc )
Best regards
SirAnn
--
Powered bywww.kitware.com
Visit other Kitware open-source projects
athttp://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ
at:http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
--
Powered bywww.kitware.com
Visit other Kitware open-source projects
athttp://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ
at:http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] add_target_properties( tgt COMPILE_FLAGS_${CONF} abc )
problem is that config specific propierties like
COMPILE_FLAGS_DEBUG
still seems not to be evaluated.
Instead of specific link propierties!
Am 26.06.2013 13:41, schrieb Leek, Jim:
Sorry, I don't have a nice clean answer like that for you. I'm too
new at cmake I guess. I would just fall back on if statements.
If(CMAKE_BUILD_TYPE MATCHES Debug)
set_target_properties( ${tgt} COMPILE_FLAGS_DEBUG /GA )
elseif(CMAKE_BUILD_TYPE MATCHES Release)
...
endif()
*From:*cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] *On
Behalf Of *Sören Textor [Ditec-GmbH]
*Sent:* Wednesday, June 26, 2013 12:28 AM
*To:* cmake@cmake.org
*Subject:* Re: [CMake] add_target_properties( tgt
COMPILE_FLAGS_${CONF} abc )
sorry my fault.
add_target_properties is a helper macro that I wrote.
Finally this is what I need:
set_target_properties( ${tgt} COMPILE_FLAGS_DEBUG /GA )
set_target_properties( ${tgt} COMPILE_FLAGS_RELEASE /GB )
set_target_properties( ${tgt} COMPILE_FLAGS_MYCONFIG1 /GC )
set_target_properties( ${tgt} COMPILE_FLAGS_MYCONFIG1 /GD )
And this is what already works:
set_target_properties( ${tgt} LINK_FLAGS_DEBUG /Libpath:xxx1 )
set_target_properties( ${tgt} LINK_FLAGS_RELEASE /Libpath:xxx2 )
set_target_properties( ${tgt} LINK_FLAGS_MYCONFIG1 /Libpath:xxx3 )
set_target_properties( ${tgt} LINK_FLAGS_MYCONFIG1 /Libpath:xxx4 )
Am 26.06.2013 09:07, schrieb Sören Textor [Ditec-GmbH]:
okay, it seems that there's a missunderstanding.
The thing I want to do is this:
add_target_properties( ${tgt} COMPILE_FLAGS_DEBUG /GA )
add_target_properties( ${tgt} COMPILE_FLAGS_RELEASE /GB )
add_target_properties( ${tgt} COMPILE_FLAGS_MYCONFIG1 /GC )
add_target_properties( ${tgt} COMPILE_FLAGS_MYCONFIG1 /GD )
like I do already:
add_target_properties( ${tgt} LINK_FLAGS_DEBUG /Libpath:xxx1 )
add_target_properties( ${tgt} LINK_FLAGS_RELEASE /Libpath:xxx2 )
add_target_properties( ${tgt} LINK_FLAGS_MYCONFIG1 /Libpath:xxx3 )
add_target_properties( ${tgt} LINK_FLAGS_MYCONFIG1 /Libpath:xxx4 )
The latter orks fine. Thus why it's not possible to obtain the same
functionaltity for compile flags?
SirAnn
protective rights.
Am 26.06.2013 00:39, schrieb Leek, Jim:
I was just messing around with this yesterday. On minGW I had to pass
the link flag -static-libgcc to my binary. There were two ways to do this:
1) To add a flag to all link lines:
Shared Libraries:
SET (CMAKE_SHARED_LINKER_FLAGS abc
CACHE STRING Flags used by the linker during the creation of
dll's.)
module linker flags:
SET (CMAKE_MODULE_LINKER_FLAGS abc
CACHE STRING Flags used by the linker during the creation of
modules.)
binary linker flags:
SET (CMAKE_EXE_LINKER_FLAGS abc
CACHE STRING Flags used by the linker during the creation of
binaries.)
2) To add a flag to just a single target:
SET_TARGET_PROPERTIES( target name
PROPERTIES
LINK_FLAGS abc)
If just used if statement to decide if how the link flags should be
set. There may be a better way to do that.
To see how to do configuration based compile flags, see this page:
http://www.cmake.org/Wiki/CMake_Useful_Variables
I added a TESTING build type, and all I had to do was define these
variables:
SET(CMAKE_CXX_FLAGS_TESTING -mfpmath=sse -msse2)
SET(CMAKE_C_FLAGS_TESTING -mfpmath=sse -msse2)
SET(CMAKE_Fortran_FLAGS_TESTING -mfpmath=sse -msse2)
-Original Message-
From:cmake-boun...@cmake.org mailto:cmake-boun...@cmake.org
[mailto:cmake-boun...@cmake.org] On Behalf Of Miller Henry
Sent: Tuesday, June 25, 2013 8:41 AM
To: Sören Textor [Ditec-GmbH];cmake@cmake.org
mailto:cmake@cmake.org
Subject: Re: [CMake] add_target_properties( tgt COMPILE_FLAGS_${CONF}
abc )
TARGET_LINK_LIBRARIES(${tgt} stdc++)
Should do the trick
-Original Message-
From:cmake-boun...@cmake.org mailto:cmake-boun...@cmake.org
[mailto:cmake-boun...@cmake.org] On Behalf Of Sören Textor [Ditec-GmbH]
Sent: Tuesday, June 25, 2013 10:15 AM
To:cmake@cmake.org mailto:cmake@cmake.org
Subject: [CMake] add_target_properties( tgt COMPILE_FLAGS_${CONF} abc
)
Hello
Is it meanwhile possible to add configuration specfic compiler flags
analouge to link flags?
add_target_properties( ${tgt} COMPILE_FLAGS_${CONF} abc )
add_target_properties( ${tgt} LINK_FLAGS_${CONF} abc )
Best regards
SirAnn
Re: [CMake] Disable parallel build under windows
just remove//the flag /MP from CMAKE_CXX_FLAGS Am 26.06.2013 16:01, schrieb ycollette.nos...@free.fr: Hello, In a directory, I build some ExternalProjects. Under windows, if I use the NMake Makefiles generator, the build is sequential (thanks to nmake which doesn't understand parallel build). But if I generate a Visual Studio solution, the external projects are build in parallel. I would like to forbid the parallel build in my ExternalProjects directory. Is it possible to do via cmake ? Best regards, YC -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] Disable Warning: Manually-specified variables were not used by the project
Hello Is it possible to disable the warning: Manually-specified variables were not used by the project? This warning is nice, but in my case I'm not interessted in and I know that I put some unused variables for certain circumstances. Best SirAnn -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] CMake 2.8.9 missing ProjectGUID in vcproj of VS .NET 2003
Hi David, Hi Bill The GUID ist part of the vcproj by design. Of course we can use 2.8.7 to fix that problem. But in my eyes it would make sense to fix that problem in future releases of cmake. It's just changing if(this-Version = VS8) into if(this-Version = VS7) Thus: it's not a show stopping thing, but a nice to have one ;-) Thanks for quick reply, SirAnn Am 04.09.2012 22:12, schrieb Bill Hoffman: On 9/4/2012 2:53 PM, David Cole wrote: The value of this-Version used to be 71 for Visual Studio 7.1, and the ProjectGUID chunk was unintentionally generated since 71 8. When the version number values were fixed so that this-Version could properly be compared, this code started having its always intended effect: only generate the ProjectGUID entry for VS 8 and above... Is this a show-stopping problem for you, or can you adapt your post-build rules to work with CMake 2.8.7 and later...? But if 7.1 works with GUID's maybe they should just be there all the time? The only reason I would see for leaving them out is that it breaks something. -- Mit freundlichen Grüßen Dr.-Ing. Sören Textor DiTEC Dr. Siegfried Kahlich Dierk Langer GmbH 69126 Heidelberg, Im Breitspiel 19, Germany Fon : (+49) 06221/31698-225 Fax : (+49) 06221/31698-399 Mail : s.tex...@ditec-gmbh.de Handelsregister : HRB 341223 USt-IdNr. : DE 172 101 757 Dieses Dokument ist vertraulich zu behandeln. Die Weitergabe, sowie Vervielfältigung, Verwertung und Mitteilung seines Inhalts ist nur mit unserer ausdrücklichen Genehmigung gestattet. Alle Rechte vorbehalten, insbesondere für den Fall der Schutzrechtsanmeldung. This document has to be treated confidentially. Its contents are not to be passed on, duplicated, exploited or disclosed without our express permission. All rights reserved, especially the right to apply for protective rights. -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] CMake 2.8.9 missing ProjectGUID in vcproj of VS .NET 2003
Hi What's the reason to neglect the ProjectGUID entry inside the generated vcproj-file at the VS .Net 2003 configuration since 2.8.9? Best regards SirAnn -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] CMake 2.8.9 missing ProjectGUID in vcproj of VS .NET 2003
We used CMake 2.8.3 and 2.8.5. But since 2.8.9 the ProjectGUID is missing in the generated vcproj files (VS 2003 .NET). We only have problems with some postbuild tools that are searching for that GUID inside the project file. The GUID ist still inside the sln and inside the VS 2008, 2010 and 2012 vcproj(x) files. (we only use 203 .Net, 2008, 2010 and 2012 VS 32 bit generators). Thus something has been changed inside the vs 2003 .Net generator.. You can reproduce the problem by generate a VS 2003 project and one 2008 project. Comparing the vcproj files shows the missing ProjectGUID entry. Best regards SirAnn Am 04.09.2012 13:19, schrieb David Cole: We did not change anything related to that in 2.8.9 to the best of my knowledge... What problem do you have now that you didn't have before? (Can I reproduce your problem here...?) Thanks, David On Tue, Sep 4, 2012 at 3:46 AM, Sören Textor s.tex...@ditec-gmbh.de wrote: Hi What's the reason to neglect the ProjectGUID entry inside the generated vcproj-file at the VS .Net 2003 configuration since 2.8.9? Best regards SirAnn -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake -- Mit freundlichen Grüßen Dr.-Ing. Sören Textor DiTEC Dr. Siegfried Kahlich Dierk Langer GmbH 69126 Heidelberg, Im Breitspiel 19, Germany Fon : (+49) 06221/31698-225 Fax : (+49) 06221/31698-399 Mail : s.tex...@ditec-gmbh.de Handelsregister : HRB 341223 USt-IdNr. : DE 172 101 757 Dieses Dokument ist vertraulich zu behandeln. Die Weitergabe, sowie Vervielfältigung, Verwertung und Mitteilung seines Inhalts ist nur mit unserer ausdrücklichen Genehmigung gestattet. Alle Rechte vorbehalten, insbesondere für den Fall der Schutzrechtsanmeldung. This document has to be treated confidentially. Its contents are not to be passed on, duplicated, exploited or disclosed without our express permission. All rights reserved, especially the right to apply for protective rights. -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
