Re: [cmake-developers] [PATCH] Added very basic Windows CE Makefile support
Hi,
On Tue, 04 Sep 2012 16:39:44 -0400, Brad King wrote:
On 09/04/2012 04:18 PM, Patrick Gansterer wrote:
I rebased the code and pushed it as ce to
https://gitorious.org/~paroga/cmake/parogas-cmake
(git://gitorious.org/~paroga/cmake/parogas-cmake.git)
Thanks! I'm looking at the first commit that adds the WindowsCE
platform files. These lines look strange:
set(MSVC_C_ARCHITECTURE_ID ${CMAKE_SYSTEM_PROCESSOR})
set(MSVC_CXX_ARCHITECTURE_ID ${CMAKE_SYSTEM_PROCESSOR})
Normally the ARCHITECTURE_ID values are detected by
Modules/CMakePlatformId.h.in
which is built by running CMAKE_(C|CXX)_COMPILER, which should
be set by the toolchain file to the proper compiler for WinCE.
Shouldn't that be taught about the architectures in question?
Thanks for the feedback. I've updated my changes and pushed it to the
same branch.
-- Patrick
--
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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
[cmake-developers] [CMake 0013515]: ExternalProject doesn’t handle .tar.xz
The following issue has been SUBMITTED. == http://public.kitware.com/Bug/view.php?id=13515 == Reported By:Joke de Buhr Assigned To: == Project:CMake Issue ID: 13515 Category: CMake Reproducibility:always Severity: feature Priority: normal Status: new == Date Submitted: 2012-09-05 05:28 EDT Last Modified: 2012-09-05 05:28 EDT == Summary:ExternalProject doesn’t handle .tar.xz Description: ExternalProject doesn’t handle .tar.xz archives. Cmake however knows how to extract .tar.xz archives. So ExternalProject should pass arguments to cmake. Steps to Reproduce: ExternalProject_Add(libgnutls URL http://ftp.gnu.org/gnu/gnutls/gnutls-3.1.1.tar.xz ... ) Additional Information: Some external projects (like gnutls) do not provide tar.gz or tar.bz2 archives any more. == Issue History Date ModifiedUsername FieldChange == 2012-09-05 05:28 Joke de Buhr New Issue 2012-09-05 05:28 Joke de Buhr File Added: ExternalProject.cmake.patch == -- 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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
[cmake-developers] [CMake 0013516]: When generating Xcode Projects certain warnings are always enabled (-Wmost)
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=13516
==
Reported By:Frank Bergmann
Assigned To:
==
Project:CMake
Issue ID: 13516
Category: CMake
Reproducibility:always
Severity: minor
Priority: normal
Status: new
==
Date Submitted: 2012-09-05 06:10 EDT
Last Modified: 2012-09-05 06:10 EDT
==
Summary:When generating Xcode Projects certain warnings are
always enabled (-Wmost)
Description:
Looking at cmGlobalXCodeGenerator.cxx, I find that the option -Wmost is always
enabled. It would be better if this option would be configurable. When this
option is specified, all the fine grained settings that can be set in Xcode are
always overwritten. Because of the way that this option is added in the
generator, no post processing step will allow me to remove them:
this-CreateString(NO));
if (this-XcodeVersion = 30)
{
cmXCodeObject *group = this-CreateObject(cmXCodeObject::OBJECT_LIST);
group-AddObject(this-CreateString(-Wmost));
group-AddObject(this-CreateString(-Wno-four-char-constants));
group-AddObject(this-CreateString(-Wno-unknown-pragmas));
buildSettings-AddAttribute(WARNING_CFLAGS, group);
}
else
{
buildSettings-AddAttribute(WARNING_CFLAGS,
this-CreateString(
-Wmost -Wno-four-char-constants
-Wno-unknown-pragmas));
}
Steps to Reproduce:
- take any cmake project and generate xcode projects with it. they all will have
WARNING_CFLAGS set with -Wmost.
- even warnings turned off in xcode (like functions hiding overloaded virtual
functions) will still be issued
==
Issue History
Date ModifiedUsername FieldChange
==
2012-09-05 06:10 Frank Bergmann New Issue
==
--
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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] ninja test failing again...
On 09/04/2012 07:46 PM, Peter Kümmel wrote: Any optimization that skips dependency checks should be done only for the first form, and never for the second form. This distinction should cover the BuildDepends test case too. http://cmake.org/gitweb?p=stage/cmake.git;a=commitdiff;h=34b0cf6a3823e0d54958a0f337308b4c35342cc3 Is this better? Yes, thanks. Please revert the other topic and merge this one instead. -Brad -- 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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] ninja test failing again...
On 05.09.2012 13:31, Brad King wrote: On 09/04/2012 07:46 PM, Peter Kümmel wrote: Any optimization that skips dependency checks should be done only for the first form, and never for the second form. This distinction should cover the BuildDepends test case too. http://cmake.org/gitweb?p=stage/cmake.git;a=commitdiff;h=34b0cf6a3823e0d54958a0f337308b4c35342cc3 Is this better? Yes, thanks. Please revert the other topic and merge this one instead. OK, I merged this: http://cmake.org/gitweb?p=stage/cmake.git;a=commitdiff;h=7b2bf28e183b5eacc22fe3030f0439853746f0bd -Brad -- 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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
[cmake-developers] [CMake 0013517]: Add FindIconv module
The following issue has been SUBMITTED. == http://public.kitware.com/Bug/view.php?id=13517 == Reported By:Steven Oliver Assigned To: == Project:CMake Issue ID: 13517 Category: CMake Reproducibility:always Severity: feature Priority: normal Status: new == Date Submitted: 2012-09-05 10:20 EDT Last Modified: 2012-09-05 10:20 EDT == Summary:Add FindIconv module Description: This module, hopefully, will properly check to see if Iconv exists on the system. == Issue History Date ModifiedUsername FieldChange == 2012-09-05 10:20 Steven Oliver New Issue 2012-09-05 10:20 Steven Oliver File Added: 0001-Add-new-FindIconv-module.patch == -- 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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
[cmake-developers] Using the internal Code::Blocks builder
Dear CMake developers,
I wanted to know if it is possible to let CMake generate a project that uses
the internal build system of the Code::Blocks IDE.
My motivation for this was that a friend of mine, who works together with me
on different projects that use CMake, uses Code::Blocks for years. He tried
CMake's Code::Blocks generator with Makefiles several times and has never been
satisfied (parallel builds not working, stopping of build not working, slow
make on Windows etc.). He ended up creating a Code::Blocks project manually.
I have written a number of hacks that modify the existing Code::Blocks
generator to generate a project that does not use the generated Makefile, but
the build system of Code::Blocks instead. I do not intend to push these
patches, they were only ment as a proof-of-concept implementation. With these
patches applied I am able to build several of our projects (shared libraries,
dependencies on external libraries, applications using them) with the
generated Code::Blocks project.
My questions to you are:
1. Is the CMake community interested in a project generator for CMake that
generates native Code::Blocks projects? If you say that this is something that
you do not want to have, I will stop my work and give my friend a custom CMake
build containing my hacks. If you are nothing loath to have such generator, I
want to try to find a way to do it right and prepare a topic branch.
2. What would be the right way to write such a generator? I think modifying
the cmExtraCodeBlocksGenerator class is not the right way. Maybe one would
have to write a new subclass of cmGlobalGenerator?
Kind regards
Benjamin
From 38a1e84b3719192f4f28f4c72da5ae39430812ca Mon Sep 17 00:00:00 2001
From: Benjamin Eikel cm...@eikel.org
Date: Sun, 2 Sep 2012 16:31:55 +0200
Subject: [PATCH 1/9] Dirty hack to use Code::Blocks internal builder without
a need for a Makefile
---
Source/cmExtraCodeBlocksGenerator.cxx | 35 -
1 file changed, 34 insertions(+), 1 deletion(-)
diff --git a/Source/cmExtraCodeBlocksGenerator.cxx b/Source/cmExtraCodeBlocksGenerator.cxx
index ad4ab76..419e9b7 100644
--- a/Source/cmExtraCodeBlocksGenerator.cxx
+++ b/Source/cmExtraCodeBlocksGenerator.cxx
@@ -315,7 +315,7 @@ void cmExtraCodeBlocksGenerator
FileVersion major=\1\ minor=\6\ /\n
Project\n
Option title=\ mf-GetProjectName()\ /\n
- Option makefile_is_custom=\1\ /\n
+ Option makefile_is_custom=\0\ /\n
Option compiler=\ compiler \ /\n
virtualFolders\n
Build\n;
@@ -632,6 +632,39 @@ void cmExtraCodeBlocksGenerator::AppendTarget(cmGeneratedFileStream fout,
fout Add option=\-D safedef.str() \ /\n;
}
}
+const char* cflags = target-GetProperty(COMPILE_FLAGS);
+if(cflags)
+ {
+ // Expand the list.
+ std::vectorstd::string flags;
+ cmSystemTools::ExpandListArgument(cflags, flags);
+ for(std::vectorstd::string::const_iterator fi = flags.begin();
+ fi != flags.end(); ++fi)
+{
+cmXMLSafe safeflag(fi-c_str());
+fout Add option=\ safeflag.str() \ /\n;
+}
+ }
+
+std::string sharedLibFlagsVar = CMAKE_SHARED_LIBRARY_CXX_FLAGS;
+if (this-GlobalGenerator-GetLanguageEnabled(CXX) == false)
+ {
+sharedLibFlagsVar = CMAKE_SHARED_LIBRARY_C_FLAGS;
+ }
+const char* sldefs = target-GetMakefile()-GetSafeDefinition(
+ CMAKE_SHARED_LIBRARY_CXX_FLAGS);
+if(sldefs)
+ {
+ // Expand the list.
+ std::vectorstd::string defs;
+ cmSystemTools::ExpandListArgument(sldefs, defs);
+ for(std::vectorstd::string::const_iterator di = defs.begin();
+ di != defs.end(); ++di)
+{
+cmXMLSafe safedef(di-c_str());
+fout Add option=\ safedef.str() \ /\n;
+}
+ }
// the include directories for this target
std::setstd::string uniqIncludeDirs;
--
1.7.10.4
From 54def9141a6477d65e49ed81fb20b7ce930dc467 Mon Sep 17 00:00:00 2001
From: Benjamin Eikel cm...@eikel.org
Date: Tue, 4 Sep 2012 18:23:06 +0200
Subject: [PATCH 2/9] Build a virtual target All referencing all other
targets built
---
Source/cmExtraCodeBlocksGenerator.cxx | 11 +++
1 file changed, 11 insertions(+)
diff --git a/Source/cmExtraCodeBlocksGenerator.cxx b/Source/cmExtraCodeBlocksGenerator.cxx
index 419e9b7..d4ecae5 100644
--- a/Source/cmExtraCodeBlocksGenerator.cxx
+++ b/Source/cmExtraCodeBlocksGenerator.cxx
@@ -322,6 +322,7 @@ void cmExtraCodeBlocksGenerator
this-AppendTarget(fout, all, 0, make.c_str(), mf, compiler.c_str());
+ std::vectorstd::string virtualTargetDeps;
// add all executable and library targets and some of the GLOBAL
// and UTILITY targets
for (std::vectorcmLocalGenerator*::const_iterator lg=lgs.begin();
@@ -388,6
Re: [cmake-developers] Using the internal Code::Blocks builder
On Wednesday 05 September 2012, Benjamin Eikel wrote: Dear CMake developers, I wanted to know if it is possible to let CMake generate a project that uses the internal build system of the Code::Blocks IDE. My motivation for this was that a friend of mine, who works together with me on different projects that use CMake, uses Code::Blocks for years. He tried CMake's Code::Blocks generator with Makefiles several times and has never been satisfied (parallel builds not working, stopping of build not working, slow make on Windows etc.). He ended up creating a Code::Blocks project manually. I have written a number of hacks that modify the existing Code::Blocks generator to generate a project that does not use the generated Makefile, but the build system of Code::Blocks instead. I do not intend to push these patches, they were only ment as a proof-of-concept implementation. With these patches applied I am able to build several of our projects (shared libraries, dependencies on external libraries, applications using them) with the generated Code::Blocks project. My questions to you are: 1. Is the CMake community interested in a project generator for CMake that generates native Code::Blocks projects? If you say that this is something that you do not want to have, I will stop my work and give my friend a custom CMake build containing my hacks. If you are nothing loath to have such generator, I want to try to find a way to do it right and prepare a topic branch. I wrote the existing CodeBlocks generator, and I'd be happy if you write a real one. So, go ahead :-) Is it possible to build a CodeBlocks project from the command line ? I think this is necessary so all the tests can be executed. 2. What would be the right way to write such a generator? I think modifying the cmExtraCodeBlocksGenerator class is not the right way. Maybe one would have to write a new subclass of cmGlobalGenerator? Yes. Alex -- 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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] Using the internal Code::Blocks builder
Hello Alex, Am Mittwoch, 5. September 2012 um 19:34:56 schrieb Alexander Neundorf: On Wednesday 05 September 2012, Benjamin Eikel wrote: Dear CMake developers, I wanted to know if it is possible to let CMake generate a project that uses the internal build system of the Code::Blocks IDE. My motivation for this was that a friend of mine, who works together with me on different projects that use CMake, uses Code::Blocks for years. He tried CMake's Code::Blocks generator with Makefiles several times and has never been satisfied (parallel builds not working, stopping of build not working, slow make on Windows etc.). He ended up creating a Code::Blocks project manually. I have written a number of hacks that modify the existing Code::Blocks generator to generate a project that does not use the generated Makefile, but the build system of Code::Blocks instead. I do not intend to push these patches, they were only ment as a proof-of-concept implementation. With these patches applied I am able to build several of our projects (shared libraries, dependencies on external libraries, applications using them) with the generated Code::Blocks project. My questions to you are: 1. Is the CMake community interested in a project generator for CMake that generates native Code::Blocks projects? If you say that this is something that you do not want to have, I will stop my work and give my friend a custom CMake build containing my hacks. If you are nothing loath to have such generator, I want to try to find a way to do it right and prepare a topic branch. I wrote the existing CodeBlocks generator, and I'd be happy if you write a real one. So, go ahead :-) Is it possible to build a CodeBlocks project from the command line ? I think this is necessary so all the tests can be executed. if the new CMake generator builds an XML project file like it is done at the moment, sure. Why shouldn't that be possible? At the moment you can build one with e.g. cmake -G CodeBlocks - Unix Makefiles (I am sure you know that. But especially because of that, I do not fully understand your question). 2. What would be the right way to write such a generator? I think modifying the cmExtraCodeBlocksGenerator class is not the right way. Maybe one would have to write a new subclass of cmGlobalGenerator? Yes. Alright. Thank you for your fast answer. Kind regards Benjamin Alex -- 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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] Using the internal Code::Blocks builder
On 9/5/2012 2:48 PM, Benjamin Eikel wrote: So, go ahead:-) Is it possible to build a CodeBlocks project from the command line ? I think this is necessary so all the tests can be executed. if the new CMake generator builds an XML project file like it is done at the moment, sure. Why shouldn't that be possible? At the moment you can build one with e.g. cmake -G CodeBlocks - Unix Makefiles (I am sure you know that. But especially because of that, I do not fully understand your question). CMake needs to be able to build with the generator being used so that it can be tested. Just because CodeBlocks - Unix Makefiles is able to build a file, does not mean the new CodeBlocks Native generator is able to build the same file. So, for testability cmake will need to drive the CodeBlocks build. It would be great to have a native CodeBlocks IDE XML file. It maybe difficult if CodeBlocks does not support building all the things cmake can build. -Bill -- 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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] Using the internal Code::Blocks builder
Am Mittwoch, 5. September 2012 um 20:54:57 schrieb Alexander Neundorf: On Wednesday 05 September 2012, Benjamin Eikel wrote: Hello Alex, Am Mittwoch, 5. September 2012 um 19:34:56 schrieb Alexander Neundorf: On Wednesday 05 September 2012, Benjamin Eikel wrote: Dear CMake developers, I wanted to know if it is possible to let CMake generate a project that uses the internal build system of the Code::Blocks IDE. My motivation for this was that a friend of mine, who works together with me on different projects that use CMake, uses Code::Blocks for years. He tried CMake's Code::Blocks generator with Makefiles several times and has never been satisfied (parallel builds not working, stopping of build not working, slow make on Windows etc.). He ended up creating a Code::Blocks project manually. I have written a number of hacks that modify the existing Code::Blocks generator to generate a project that does not use the generated Makefile, but the build system of Code::Blocks instead. I do not intend to push these patches, they were only ment as a proof-of-concept implementation. With these patches applied I am able to build several of our projects (shared libraries, dependencies on external libraries, applications using them) with the generated Code::Blocks project. My questions to you are: 1. Is the CMake community interested in a project generator for CMake that generates native Code::Blocks projects? If you say that this is something that you do not want to have, I will stop my work and give my friend a custom CMake build containing my hacks. If you are nothing loath to have such generator, I want to try to find a way to do it right and prepare a topic branch. I wrote the existing CodeBlocks generator, and I'd be happy if you write a real one. So, go ahead :-) Is it possible to build a CodeBlocks project from the command line ? I think this is necessary so all the tests can be executed. if the new CMake generator builds an XML project file like it is done at the moment, sure. Why shouldn't that be possible? At the moment you can build one with e.g. cmake -G CodeBlocks - Unix Makefiles (I am sure you know that. But especially because of that, I do not fully understand your question). Yes, this is not what I meant. Once cmake has generated a codeblocks project, let's say foo.cbp, is it possible to build (compile) this project using codeblocks from the command line ? Something like $ codeblocks --build foo.cbp This is more or less necessary so cmake can run its test suite to verify the generator works correctly. That might become a problem. I tried codeblocks --build --target=MyTarget MyProject.cbp which works and builds the specified target inside the project. But that opens a log window. I have not found a possibility to execute that without a display, yet. Alex -- 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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] [PATCH] Added very basic Windows CE Makefile support
On 09/05/2012 04:26 AM, Patrick Gansterer wrote: Thanks for the feedback. I've updated my changes and pushed it to the same branch. Great, thanks. I've pushed the platform file commits with minor tweaks: http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=e7cb8055 http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=28d744c9 Please rebase the rest of the topic on those, or on master after they make it there. Thanks, -Brad -- 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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
[cmake-developers] [CMake 0013306]: findglut bug
The following issue is now in status NEW (again)
==
http://public.kitware.com/Bug/view.php?id=13306
==
Reported By:Jona
Assigned To:
==
Project:CMake
Issue ID: 13306
Category: Modules
Reproducibility:always
Severity: minor
Priority: normal
Status: new
==
Date Submitted: 2012-06-14 16:45 EDT
Last Modified: 2012-09-05 16:41 EDT
==
Summary:findglut bug
Description:
I have installed freeglut on my system, but FindGlut.cmake is unable to find it.
I have an enviroment variable called GLUT_ROOT_PATH but it is not used by the
skript.
I rewrote the script and now it works for me:
IF (WIN32)
FIND_PATH( GLUT_INCLUDE_DIR NAMES GL/glut.h
PATHS ENV GLUT_ROOT_PATH
PATH_SUFFIXES include
)
FIND_LIBRARY( GLUT_glut_LIBRARY NAMES glut glut32 freeglut
PATHS ENV OPENGL_LIBRARY_DIR GLUT_ROOT_PATH
PATH_SUFFIXES Release lib
)
ELSE (WIN32)
The old version was:
IF (WIN32)
FIND_PATH( GLUT_INCLUDE_DIR NAMES GL/glut.h
PATHS ${GLUT_ROOT_PATH}/include )
FIND_LIBRARY( GLUT_glut_LIBRARY NAMES glut glut32 freeglut
PATHS
${OPENGL_LIBRARY_DIR}
${GLUT_ROOT_PATH}/Release
)
ELSE (WIN32)
(as I can see, it uses the cmake variable GLUT_ROOT_PATH instead of the
enviromentvariable and doenst look inside /lib for the library.
==
--
(0030440) David Cole (manager) - 2012-08-11 21:42
http://public.kitware.com/Bug/view.php?id=13306#c30440
--
Sending old, never assigned issues to the backlog.
(The age of the bug, plus the fact that it's never been assigned to anyone means
that nobody is actively working on it...)
If an issue you care about is sent to the backlog when you feel it should have
been addressed in a different manner, please bring it up on the CMake mailing
list for discussion. Sign up for the mailing list here, if you're not already on
it: http://www.cmake.org/mailman/listinfo/cmake
It's easy to re-activate a bug here if you can find a CMake developer who has
the bandwidth to take it on, and ferry a fix through to our 'next' branch for
dashboard testing.
--
(0030925) Brandon Van Every (reporter) - 2012-09-05 09:25
http://public.kitware.com/Bug/view.php?id=13306#c30925
--
Are these date stamps accurate? They seem to say, a bug + a possible fix was
submitted on June 14, 2012. Put into the backlog on August 11, 2012. That's
less than 2 months. In terms of volunteer open source labor, what people have
the time to track down and submit, that's a rather fresh bug. Calling such a
bug old doesn't send a good message. Please consider changing your threshold
of what you call old to something more reasonable. 6..12 months? Or else
don't call it old, just call it never assigned.
--
(0030928) David Cole (manager) - 2012-09-05 14:31
http://public.kitware.com/Bug/view.php?id=13306#c30928
--
The date stamps are accurate.
I agree that perhaps my judgment call of using 2 months as an old threshold
was on the small side. Maybe 6 is more reasonable. 12... I don't know. Just as
calling it old doesn't send a good message, neither does leaving it as new
and unassigned for a year. If nobody's going to be doing anything about it,
shouldn't it be categorized and clearly labelled as such?
On the other hand, if nobody's doing anything about it, then sending it to the
backlog notifies the person who submitted the bug that an action has been
taken. If that person wants, he may respond by saying hey, no fair, this is
important.
The goal with this action was to trigger such reactions from people who care
about the issues enough to speak up further about the individual ones that are
important.
Nobody likes to wade through masses of bugs, trying to prioritize them. Doing
this is a way of getting the important ones back on the roadmap.
If you object to specific bugs having been sent to the backlog, please do let us
know which ones, so that they might get onto somebody's radar.
Thanks.
[cmake-developers] [CMake 0013519]: FindGTK2 fails to include libgmodule
The following issue has been SUBMITTED. == http://public.kitware.com/Bug/view.php?id=13519 == Reported By:Jtappin Assigned To: == Project:CMake Issue ID: 13519 Category: Modules Reproducibility:always Severity: minor Priority: normal Status: new == Date Submitted: 2012-09-05 23:02 EDT Last Modified: 2012-09-05 23:02 EDT == Summary:FindGTK2 fails to include libgmodule Description: When building a package that uses cmake as its build system and includes GTK2, the libgmodule library of glib is not included in the linking list. The specific example is one of the test codes for gtk-fortran. Steps to Reproduce: On a system with PC-BSD installed. Needs the gtk+ 2 libraries gfortran. 1) Download gtk-fortran (branch gtk2-old) from github.com: git pull https://github.com/jerryd/gtk-fortran.git gtk2-old 2) Build it: mkdir build cd build cmake -D CMAKE_Fortran_COMPILER=gfortran46 .. make 3) Run the gtkbuilder2 example: ./examples/gtkbuilder2 The callback routines are not found, c.f. gtkbuilder which does not need libgmodule where they are found. Additional Information: I have only seen the problem on BSD, not Linux. == Issue History Date ModifiedUsername FieldChange == 2012-09-05 23:02 JtappinNew Issue == -- 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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [CMake] cmake + VS 2012
I have tried VS 2012 and I'm not getting exceptions when cmake regenerates projects. They get reloaded by the IDE and so it looks like things are good. Only one day of trying, so I may still be disappointed, but so far I'm happy. Hopefully I won't need those add-ins, but since I use intel fortran and it's not yet available for VS 2012, I still need to keep VS 2010/2008 for some projects and I'll certainly check out the stuff you mentioned. Thanks. JB -Original Message- From: David Cole [mailto:david.c...@kitware.com] Sent: 04 September 2012 18:06 To: Michael Jackson Cc: Biddiscombe, John A.; cmake@cmake.org Subject: Re: [CMake] cmake + VS 2012 The Visual Studio addin is from vscommands.com and is mentioned in this bug report on the issue: http://public.kitware.com/Bug/view.php?id=11258 As you can tell from reading through the notes, we never did find a satisfactory solution to the problem... issue is still open, but folks who've tried vscommands report that it reduces the pain. HTH, David On Tue, Sep 4, 2012 at 7:58 AM, Michael Jackson mike.jack...@bluequartz.net wrote: John. There was some sort of plugin or Addin that helped out the situation of reloading after CMake runs of VS2010. It was mentioned on the CMake mailing list sometime in the past year I think. I was able to install it and my VS2010 builds do run much smoother now. Not sure if that is of any help at all but thought I would mention it. When I get to work I'll try to figure out the name of the plugin. -- Mike Jackson www.bluequartz.net On Sep 4, 2012, at 5:20 AM, Biddiscombe, John A. wrote: I had a lot of trouble with cmake and VS 2010 due to the IDE crashing when projects were regenerated by cmake and having to click reload millions of times. Can anyone tell me if things are better with visual studio 2012? I want to upgrade some projects, but will delay a while if I know these IDE bugs are still present. thanks JB -- John Biddiscombe,email:biddisco @.at.@ cscs.ch http://www.cscs.ch/ CSCS, Swiss National Supercomputing Centre | Tel: +41 (91) 610.82.07 Via Trevano 131, 6900 Lugano, Switzerland | Fax: +41 (91) 610.82.82 -- 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] 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] Different compiler in sub directory
Hi, I have a need to build different parts of a project using different version of g++ If I set the top level CMakeLists.txt compiler via -DCMAKE_CXX_COMPILER=/usr/local/bin/g++ and subsequently use another compiler SET ( CMAKE_CXX_COMPILER /usr/bin/g++ ) will the compiler being set only scoped within that directory (when I use ADD_SUBDIRECTORY) or would that become global for other projects later... Regards -- Nicholas Yue Graphics - RenderMan, Visualization, OpenGL, HDF5 Custom Dev - C++ porting, OSX, Linux, Windows Management - Recruitment, career management http://www.proceduralinsight.com/ http://au.linkedin.com/in/nicholasyue -- 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] unknown cmake command configure_boost
I get this error in a cmake list ... -- View this message in context: http://cmake.3232098.n2.nabble.com/unknown-cmake-command-configure-boost-tp7581513.html Sent from the CMake mailing list archive at Nabble.com. -- 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] unknown cmake command configure_boost
^^ error is unknown cmake command configure_boost -- View this message in context: http://cmake.3232098.n2.nabble.com/unknown-cmake-command-configure-boost-tp7581513p7581514.html Sent from the CMake mailing list archive at Nabble.com. -- 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 + VS 2012
On 9/5/2012 1:59 AM, Biddiscombe, John A. wrote: I have tried VS 2012 and I'm not getting exceptions when cmake regenerates projects. They get reloaded by the IDE and so it looks like things are good. Only one day of trying, so I may still be disappointed, but so far I'm happy. Hopefully I won't need those add-ins, but since I use intel fortran and it's not yet available for VS 2012, I still need to keep VS 2010/2008 for some projects and I'll certainly check out the stuff you mentioned. Thanks. The add-in just makes VS reload with one dialog even if more than one project in the solution changes. It will show a dialog with all the projects that changed. -Bill -- 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] unknown cmake command configure_boost
Am Mittwoch, 5. September 2012 um 12:55:50 schrieb geek121: ^^ error is unknown cmake command configure_boost Why do you think configure_boost is a valid CMake command? I was not able to find it in the documentation. -- View this message in context: http://cmake.3232098.n2.nabble.com/unknown-cmake-command-configure-boost-t p7581513p7581514.html Sent from the CMake mailing list archive at Nabble.com. -- 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] Different compiler in sub directory
It's better to use ExternalProject.cmake to configure part of your solution with different compiler. On Wed, Sep 5, 2012 at 12:09 PM, Nicholas Yue yue.nicho...@gmail.comwrote: Hi, I have a need to build different parts of a project using different version of g++ If I set the top level CMakeLists.txt compiler via -DCMAKE_CXX_COMPILER=/usr/**local/bin/g++ and subsequently use another compiler SET ( CMAKE_CXX_COMPILER /usr/bin/g++ ) will the compiler being set only scoped within that directory (when I use ADD_SUBDIRECTORY) or would that become global for other projects later... Regards -- Nicholas Yue Graphics - RenderMan, Visualization, OpenGL, HDF5 Custom Dev - C++ porting, OSX, Linux, Windows Management - Recruitment, career management http://www.proceduralinsight.**com/ http://www.proceduralinsight.com/ http://au.linkedin.com/in/**nicholasyuehttp://au.linkedin.com/in/nicholasyue -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/** opensource/opensource.htmlhttp://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/**CMake_FAQhttp://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/**listinfo/cmakehttp://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] adding extra files to distribution
Hi, I'm new to CMake, but quite familiar with Autotools. I am trying to do something that is probably quite simple, but I cannot find any documentation for. The distribution creation mechanism is difficult to learn because of the lack of documentation. For instance, it seems (though I'm not sure of this) that the distribution will only contain files for which you've written an install rule, but I don't see that documented in any tutorial I've read. I was confused by that, being familiar with autotools, because I don't have to write those rules manually, and everything make has touched goes automatically into a distribution archive. I was surprised when I wrote the cpack commands into my CMakeLists.txt file only to get an empty archive. That's not meant as a cheer for autotools, just an anecdote from an autotools convert-in-progress. That leads me to my main question. If I have to have an install rule for everything, how do I add things to the distribution archive that I do not want to be installed? It's not uncommon to see projects with data or example directories that should never leave the source folders, and that never get installed. My google-fu has failed, because I cannot find how to include those files in the distribution yet not have them install anywhere. Thanks, Jack -- 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] GENERATE_EXPORT_HEADER
For static libraries the macro GENERATE_EXPORT_HEADER produce an output like this one: ... #else # ifndef CTEST_EXPORT #ifdef cTest_EXPORTS /* We are building this library */ # define CTEST_EXPORT #else /* We are using this library */ # define CTEST_EXPORT #endif # endif ... For for a static version of a library CTEST_EXPORT is empty. For Windows and the MSVC it is not always a good idea, since the MSVC can produce errors in this case. So I propose (static versions of libraries): For the MSVC and Windows CTEST_EXPORT should be defined with extern, either by option or by default. Greeting Micha -- 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] GENERATE_EXPORT_HEADER
On 9/5/2012 3:52 PM, Micha Renner wrote: For static libraries the macro GENERATE_EXPORT_HEADER produce an output like this one: ... #else # ifndef CTEST_EXPORT #ifdef cTest_EXPORTS /* We are building this library */ # define CTEST_EXPORT #else /* We are using this library */ # define CTEST_EXPORT #endif # endif ... For for a static version of a library CTEST_EXPORT is empty. For Windows and the MSVC it is not always a good idea, since the MSVC can produce errors in this case. What kind of errors? Are you sure that you're using the export macro correctly? So I propose (static versions of libraries): For the MSVC and Windows CTEST_EXPORT should be defined with extern, either by option or by default. Applying extern to a class definition doesn't make any sense. -- 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_DIR
On Wed, Jan 11, 2012 at 5:55 AM, Daniel Dekkers d.dekk...@cthrough.nl wrote: Hi, does anyone know what this “Boost_DIR” variable is from the findBoost.cmake module? And why it is never found? Everything works well, I use BOOST_ROOT to set the path to the Boost distribution, just curious. Daniel I would like to revive this question. When I do this: FIND_PACKAGE(Boost 1.51 COMPONENTS program_options required) I see a variable Boost_DIR that gets set to Boost_DIR-NOTFOUND, even though Boost_INCLUDE_DIR, Boost_LIBRARY_DIRS, and a whole bunch of other variables are set correctly, and the project builds correctly. Is there something else you have to do to get Boost_DIR to not say NOTFOUND? Thanks, David -- 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] Incremental linking and Intel fortan
Sorry for delay... I checked that setting CMAKE_EXE_LINKER_FLAGS without CACHE attribute doesnt make a change. But if I switched to NMake then all things started to work. Incremental linking is turned off, traceback works. Exactly the same CMakeLists.txt produces wrong project for VS. What do you think about different lines that I see in vfproj file? I mean LinkIncremental=1 and LinkIncremental=linkIncrementalNo. I searched the internet and found both options. For me CMake produces vfproj with 1 but Intel Fortran - with linkIncrementalNo... Thanks, Alexander 2012/9/4 Petr Kmoch petr.km...@gmail.com One more thing I noticed - CMAKE_EXE_LINKER_FLAGS is normally not a cache variable, and having both a cache and non-cache var of the same name can have weird consequences. Maybe try just setting it without CACHE STRING ... If that doesn't help, can you generate a different buildsystem (perhaps NMake) and see what the command line looks like there? Perhaps a flag turning incremental linking on comes from a different variable (there's a lot of cmake vars which make up the final command line). Petr On Mon, Sep 3, 2012 at 6:34 PM, Alexander Ivanov alexander.nik.iva...@gmail.com wrote: Hi Petr, Unfortunately it doesn't. I changed the sample as following but intel fortran ignores incremental linking setting. cmake_minimum_required(VERSION 2.8) project(TestF90 Fortran) set(CMAKE_EXE_LINKER_FLAGS /INCREMENTAL:NO CACHE STRING EXE_LINKER_FLAGS FORCE) add_executable(TestF90_EXE main.f90) Thanks, Alexander 2012/9/3 Petr Kmoch petr.km...@gmail.com Hi Alexander. CMAKE_EXE_LINKER_FLAGS and similar variables can only be modified after a call to PROJECT() (the PROJECT() calls sets them up to some defaults). See if this fixes your issue. Petr -- 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] Boost_DIR
I might be wrong but my understanding is that it's the other way arround: you provide Boost_DIR (root of your boost installation) and it finds the rest itself. I've been using it like that. I have a custom build of boost in a specific directory and an environnement variable Boost_DIR set to it. I also set Boost_ROOT to be sure because previous versions of CMake would look for it. Joel Lamotte -- 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_DIR
On Wed, Sep 5, 2012 at 2:16 PM, Klaim - Joël Lamotte mjkl...@gmail.com wrote: I might be wrong but my understanding is that it's the other way arround: you provide Boost_DIR (root of your boost installation) and it finds the rest itself. I've been using it like that. I have a custom build of boost in a specific directory and an environnement variable Boost_DIR set to it. I also set Boost_ROOT to be sure because previous versions of CMake would look for it. Joel Lamotte Joel, I tried that - with export Boost_DIR=/home/doriad/build/Boost_1_51/ in my ~/.profile and using: FIND_PACKAGE(Boost 1.51) ccmake still shows: Boost_DIR =*Boost_DIR-NOTFOUND But as I mentioned, Boost_INCLUDE_DIR and Boost_LIBRARY_DIRS are set correctly, and everything builds fine. It is just terribly confusing for one of the first things a user sees in ccmake is Boost_DIR-NOTFOUND, even though everything is configured properly! David -- 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_DIR
On Wed, Sep 5, 2012 at 2:24 PM, David Doria daviddo...@gmail.com wrote: On Wed, Sep 5, 2012 at 2:16 PM, Klaim - Joël Lamotte mjkl...@gmail.com wrote: I might be wrong but my understanding is that it's the other way arround: you provide Boost_DIR (root of your boost installation) and it finds the rest itself. I've been using it like that. I have a custom build of boost in a specific directory and an environnement variable Boost_DIR set to it. I also set Boost_ROOT to be sure because previous versions of CMake would look for it. Joel Lamotte Joel, I tried that - with export Boost_DIR=/home/doriad/build/Boost_1_51/ in my ~/.profile and using: FIND_PACKAGE(Boost 1.51) ccmake still shows: Boost_DIR =*Boost_DIR-NOTFOUND But as I mentioned, Boost_INCLUDE_DIR and Boost_LIBRARY_DIRS are set correctly, and everything builds fine. It is just terribly confusing for one of the first things a user sees in ccmake is Boost_DIR-NOTFOUND, even though everything is configured properly! David -- 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 That variable is never set by FindBoost. It must be find_package internally setting that since it never found a BoostConfig.cmake file. I agree that it's confusing, but there are several different ways to build/install boost out in the wild, and FindBoost tries to accommodate all of them, even the installations without any BoostConfig file. (In my view, it's unfortunate that there are quite so many different ways of installing boost.) It's just one of the things I think you get used to with building a CMake project that uses boost... Maybe the FindBoost maintainers will chime in here, too. Perhaps there's a way to mark the variable INTERNAL when it finds a boost that has no config file. If not, though, myabe you could just do a mark_as_advanced() on it so it gets hidden from the view of the users of your project. Cheers, David C. -- 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] OS X spaces in paths issue
This might have already been answered on the list but it didn't come up in a search. Someone that I work with was trying to run a ctest dashboard-generation script on OS X, and ctest was reporting There was an error: No such file or directory. Running ctest -VV gave more info about the error: Run command: /Applications/CMake 2.8-9.app/Contents/bin/cmake -DCMAKE_BUILD_TYPE:STRING=RelWithDebInfo -DBUILD_DOCUMENTATION:BOOL=OFF -GUnix Makefiles /Users/ellen/TestBinDir So ctest was finding cmake automatically, but was failing because the absolute path to cmake contained a space. Has anyone else seen this error when using ctest to build a dashboard? I always build cmake from source, so I didn't encounter this until I tried running ctest on someone else's machine. - David -- 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] Add sources to a target library after add_library()?
Hi, I look this ML: http://www.cmake.org/pipermail/cmake/2010-January/034437.html Does CMake still can't support how to add sources to a target library after add_library()? I wan't support Precompiled Header for both MSVC / GCC(MinGW). In MSVC case, it need a source, e.g. StdAfx.cpp to support PCH. But in GCC case, it only need a header, e.g. pch.h Any help or comments or tips are best welcome! See: https://codereview.qt-project.org/#change,34052 -- Best Regards Yuchen -- 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 sources to a target library after add_library()?
On 06/09/2012 00:30, Loaden wrote: Hi, I look this ML: http://www.cmake.org/pipermail/cmake/2010-January/034437.html Does CMake still can't support how to add sources to a target library after add_library()? I wan't support Precompiled Header for both MSVC / GCC(MinGW). In MSVC case, it need a source, e.g. StdAfx.cpp to support PCH. But in GCC case, it only need a header, e.g. pch.h Any help or comments or tips are best welcome! See: https://codereview.qt-project.org/#change,34052 I don't see what this feature would have to do with precompiled headers. To use a precompiled header with GCC, just add -include path/to/precompiled/header.hpp to your compilation flags, and make sure you've built path/to/precompiled/header.hpp.gch before that. -- 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 sources to a target library after add_library()?
Yes, it simply for GCC. But it is diffrent for MSVC compiler.
for MSVC, we have to use a .cpp file, e.g. stdafx.cpp to support
precompiled. (/Yc flags)
For now, I have to implement it like this to support both MSVC and GCC's
PCH support.
set(target Core)
if (QTCREATOR_PRECOMPILED AND MSVC)
set(precompiled libpch.cpp)
endif()
set(sources
lib.cpp
lib2.cpp
)
add_qtcreator_plugin(${target}
${sources}
${precompiled}
)
add_dependencies(${target} Botan)
if (QTCREATOR_PRECOMPILED)
add_precompiled_header(${target} CXX libpch.h ${precompiled})
use_precompiled_header(${target} ${sources})
endif()
2012/9/6 Mathias Gaunard mathias.gaun...@ens-lyon.org
To use a precompiled header with GCC, just add -include
path/to/precompiled/header.hpp to your compilation flags, and make sure
you've built path/to/precompiled/header.**hpp.gch before that.
--
Best Regards
Yuchen
--
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-commits] CMake branch, next, updated. v2.8.9-364-g6b1ccc4
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 6b1ccc4ad2de5548db2d607a41f944b7acdf7102 (commit)
via 043ef66c5fa77a46e48f0c1d07b6532e93bbc909 (commit)
from e3d033a4451a6d8ce4eed17c46f772a2650b6976 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=6b1ccc4ad2de5548db2d607a41f944b7acdf7102
commit 6b1ccc4ad2de5548db2d607a41f944b7acdf7102
Merge: e3d033a 043ef66
Author: David Cole david.c...@kitware.com
AuthorDate: Wed Sep 5 07:46:23 2012 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Wed Sep 5 07:46:23 2012 -0400
Merge topic 'ninja-rc-without-compile-flags' into next
043ef66 Revert Ninja: BUG 13486, don't pass COMPILE_FLAGS to rc
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=043ef66c5fa77a46e48f0c1d07b6532e93bbc909
commit 043ef66c5fa77a46e48f0c1d07b6532e93bbc909
Author: David Cole david.c...@kitware.com
AuthorDate: Wed Sep 5 07:44:11 2012 -0400
Commit: David Cole david.c...@kitware.com
CommitDate: Wed Sep 5 07:44:11 2012 -0400
Revert Ninja: BUG 13486, don't pass COMPILE_FLAGS to rc
This reverts commit 439f025543beb736dd3aa9f84e0d05a1e420a58e.
Plan on using CMAKE_RC_FLAG_REGEX instead of hard-coding it like
this commit attempted to do. See notes in bug #13486 for more details.
diff --git a/Source/cmNinjaTargetGenerator.cxx
b/Source/cmNinjaTargetGenerator.cxx
index ee163de..b6bdfdc 100644
--- a/Source/cmNinjaTargetGenerator.cxx
+++ b/Source/cmNinjaTargetGenerator.cxx
@@ -167,14 +167,11 @@
cmNinjaTargetGenerator::ComputeFlagsForObject(cmSourceFile *source,
// Append old-style preprocessor definition flags.
this-LocalGenerator-AppendFlags(flags, this-Makefile-GetDefineFlags());
- if (language != RC)
-{
-// Add target-specific and source-specific flags.
-this-LocalGenerator-AppendFlags(flags,
-this-Target-GetProperty(COMPILE_FLAGS));
-this-LocalGenerator-AppendFlags(flags,
- source-GetProperty(COMPILE_FLAGS));
-}
+ // Add target-specific and source-specific flags.
+ this-LocalGenerator-AppendFlags(flags,
+ this-Target-GetProperty(COMPILE_FLAGS));
+ this-LocalGenerator-AppendFlags(flags,
+source-GetProperty(COMPILE_FLAGS));
// TODO: Handle Apple frameworks.
---
Summary of changes:
Source/cmNinjaTargetGenerator.cxx | 13 +
1 files changed, 5 insertions(+), 8 deletions(-)
hooks/post-receive
--
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-commits
[Cmake-commits] CMake branch, next, updated. v2.8.9-366-gadcef96
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via adcef9697b33c0e574b32e7a1a4f7579c7ec9524 (commit)
via c875be5cee7d411d63f98e31d824f3636278b401 (commit)
from 6b1ccc4ad2de5548db2d607a41f944b7acdf7102 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=adcef9697b33c0e574b32e7a1a4f7579c7ec9524
commit adcef9697b33c0e574b32e7a1a4f7579c7ec9524
Merge: 6b1ccc4 c875be5
Author: Peter Kuemmel syntheti...@gmx.net
AuthorDate: Wed Sep 5 08:30:29 2012 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Wed Sep 5 08:30:29 2012 -0400
Merge topic 'ninja-BuildDepends' into next
c875be5 Ninja: undo, and fix via try_compile feature
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=c875be5cee7d411d63f98e31d824f3636278b401
commit c875be5cee7d411d63f98e31d824f3636278b401
Author: Peter Kümmel syntheti...@gmx.net
AuthorDate: Wed Sep 5 14:29:22 2012 +0200
Commit: Peter Kümmel syntheti...@gmx.net
CommitDate: Wed Sep 5 14:29:22 2012 +0200
Ninja: undo, and fix via try_compile feature
diff --git a/Source/cmNinjaTargetGenerator.cxx
b/Source/cmNinjaTargetGenerator.cxx
index bdb50b1..918f582 100644
--- a/Source/cmNinjaTargetGenerator.cxx
+++ b/Source/cmNinjaTargetGenerator.cxx
@@ -355,8 +355,8 @@ cmNinjaTargetGenerator
if (lang == C || lang == CXX || lang == RC)
{
clDepsBinary = mf-GetSafeDefinition(CMAKE_CMCLDEPS_EXECUTABLE);
-const std::string name = mf-GetProjectName() ? mf-GetProjectName() : ;
-if (!clDepsBinary.empty() name != TRY_COMPILE)
+if (!clDepsBinary.empty()
+!this-GetGlobalGenerator()-GetCMakeInstance()-GetIsInTryCompile())
{
clShowPrefix = mf-GetSafeDefinition(CMAKE_CL_SHOWINCLUDE_PREFIX);
clBinary = mf-GetDefinition(CMAKE_C_COMPILER) ?
---
Summary of changes:
Source/cmNinjaTargetGenerator.cxx |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
hooks/post-receive
--
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-commits
[Cmake-commits] CMake branch, next, updated. v2.8.9-368-gdc4345a
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via dc4345a1a236ecd4ad95980507ca825c9abc9327 (commit)
via 7b2bf28e183b5eacc22fe3030f0439853746f0bd (commit)
from adcef9697b33c0e574b32e7a1a4f7579c7ec9524 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=dc4345a1a236ecd4ad95980507ca825c9abc9327
commit dc4345a1a236ecd4ad95980507ca825c9abc9327
Merge: adcef96 7b2bf28
Author: Peter Kuemmel syntheti...@gmx.net
AuthorDate: Wed Sep 5 08:56:16 2012 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Wed Sep 5 08:56:16 2012 -0400
Merge topic 'IsSourceFileTryCompile' into next
7b2bf28 Ninja: suppress cmcldeps only for source file signature try_compiles
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=7b2bf28e183b5eacc22fe3030f0439853746f0bd
commit 7b2bf28e183b5eacc22fe3030f0439853746f0bd
Author: Peter Kümmel syntheti...@gmx.net
AuthorDate: Wed Sep 5 01:44:11 2012 +0200
Commit: Peter Kümmel syntheti...@gmx.net
CommitDate: Wed Sep 5 14:38:49 2012 +0200
Ninja: suppress cmcldeps only for source file signature try_compiles
diff --git a/Source/cmMakefile.cxx b/Source/cmMakefile.cxx
index 7b6c450..9a9c1c8 100644
--- a/Source/cmMakefile.cxx
+++ b/Source/cmMakefile.cxx
@@ -46,6 +46,7 @@ public:
std::stackcmDefinitions, std::listcmDefinitions VarStack;
std::stackstd::setcmStdString VarInitStack;
std::stackstd::setcmStdString VarUsageStack;
+ bool IsSourceFileTryCompile;
};
// default is not to be building executables
@@ -56,6 +57,7 @@ cmMakefile::cmMakefile(): Internal(new Internals)
this-Internal-VarStack.push(defs);
this-Internal-VarInitStack.push(globalKeys);
this-Internal-VarUsageStack.push(globalKeys);
+ this-Internal-IsSourceFileTryCompile = false;
// Initialize these first since AddDefaultDefinitions calls AddDefinition
this-WarnUnused = false;
@@ -2912,6 +2914,7 @@ int cmMakefile::TryCompile(const char *srcdir, const char
*bindir,
const std::vectorstd::string *cmakeArgs,
std::string *output)
{
+ this-Internal-IsSourceFileTryCompile = fast;
// does the binary directory exist ? If not create it...
if (!cmSystemTools::FileIsDirectory(bindir))
{
@@ -2937,6 +2940,7 @@ int cmMakefile::TryCompile(const char *srcdir, const char
*bindir,
Internal CMake error, TryCompile bad GlobalGenerator);
// return to the original directory
cmSystemTools::ChangeDirectory(cwd.c_str());
+this-Internal-IsSourceFileTryCompile = false;
return 1;
}
cm.SetGlobalGenerator(gg);
@@ -3009,6 +3013,7 @@ int cmMakefile::TryCompile(const char *srcdir, const char
*bindir,
Internal CMake error, TryCompile configure of cmake failed);
// return to the original directory
cmSystemTools::ChangeDirectory(cwd.c_str());
+this-Internal-IsSourceFileTryCompile = false;
return 1;
}
@@ -3018,6 +3023,7 @@ int cmMakefile::TryCompile(const char *srcdir, const char
*bindir,
Internal CMake error, TryCompile generation of cmake failed);
// return to the original directory
cmSystemTools::ChangeDirectory(cwd.c_str());
+this-Internal-IsSourceFileTryCompile = false;
return 1;
}
@@ -3031,9 +3037,15 @@ int cmMakefile::TryCompile(const char *srcdir, const
char *bindir,
this);
cmSystemTools::ChangeDirectory(cwd.c_str());
+ this-Internal-IsSourceFileTryCompile = false;
return ret;
}
+bool cmMakefile::GetIsSourceFileTryCompile() const
+{
+ return this-Internal-IsSourceFileTryCompile;
+}
+
cmake *cmMakefile::GetCMakeInstance() const
{
if ( this-LocalGenerator this-LocalGenerator-GetGlobalGenerator() )
diff --git a/Source/cmMakefile.h b/Source/cmMakefile.h
index 8a0088b..74c8039 100644
--- a/Source/cmMakefile.h
+++ b/Source/cmMakefile.h
@@ -128,6 +128,8 @@ public:
const std::vectorstd::string *cmakeArgs,
std::string *output);
+ bool GetIsSourceFileTryCompile() const;
+
/**
* Specify the makefile generator. This is platform/compiler
* dependent, although the interface is through a generic
diff --git a/Source/cmNinjaTargetGenerator.cxx
b/Source/cmNinjaTargetGenerator.cxx
index 918f582..4cc23ca 100644
--- a/Source/cmNinjaTargetGenerator.cxx
+++ b/Source/cmNinjaTargetGenerator.cxx
@@ -355,8 +355,7 @@ cmNinjaTargetGenerator
if (lang == C || lang == CXX || lang == RC)
{
clDepsBinary = mf-GetSafeDefinition(CMAKE_CMCLDEPS_EXECUTABLE);
-if (!clDepsBinary.empty()
-
[Cmake-commits] CMake branch, next, updated. v2.8.9-375-g2dd3b78
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 2dd3b783fdc8d0c918d8134f9623439940715073 (commit)
via 57234dd10a091e676d9e3a9279029dadace757c3 (commit)
via 3776690e62c631edd520f566b2ebcaffbad230b4 (commit)
via 41f0f83542ce8d69e4d9a4512a6dc66327f20c8d (commit)
via fb6d5136926fc142fa893f853b62c5ca8df04d6c (commit)
via 8d1e10296ae852afd80c789efa73492f87543034 (commit)
via 2f204bc176e418e810de7034903974e7edb46b14 (commit)
from dc4345a1a236ecd4ad95980507ca825c9abc9327 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=2dd3b783fdc8d0c918d8134f9623439940715073
commit 2dd3b783fdc8d0c918d8134f9623439940715073
Merge: dc4345a 57234dd
Author: Brad King brad.k...@kitware.com
AuthorDate: Wed Sep 5 09:36:10 2012 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Wed Sep 5 09:36:10 2012 -0400
Merge topic 'ctest-svn-update' into next
57234dd cmCTestSVN: Load and process information from externals
3776690 cmCTestSVN: Add a LoadExternal() function and an ExternalParser
class
41f0f83 cmCTestSVN: Use the SVNInfo structure
fb6d513 cmCTestSVN: Create the SVNInfo for the root repository
8d1e102 cmCTestSVN: Add the Repositories list and the RootInfo pointer
2f204bc cmCTestSVN: Extend Revision struct with SVN repo information
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=57234dd10a091e676d9e3a9279029dadace757c3
commit 57234dd10a091e676d9e3a9279029dadace757c3
Author: Xavier Besseron xavier.besse...@uni.lu
AuthorDate: Mon Sep 3 11:10:53 2012 +0200
Commit: Brad King brad.k...@kitware.com
CommitDate: Tue Sep 4 08:35:36 2012 -0400
cmCTestSVN: Load and process information from externals
Call LoadExternals() and perform operations on all elements of the
Repositories list.
diff --git a/Source/CTest/cmCTestSVN.cxx b/Source/CTest/cmCTestSVN.cxx
index b27c633..49cea2e 100644
--- a/Source/CTest/cmCTestSVN.cxx
+++ b/Source/CTest/cmCTestSVN.cxx
@@ -121,9 +121,15 @@ void cmCTestSVN::NoteOldRevision()
// Info for root repository
this-Repositories.push_back( SVNInfo() );
this-RootInfo = (this-Repositories.back());
+ // Info for the external repositories
+ this-LoadExternals();
-// Get info for the root repositiry
-SVNInfo svninfo = *RootInfo;
+ // Get info for all the repositories
+ std::listSVNInfo::iterator itbeg = this-Repositories.begin();
+ std::listSVNInfo::iterator itend = this-Repositories.end();
+ for( ; itbeg != itend ; itbeg++)
+{
+SVNInfo svninfo = *itbeg;
svninfo.OldRevision = this-LoadInfo(svninfo);
this-Log Revision for repository ' svninfo.LocalPath
' before update: svninfo.OldRevision \n;
@@ -131,6 +137,7 @@ void cmCTestSVN::NoteOldRevision()
Old revision of external repository '
svninfo.LocalPath ' is:
svninfo.OldRevision \n);
+}
// Set the global old revision to the one of the root
this-OldRevision = this-RootInfo-OldRevision;
@@ -140,8 +147,12 @@ void cmCTestSVN::NoteOldRevision()
//
void cmCTestSVN::NoteNewRevision()
{
- // Get info for the root repository
-SVNInfo svninfo = *RootInfo;
+ // Get info for the external repositories
+ std::listSVNInfo::iterator itbeg = this-Repositories.begin();
+ std::listSVNInfo::iterator itend = this-Repositories.end();
+ for( ; itbeg != itend ; itbeg++)
+{
+SVNInfo svninfo = *itbeg;
svninfo.NewRevision = this-LoadInfo(svninfo);
this-Log Revision for repository ' svninfo.LocalPath
' after update: svninfo.NewRevision \n;
@@ -168,6 +179,8 @@ void cmCTestSVN::NoteNewRevision()
this-Log Repository ' svninfo.LocalPath
' Base = svninfo.Base \n;
+ }
+
// Set the global new revision to the one of the root
this-NewRevision = this-RootInfo-NewRevision;
}
@@ -379,9 +392,14 @@ private:
//
void cmCTestSVN::LoadRevisions()
{
-// Get revision of the root repository
-SVNInfo svninfo = *RootInfo;
+ // Get revisions for all the external repositories
+ std::listSVNInfo::iterator itbeg = this-Repositories.begin();
+ std::listSVNInfo::iterator itend = this-Repositories.end();
+ for( ; itbeg != itend ; itbeg++)
+{
+SVNInfo svninfo = *itbeg;
LoadRevisions(svninfo);
+}
}
//
@@ -418,6 +436,14 @@ void
[Cmake-commits] CMake branch, next, updated. v2.8.9-378-gfc28530
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, next has been updated via fc28530d55f0955423620941521e8dc52418f08b (commit) via 084c5af4e0c7f2aa4bea6f6db0fe00ebd4802b37 (commit) via 2da17ef7975b521abe2be4736569d19ef79dc3be (commit) from 2dd3b783fdc8d0c918d8134f9623439940715073 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=fc28530d55f0955423620941521e8dc52418f08b commit fc28530d55f0955423620941521e8dc52418f08b Merge: 2dd3b78 084c5af Author: Brad King brad.k...@kitware.com AuthorDate: Wed Sep 5 12:50:51 2012 -0400 Commit: CMake Topic Stage kwro...@kitware.com CommitDate: Wed Sep 5 12:50:51 2012 -0400 Merge topic 'aix-release-bmaxdata' into next 084c5af Utilities/Release: Link AIX binary with large maxdata 2da17ef CMake Nightly Date Stamp http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=084c5af4e0c7f2aa4bea6f6db0fe00ebd4802b37 commit 084c5af4e0c7f2aa4bea6f6db0fe00ebd4802b37 Author: Brad King brad.k...@kitware.com AuthorDate: Wed Sep 5 12:03:34 2012 -0400 Commit: Brad King brad.k...@kitware.com CommitDate: Wed Sep 5 12:49:37 2012 -0400 Utilities/Release: Link AIX binary with large maxdata Raise the default maxdata linker setting on the 32-bit AIX release binaries. This allows the CMake binaries to process larger projects without encountering a Segmentation fault in extend_brk. diff --git a/Utilities/Release/v20n250_aix_release.cmake b/Utilities/Release/v20n250_aix_release.cmake index 53c34d7..cc8cd05 100644 --- a/Utilities/Release/v20n250_aix_release.cmake +++ b/Utilities/Release/v20n250_aix_release.cmake @@ -7,6 +7,7 @@ set(MAKE_PROGRAM make) set(CC xlc_r) set(CXX xlC_r) set(FC xlf) +set(LDFLAGS -Wl,-bmaxdata:0x8000) # Push Segmentation fault in extend_brk over horizon set(INITIAL_CACHE CMAKE_BUILD_TYPE:STRING=Release CMAKE_SKIP_BOOTSTRAP_TEST:STRING=TRUE --- Summary of changes: Source/CMakeVersion.cmake |2 +- Utilities/Release/v20n250_aix_release.cmake |1 + 2 files changed, 2 insertions(+), 1 deletions(-) hooks/post-receive -- CMake ___ Cmake-commits mailing list Cmake-commits@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-commits
[Cmake-commits] CMake branch, next, updated. v2.8.9-381-g1577079
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 1577079663bb2f720157ca614b6bae9600161a08 (commit)
via 28d744c9ea332a10b9fc3061758d5f8031158727 (commit)
via e7cb80556eddc33dfa81c8ba1070a448d8eea5f9 (commit)
from fc28530d55f0955423620941521e8dc52418f08b (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=1577079663bb2f720157ca614b6bae9600161a08
commit 1577079663bb2f720157ca614b6bae9600161a08
Merge: fc28530 28d744c
Author: Brad King brad.k...@kitware.com
AuthorDate: Wed Sep 5 16:00:12 2012 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Wed Sep 5 16:00:12 2012 -0400
Merge topic 'windows-ce' into next
28d744c Add WindowsCE platform information files
e7cb805 Add additional architectures to CMakePlatformId.h.in
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=28d744c9ea332a10b9fc3061758d5f8031158727
commit 28d744c9ea332a10b9fc3061758d5f8031158727
Author: Patrick Gansterer par...@paroga.com
AuthorDate: Wed Sep 5 10:08:58 2012 +0200
Commit: Brad King brad.k...@kitware.com
CommitDate: Wed Sep 5 07:38:45 2012 -0400
Add WindowsCE platform information files
This enables CMake to create Makefiles targeting Windows CE devices.
CMake needs to be run within a cross compile command prompt and requires
a toolchain file which sets CMAKE_SYSTEM_NAME to WindowsCE and
optionally CMAKE_SYSTEM_VERSION.
diff --git a/Modules/Platform/Windows-MSVC.cmake
b/Modules/Platform/Windows-MSVC.cmake
index 238aa24..cc48cfe 100644
--- a/Modules/Platform/Windows-MSVC.cmake
+++ b/Modules/Platform/Windows-MSVC.cmake
@@ -38,8 +38,13 @@ endif()
set(WIN32 1)
-set(CMAKE_CREATE_WIN32_EXE /subsystem:windows)
-set(CMAKE_CREATE_CONSOLE_EXE /subsystem:console)
+if(CMAKE_SYSTEM_NAME MATCHES WindowsCE)
+ set(CMAKE_CREATE_WIN32_EXE /subsystem:windowsce /entry:WinMainCRTStartup)
+ set(CMAKE_CREATE_CONSOLE_EXE /subsystem:windowsce /entry:mainACRTStartup)
+else()
+ set(CMAKE_CREATE_WIN32_EXE /subsystem:windows)
+ set(CMAKE_CREATE_CONSOLE_EXE /subsystem:console)
+endif()
if(CMAKE_GENERATOR MATCHES Visual Studio 6)
set (CMAKE_NO_BUILD_TYPE 1)
@@ -117,14 +122,38 @@ endif()
# default to Debug builds
set(CMAKE_BUILD_TYPE_INIT Debug)
-if(MSVC_VERSION GREATER 1310)
- set(_RTC1 /RTC1)
+if(CMAKE_SYSTEM_NAME MATCHES WindowsCE)
+ string(TOUPPER ${MSVC_C_ARCHITECTURE_ID} _MSVC_C_ARCHITECTURE_ID_UPPER)
+ string(TOUPPER ${MSVC_CXX_ARCHITECTURE_ID} _MSVC_CXX_ARCHITECTURE_ID_UPPER)
+
+ if(${CMAKE_SYSTEM_VERSION} MATCHES ^([0-9]+)\\.([0-9]+))
+math(EXPR _CE_VERSION ${CMAKE_MATCH_1}*100 + ${CMAKE_MATCH_2})
+ elseif(${CMAKE_SYSTEM_VERSION} STREQUAL )
+set(_CE_VERSION 500)
+ else()
+message(FATAL_ERROR Invalid Windows CE version: ${CMAKE_SYSTEM_VERSION})
+ endif()
+
+ set(_PLATFORM_DEFINES /D_WIN32_WCE=0x${_CE_VERSION} /DUNDER_CE)
+ set(_PLATFORM_DEFINES_C /D${MSVC_C_ARCHITECTURE_ID}
/D_${_MSVC_C_ARCHITECTURE_ID_UPPER}_)
+ set(_PLATFORM_DEFINES_CXX /D${MSVC_CXX_ARCHITECTURE_ID}
/D_${_MSVC_CXX_ARCHITECTURE_ID_UPPER}_)
+
+ set(_RTC1 )
set(_FLAGS_CXX /GR /EHsc)
- set(CMAKE_C_STANDARD_LIBRARIES_INIT kernel32.lib user32.lib gdi32.lib
winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib
advapi32.lib)
+ set(CMAKE_C_STANDARD_LIBRARIES_INIT coredll.lib corelibc.lib ole32.lib
oleaut32.lib uuid.lib commctrl.lib)
+ set(CMAKE_EXE_LINKER_FLAGS_INIT ${CMAKE_EXE_LINKER_FLAGS_INIT}
/NODEFAULTLIB:libc.lib /NODEFAULTLIB:oldnames.lib)
else()
- set(_RTC1 /GZ)
- set(_FLAGS_CXX /GR /GX)
- set(CMAKE_C_STANDARD_LIBRARIES_INIT kernel32.lib user32.lib gdi32.lib
winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib
uuid.lib odbc32.lib odbccp32.lib)
+ set(_PLATFORM_DEFINES /DWIN32)
+
+ if(MSVC_VERSION GREATER 1310)
+set(_RTC1 /RTC1)
+set(_FLAGS_CXX /GR /EHsc)
+set(CMAKE_C_STANDARD_LIBRARIES_INIT kernel32.lib user32.lib gdi32.lib
winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib
advapi32.lib)
+ else()
+set(_RTC1 /GZ)
+set(_FLAGS_CXX /GR /GX)
+set(CMAKE_C_STANDARD_LIBRARIES_INIT kernel32.lib user32.lib gdi32.lib
winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib
uuid.lib odbc32.lib odbccp32.lib)
+ endif()
endif()
set(CMAKE_CXX_STANDARD_LIBRARIES_INIT ${CMAKE_C_STANDARD_LIBRARIES_INIT})
@@ -136,6 +165,13 @@ set(_MACHINE_ARCH_FLAG ${MSVC_C_ARCHITECTURE_ID})
if(NOT _MACHINE_ARCH_FLAG)
set(_MACHINE_ARCH_FLAG ${MSVC_CXX_ARCHITECTURE_ID})
endif()
+if(CMAKE_SYSTEM_NAME MATCHES WindowsCE)
+ if(_MACHINE_ARCH_FLAG MATCHES ARM)
+
[Cmake-commits] CMake branch, master, updated. v2.8.9-235-g8797df4
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, master has been updated via 8797df41b285e7f17fdf1302e3b872ba94e110af (commit) from 2da17ef7975b521abe2be4736569d19ef79dc3be (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=8797df41b285e7f17fdf1302e3b872ba94e110af commit 8797df41b285e7f17fdf1302e3b872ba94e110af Author: Kitware Robot kwro...@kitware.com AuthorDate: Thu Sep 6 00:01:02 2012 -0400 Commit: Kitware Robot kwro...@kitware.com CommitDate: Thu Sep 6 00:01:02 2012 -0400 CMake Nightly Date Stamp diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake index 264dcc9..86f8282 100644 --- a/Source/CMakeVersion.cmake +++ b/Source/CMakeVersion.cmake @@ -2,5 +2,5 @@ set(CMake_VERSION_MAJOR 2) set(CMake_VERSION_MINOR 8) set(CMake_VERSION_PATCH 9) -set(CMake_VERSION_TWEAK 20120905) +set(CMake_VERSION_TWEAK 20120906) #set(CMake_VERSION_RC 1) --- Summary of changes: Source/CMakeVersion.cmake |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) hooks/post-receive -- CMake ___ Cmake-commits mailing list Cmake-commits@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-commits
