Re: [CMake] ninja under windows
I suspect that ninja thinks its on a posix system because you compiled it in cygwin. Try building it in a windows "terminal". I routinely use cmake and ninja on windows with the msvc toolchain and it works great but I use msys instead of cygwin. Hopefully that helps you. Frank On 8/3/2015 12:22 PM, Gonzalo Garramuño wrote: I compiled Ninja on cygwin from git. That now works fine it seems. I am trying to compile for msvc. However, when cmake runs, I get: [1/123] Building CXX object 'libACESclip\CMakeFiles\ACESclip.dir\src\ACESclipWriter.cpp.obj'ninja: fatal: unknown deps type 'msvc' $ ninja --version 1.6.0.git Is compiling under the microsoft compiler not an option for ninja files ( I can compile with NMake Makefiles just fine in the same project ). -- 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] Programmatically-generated dependencies
You will want to also make sure that a reconfigure happens when the xml file changes which can be done with the recently added CMAKE_CONFIGURE_DEPENDS property. If you need to support older versions of cmake, then you can use configure_file() to copy the xml file somewhere (no need to use it). This is unfortunate. I was hoping someone would have a better solution but it looks like the feature we want doesn't exist. http://public.kitware.com/Bug/view.php?id=2172 Frank > -Original Message- > From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of Jakub > Zakrzewski > Sent: Thursday, December 11, 2014 9:06 AM > To: ax487 > Cc: cmake@cmake.org > Subject: Re: [CMake] Programmatically-generated dependencies > > Hi, > > CMake provides functions to execute commands and capture the output. > You would use them as a part of configure step to get dependencies. > Then add_custom_command to actually generate the C file and use the > output to generate the DEPENDS section. > > -- > Gruesse, > Jakub > > > > > -Original Message- > From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of ax487 > Sent: Donnerstag, 11. Dezember 2014 15:49 > To: cmake@cmake.org > Subject: Re: [CMake] Programmatically-generated dependencies > > *bump* > > On 09.12.2014 10:38, ax487 wrote: > > Hello all, > > > > I am mainly asking having glib-compile-resources in mind. This little > > program translates files into C source code to be used with the > > gresource system. It works in the following way: You have a file.xml > > describing the resources: > > > >> prefix="/some/prefix"> > > > > some_file.txt > > > > > > > > To generate the source you use `glib-compile-resources > > --generate-source --target=output.c file.xml`. Clearly the generated > > output.c depends on file.xml. But it also depends on some_file.txt. It > > is possible to get a list of dependencies using > > `glib-compile-resources --generate-dependencies file.xml` which will > > output > > > > some_file.txt > > > > The situation is similar to the case of auto-generated header > > dependencies for C/C++ source code using the "-MM" option of gcc. > > I saw the following version on github: > > > > https://github.com/bgK/vba-ttb/blob/master/cmake/GResource.cmake > > > > which does not correctly detect dependencies, but nothing apart from > > that. But since the process works with C/C++ source code I figured > > there is no reason why it shouldn't also work in this case. Could > > anyone give me some pointers on how to get this to work? > > > > ax487 > > > -- > > 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 > -- > > 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 This communication, including any attachments, may contain information that is proprietary, privileged, confidential or legally exempt from disclosure. If you are not a named addressee, you are hereby notified that you are not authorized to read, print, retain a copy of or disseminate any portion of this communication without the consent of the sender and that doing so may be unlawful. If you have received this communication in error, please immediately notify the sender via return e-mail and delete it from your system. In order to safeguard its employee data as well as sensitive patient, customer, business, legal and other information, the company uses all lawful means, under all applicable law, to access, monitor, preserve, collect and review all communications between employees and all other users only when, and to the extent necessary, to fulfill investigatory and other important business and legal responsibilities. By responding to this communication, or initiating additional co mmunication with the company, you consent to such lawful monitoring, to the extent such consent is required and valid in your local a
Re: [CMake] Windows RC files with Ninja
I found a workaround. Turns out that the issue is caused when not enabling C language support in the project() command. i.e I was doing cmake_minimum_required( VERSION 3.0.0 ) project( proj CXX) Changing this to cmake_minimum_required( VERSION 3.0.0 ) project( proj CXX) fixes the issue. http://public.kitware.com/Bug/view.php?id=15088 Frank > -Original Message- > From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of Miller, > Frank > Sent: Tuesday, August 12, 2014 11:44 AM > To: CMake MailingList > Subject: [CMake] Windows RC files with Ninja > > Greetings, > > I tried to move from 2.8 to 3.0.1 today and I'm experiencing an issue with RC > files. Looks like a simple problem but I would be baffled if I'm the first to > experience this so I expect I have some kind of configuration issue. Here is > the offending snippet in the rules.ninja file: > > rule RC_COMPILER > depfile = $DEP_FILE > deps = gcc > command = "" RC $in "$DEP_FILE" $out "" "c:/Program Files (x86)/Microsoft > Visual Studio 12.0/VC/bin/cl.exe" > c:\PROGRA~2\WI3CF2~1\8.1\bin\x86\rc.exe $FLAGS $DEFINES /fo$out $in > description = Building RC object $out > > If I put the path to "cmcldeps.exe" in the empty quotes on the command > line, it works as expected. > > Does anyone else have this problem? > > Frank > > This communication, including any attachments, may contain information > that is proprietary, privileged, confidential or legally exempt from > disclosure. > If you are not a named addressee, you are hereby notified that you are not > authorized to read, print, retain a copy of or disseminate any portion of this > communication without the consent of the sender and that doing so may be > unlawful. If you have received this communication in error, please > immediately notify the sender via return e-mail and delete it from your > system. In order to safeguard its employee data as well as sensitive patient, > customer, business, legal and other information, the company uses all lawful > means, under all applicable law, to access, monitor, preserve, collect and > review all communications between employees and all other users only > when, and to the extent necessary, to fulfill investigatory and other > important business and legal responsibilities. By responding to this > communication, or initiating additional co > mmunication with the company, you consent to such lawful monitoring, to > the extent such consent is required and valid in your local area. > -- > > 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 This communication, including any attachments, may contain information that is proprietary, privileged, confidential or legally exempt from disclosure. If you are not a named addressee, you are hereby notified that you are not authorized to read, print, retain a copy of or disseminate any portion of this communication without the consent of the sender and that doing so may be unlawful. If you have received this communication in error, please immediately notify the sender via return e-mail and delete it from your system. In order to safeguard its employee data as well as sensitive patient, customer, business, legal and other information, the company uses all lawful means, under all applicable law, to access, monitor, preserve, collect and review all communications between employees and all other users only when, and to the extent necessary, to fulfill investigatory and other important business and legal responsibilities. By responding to this communication, or initiating additional co mmunication with the company, you consent to such lawful monitoring, to the extent such consent is required and valid in your local area. -- 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] Windows RC files with Ninja
Greetings, I tried to move from 2.8 to 3.0.1 today and I'm experiencing an issue with RC files. Looks like a simple problem but I would be baffled if I'm the first to experience this so I expect I have some kind of configuration issue. Here is the offending snippet in the rules.ninja file: rule RC_COMPILER depfile = $DEP_FILE deps = gcc command = "" RC $in "$DEP_FILE" $out "" "c:/Program Files (x86)/Microsoft Visual Studio 12.0/VC/bin/cl.exe" c:\PROGRA~2\WI3CF2~1\8.1\bin\x86\rc.exe $FLAGS $DEFINES /fo$out $in description = Building RC object $out If I put the path to "cmcldeps.exe" in the empty quotes on the command line, it works as expected. Does anyone else have this problem? Frank This communication, including any attachments, may contain information that is proprietary, privileged, confidential or legally exempt from disclosure. If you are not a named addressee, you are hereby notified that you are not authorized to read, print, retain a copy of or disseminate any portion of this communication without the consent of the sender and that doing so may be unlawful. If you have received this communication in error, please immediately notify the sender via return e-mail and delete it from your system. In order to safeguard its employee data as well as sensitive patient, customer, business, legal and other information, the company uses all lawful means, under all applicable law, to access, monitor, preserve, collect and review all communications between employees and all other users only when, and to the extent necessary, to fulfill investigatory and other important business and legal responsibilities. By responding to this communication, or initiating additional co mmunication with the company, you consent to such lawful monitoring, to the extent such consent is required and valid in your local area. -- 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] Ninja: Avoiding unnecessary rebuilds with generated files
This has been fixed.
http://www.cmake.org/Bug/view.php?id=13592
Frank
> -Original Message-
> From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On
> Behalf Of Florian Weimer
> Sent: Sunday, May 05, 2013 7:17 AM
> To: cmake@cmake.org
> Subject: [CMake] Ninja: Avoiding unnecessary rebuilds with generated files
>
> I've got a custom command which mangles a text file so that it can be linked
> into the program:
>
> add_custom_command (
> OUTPUT ${CMAKE_CURRENT_BINARY_DIR}/schema.sql.inc
> COMMAND xxd -i < ${PROJECT_SOURCE_DIR}/schema.sql >
> ${CMAKE_CURRENT_BINARY_DIR}/schema.sql.inc
> DEPENDS schema.sql
> )
>
> The generated file is then referenced from a library:
>
> add_library (SymbolDB
> lib/symboldb/database.cpp
> lib/symboldb/download.cpp
> ... (more *.cpp files)
> ${CMAKE_CURRENT_BINARY_DIR}/schema.sql.inc
> )
>
> Full CMakeLists.txt is here:
>
>
> With cmake 2.8.10, this triggers a rebuild of all the the *.cpp files listed
> above
> when schema.sql changes. But only lib/symboldb/database.cpp includes
> schema.sql.inc and therefore needs rebuilding.
>
> It seems that these unnecessary rebuilds only happen with the Ninja
> generator. I don't see it with the make generator. Could this be a bug in
> the
> Ninja generator?
> --
>
> 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
This communication, including any attachments, may contain information that is
proprietary, privileged, confidential or legally exempt from disclosure. If you
are not a named addressee, you are hereby notified that you are not authorized
to read, print, retain a copy of or disseminate any portion of this
communication without the consent of the sender and that doing so may be
unlawful. If you have received this communication in error, please immediately
notify the sender via return e-mail and delete it from your system.
--
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] How to determine the compiler used outside of cmake
Update. The reason I didn’t have CMAKE_CXX_COMPILER in my cache is because I was doing a set(CMAKE_CXX_COMPILER /usr/bin/g++44 ) at the top of my root CMakeLists.txt. That preempts the set( CACHE ) call that project() does. My bad. Frank From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf Of Miller, Frank Sent: Thursday, May 02, 2013 9:51 AM To: m.hergar...@euphoria-it.nl Cc: cmake@cmake.org Subject: Re: [CMake] How to determine the compiler used outside of cmake Interesting. I am running a very recent version (2.8.10.20130415) built from git. Perhaps the handling of CMAKE_CXX_COMPILER has changed recently. I can’t believe I didn’t think to manually put it in the cache. That will work for me. Thanks. As for the bigger problem I am solving... I have a wrapper script that drives the build. This is done to emulate a legacy build system and add some nice-to-haves. For example, the user can call the script from their source tree and it will call cmake/ninja in the proper binary tree. The default compiler to be used is hard coded into the CMakeLists.txt and I would like to have the script detect when the compiler changes and do a reconfigure automatically. Now that I’m explaining the larger problem, I think I will have to put extra information in the cache to detect when the user manually overrides the default compiler. So I probably would have come around to your suggestion on my own. Thanks again, Frank From: m.hergarden [mailto:m.hergar...@euphoria-it.nl] Sent: Thursday, May 02, 2013 12:16 AM To: Miller, Frank Cc: cmake@cmake.org<mailto:cmake@cmake.org> Subject: Re: [CMake] How to determine the compiler used outside of cmake The compiler does show up in my cache: CMAKE_CXX_COMPILER:FILEPATH=/usr/bin/c++, but that doesn't solve your issue. What is the bigger problem you are solving? If you really really need it in the cache, you can always write a variable yourself to make sure it's there. Regards, Micha On 05/01/2013 09:56 PM, Miller, Frank wrote: Greetings, Given a configured build tree, I would like to determine the c++ compiler used without reconfiguring. I expected the CMAKE_CXX_COMPILER variable would be in the CMakeCache.txt but I was wrong. I tried to run a simple cmake script with ‘cmake -P’ and print the value of CMAKE_CXX_COMPILER but that does not work. I found the value in ‘CMakeFiles/2.8.10.20130415/CMakeCXXCompiler.cmake’, so I have a workaround, but that smells like the wrong solution. Does anyone know of a better way? Thanks as always, Frank This communication, including any attachments, may contain information that is proprietary, privileged, confidential or legally exempt from disclosure. If you are not a named addressee, you are hereby notified that you are not authorized to read, print, retain a copy of or disseminate any portion of this communication without the consent of the sender and that doing so may be unlawful. If you have received this communication in error, please immediately notify the sender via return e-mail and delete it from your system. -- Powered by www.kitware.com<http://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 -- Met vriendelijke groet, Micha Hergarden [image001] Lieve Vrouweplein 9-10 5038 TS Tilburg CONTACT T+31 (0) 13 460 92 80 F+31 (0) 13 460 92 81 Em.hergar...@euphoria-it.nl<mailto:m.hergar...@euphoria-it.nl> W www.euphoria-it.nl<http://www.euphoria-it.nl/> Helpdesk: 013 - 460 92 86 Storingdienst: 06-47942098 <>-- 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] How to determine the compiler used outside of cmake
Interesting. I am running a very recent version (2.8.10.20130415) built from git. Perhaps the handling of CMAKE_CXX_COMPILER has changed recently. I can’t believe I didn’t think to manually put it in the cache. That will work for me. Thanks. As for the bigger problem I am solving... I have a wrapper script that drives the build. This is done to emulate a legacy build system and add some nice-to-haves. For example, the user can call the script from their source tree and it will call cmake/ninja in the proper binary tree. The default compiler to be used is hard coded into the CMakeLists.txt and I would like to have the script detect when the compiler changes and do a reconfigure automatically. Now that I’m explaining the larger problem, I think I will have to put extra information in the cache to detect when the user manually overrides the default compiler. So I probably would have come around to your suggestion on my own. Thanks again, Frank From: m.hergarden [mailto:m.hergar...@euphoria-it.nl] Sent: Thursday, May 02, 2013 12:16 AM To: Miller, Frank Cc: cmake@cmake.org Subject: Re: [CMake] How to determine the compiler used outside of cmake The compiler does show up in my cache: CMAKE_CXX_COMPILER:FILEPATH=/usr/bin/c++, but that doesn't solve your issue. What is the bigger problem you are solving? If you really really need it in the cache, you can always write a variable yourself to make sure it's there. Regards, Micha On 05/01/2013 09:56 PM, Miller, Frank wrote: Greetings, Given a configured build tree, I would like to determine the c++ compiler used without reconfiguring. I expected the CMAKE_CXX_COMPILER variable would be in the CMakeCache.txt but I was wrong. I tried to run a simple cmake script with ‘cmake -P’ and print the value of CMAKE_CXX_COMPILER but that does not work. I found the value in ‘CMakeFiles/2.8.10.20130415/CMakeCXXCompiler.cmake’, so I have a workaround, but that smells like the wrong solution. Does anyone know of a better way? Thanks as always, Frank This communication, including any attachments, may contain information that is proprietary, privileged, confidential or legally exempt from disclosure. If you are not a named addressee, you are hereby notified that you are not authorized to read, print, retain a copy of or disseminate any portion of this communication without the consent of the sender and that doing so may be unlawful. If you have received this communication in error, please immediately notify the sender via return e-mail and delete it from your system. -- Powered by www.kitware.com<http://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 -- Met vriendelijke groet, Micha Hergarden [image001] Lieve Vrouweplein 9-10 5038 TS Tilburg CONTACT T+31 (0) 13 460 92 80 F+31 (0) 13 460 92 81 Em.hergar...@euphoria-it.nl<mailto:m.hergar...@euphoria-it.nl> W www.euphoria-it.nl<http://www.euphoria-it.nl/> Helpdesk: 013 - 460 92 86 Storingdienst: 06-47942098 <>-- 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] How to determine the compiler used outside of cmake
Greetings, Given a configured build tree, I would like to determine the c++ compiler used without reconfiguring. I expected the CMAKE_CXX_COMPILER variable would be in the CMakeCache.txt but I was wrong. I tried to run a simple cmake script with 'cmake -P' and print the value of CMAKE_CXX_COMPILER but that does not work. I found the value in 'CMakeFiles/2.8.10.20130415/CMakeCXXCompiler.cmake', so I have a workaround, but that smells like the wrong solution. Does anyone know of a better way? Thanks as always, Frank This communication, including any attachments, may contain information that is proprietary, privileged, confidential or legally exempt from disclosure. If you are not a named addressee, you are hereby notified that you are not authorized to read, print, retain a copy of or disseminate any portion of this communication without the consent of the sender and that doing so may be unlawful. If you have received this communication in error, please immediately notify the sender via return e-mail and delete it from your system. -- 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] newbie: find_package Boost ceases to work when mixed with CLang CMAKE_TOOLCHAIN_FILE (on Ubuntu 64bit Quantal 12.10)
> Is there any better way to use clang with cmake on Ubuntu ? I do it like this cmake -DCMAKE_CXX_COMPILER=/path/to/clang++ -DCMAKE_C_COMPILER=/path/to/clang /path/to/source But you can also hard code the path to the compiler in your CMakeLists.txt. http://www.cmake.org/Wiki/CMake_Useful_Variables#Compilers_and_Tools Frank This communication, including any attachments, may contain information that is proprietary, privileged, confidential or legally exempt from disclosure. If you are not a named addressee, you are hereby notified that you are not authorized to read, print, retain a copy of or disseminate any portion of this communication without the consent of the sender and that doing so may be unlawful. If you have received this communication in error, please immediately notify the sender via return e-mail and delete it from your system. -- 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] set_target_properties called twice
I think this is intended. The semantics are the same as the set function. You
can use set_property with the APPEND or APPEND_STRING option to do what you
want.
Frank
From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf Of
Eric Clark
Sent: Tuesday, October 16, 2012 2:53 PM
To: CMake Mailing List (cmake@cmake.org)
Subject: [CMake] set_target_properties called twice
Hello,
I am currently having trouble with set_target_properties(...). I am trying to
call it twice to set two different values for the same property. The first call
I make looks like this:
set_target_properties(${PROJECT_NAME} PROPERTIES LINK_FLAGS
"/ENTRY:mainCRTStartup")
Then, I call it again with the following signature:
set_target_properties(${PROJECT_NAME} PROPERTIES LINK_FLAGS "/INCREMENTAL:NO")
When I do this, the second call seems to override the previous call. Can anyone
tell me if this is intended or a bug? And, if so, does anyone know of a
work-around for this?
Thank You,
Eric
To be fond of something is better than merely to know it, and to find joy in it
is better than merely to be fond of it. -- The Analects, Confucius
This communication, including any attachments, may contain information that is
proprietary, privileged, confidential or legally exempt from disclosure. If you
are not a named addressee, you are hereby notified that you are not authorized
to read, print, retain a copy of or disseminate any portion of this
communication without the consent of the sender and that doing so may be
unlawful. If you have received this communication in error, please immediately
notify the sender via return e-mail and delete it from your system.
--
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] [boost][b2] Differenciate 32bit and 64 bit binaries when using CMake.
A simple solution would be to install only the 64bit version of boost into a new directory and change the environment variable to point there. Then FindBoost will only be able to see the version you want. Frank From: cmake-boun...@cmake.org [cmake-boun...@cmake.org] on behalf of Klaim - Joël Lamotte [mjkl...@gmail.com] Sent: Thursday, October 11, 2012 5:16 AM To: Boost users list; cmake@cmake.org Subject: [CMake] [boost][b2] Differenciate 32bit and 64 bit binaries when using CMake. I am having a problem with b2 on Windows using Visual Studio (2010 & 2012 but it is irrelevant): Until now I was building boost with b2 in a way that would first build 32 bit version in the default library directory, then the 64bit version in lib/64 . I wasn't using the 64bit version until this morning so I didn't get any problem whatever my use of boost was. I often use Cmake these days and I set the boost environment variables for FindBoost CMake script to find it. My problem is that I'm trying now to use the 64 bit version now and CMake FindBoost script will only find the 32 bit version. CMake correctly assume that the library files in the lib directory are the one to use, however it have no apparent way to find if it is for 64 or 32 bit. Now I'm not sure how to fix this. I see two solutions but I don't see how to apply them: 1. make b2 generate lib and dll files with an additional indication on if it's 64 or 32 bit address model. I didn't find such option in b2 --help so I assume that it is not possible? 2. find a way for CMake FindBoost to automatically find the 64 bit binaries instead of the 32 bit binaris. I don't see a clear solution to achieve this, because it depends a lot on how boost have been compiled. Note: I don't want to use a default boost installation, I want to use my custom build. Any advice on how I should proceed? Thanks for your patience. Joel Lamotte This communication, including any attachments, may contain information that is proprietary, privileged, confidential or legally exempt from disclosure. If you are not a named addressee, you are hereby notified that you are not authorized to read, print, retain a copy of or disseminate any portion of this communication without the consent of the sender and that doing so may be unlawful. If you have received this communication in error, please immediately notify the sender via return e-mail and delete it from your system. -- 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] QT4_WRAP_CPP and Implicit Dependencies
Greetings,
Suppose we have a header file, Dum.h, that is included by another header
file, Main.h, and Main.h needs to be processed with the qt moc tool.
When Dum.h changes, should we rerun moc on Main.h?
QMake says yes. CMake, using QT4_WRAP_CPP, says no.
I am inclined to believe qmake on this one. However, I have yet to think
of a way to break a build by not rerunning moc. Is this a problem?
Please pardon me if you think this question is in the wrong forum. I am
asking here because I know there are a lot of qt users in this community
and qmake is clearly not doing anything wrong.
Here is a simple example:
=== CMakeLists.txt ===
cmake_minimum_required( VERSION 2.8.0 )
project( mocdep )
find_package( Qt4 REQUIRED )
include( ${QT_USE_FILE} )
include_directories( ${CMAKE_BINARY_DIR} )
QT4_WRAP_CPP( mocdep_MOCSOURCES Main.h )
add_executable( mocdep Main.cpp ${mocdep_MOCSOURCES} Main.h )
target_link_libraries( mocdep ${QT_QTCORE_LIBRARY} ${QT_QTGUI_LIBRARY} )
=== mocdep.pro ===
HEADERS = Main.h Dum.h
SOURCES = Main.cpp
=== Dum.h ===
#pragma once
=== Main.h ===
#pragma once
#include "Dum.h"
#include
class MainWindow : public QMainWindow
{
Q_OBJECT
};
=== Main.cpp ===
#include "Main.h"
#include
int main( int argc, char * argv[] )
{
QApplication app(argc, argv);
MainWindow mainWindow;
mainWindow.show();
return app.exec();
}
Frank
This communication, including any attachments, may contain information that is
proprietary, privileged, confidential or legally exempt from disclosure. If you
are not a named addressee, you are hereby notified that you are not authorized
to read, print, retain a copy of or disseminate any portion of this
communication without the consent of the sender and that doing so may be
unlawful. If you have received this communication in error, please immediately
notify the sender via return e-mail and delete it from your system.
--
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
