[Cmake-commits] CMake branch, next, updated. v2.8.8-2712-g198bb9d
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 198bb9d1e7702cf4a22d9e65aeda1ec83ad6e92f (commit)
via dd07161c512e8d520da51f8bb82a65ec29aa57ba (commit)
from 08118430d645ef0f8bb9f4429cee534b0fcb2a71 (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=198bb9d1e7702cf4a22d9e65aeda1ec83ad6e92f
commit 198bb9d1e7702cf4a22d9e65aeda1ec83ad6e92f
Merge: 0811843 dd07161
Author: Bill Hoffman bill.hoff...@kitware.com
AuthorDate: Thu Apr 26 08:31:01 2012 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Thu Apr 26 08:31:01 2012 -0400
Merge topic 'mumps_coverage' into next
dd07161 Fix warning about char* instead of const char*.
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=dd07161c512e8d520da51f8bb82a65ec29aa57ba
commit dd07161c512e8d520da51f8bb82a65ec29aa57ba
Author: Bill Hoffman bill.hoff...@kitware.com
AuthorDate: Thu Apr 26 08:30:13 2012 -0400
Commit: Bill Hoffman bill.hoff...@kitware.com
CommitDate: Thu Apr 26 08:30:13 2012 -0400
Fix warning about char* instead of const char*.
diff --git a/Source/CTest/cmParseGTMCoverage.cxx
b/Source/CTest/cmParseGTMCoverage.cxx
index 16e0f61..130e40e 100644
--- a/Source/CTest/cmParseGTMCoverage.cxx
+++ b/Source/CTest/cmParseGTMCoverage.cxx
@@ -351,7 +351,7 @@ bool cmParseGTMCoverage::ReadMCovFile(const char* file)
else
{
// try some alternate names
- char* tryname[] = {GUX, GTM, ONT, 0};
+ const char* tryname[] = {GUX, GTM, ONT, 0};
for(int k=0; tryname[k] != 0; k++)
{
std::string routine2 = routine + tryname[k];
---
Summary of changes:
Source/CTest/cmParseGTMCoverage.cxx |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
[Cmake-commits] CMake branch, next, updated. v2.8.8-2714-gf661b99
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 f661b99a80b69b787815b274c3c2206a571b996b (commit)
via 72210c266238607e12c12ed7e983efed557fa784 (commit)
from 198bb9d1e7702cf4a22d9e65aeda1ec83ad6e92f (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=f661b99a80b69b787815b274c3c2206a571b996b
commit f661b99a80b69b787815b274c3c2206a571b996b
Merge: 198bb9d 72210c2
Author: Bill Hoffman bill.hoff...@kitware.com
AuthorDate: Thu Apr 26 08:34:01 2012 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Thu Apr 26 08:34:01 2012 -0400
Merge topic 'mumps_coverage' into next
72210c2 Fix line length.
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=72210c266238607e12c12ed7e983efed557fa784
commit 72210c266238607e12c12ed7e983efed557fa784
Author: Bill Hoffman bill.hoff...@kitware.com
AuthorDate: Thu Apr 26 08:33:27 2012 -0400
Commit: Bill Hoffman bill.hoff...@kitware.com
CommitDate: Thu Apr 26 08:33:27 2012 -0400
Fix line length.
diff --git a/Source/CTest/cmCTestCoverageHandler.cxx
b/Source/CTest/cmCTestCoverageHandler.cxx
index 6c99928..099bcb6 100644
--- a/Source/CTest/cmCTestCoverageHandler.cxx
+++ b/Source/CTest/cmCTestCoverageHandler.cxx
@@ -765,7 +765,8 @@ int cmCTestCoverageHandler::HandleGTMCoverage(
cmCTestCoverageHandlerContainer* cont)
{
cmParseGTMCoverage cov(*cont, this-CTest);
- std::string coverageFile = this-CTest-GetBinaryDir() +
/gtm_coverage.mcov;
+ std::string coverageFile = this-CTest-GetBinaryDir() +
+/gtm_coverage.mcov;
if(cmSystemTools::FileExists(coverageFile.c_str()))
{
cov.ReadGTMCoverage(coverageFile.c_str());
---
Summary of changes:
Source/CTest/cmCTestCoverageHandler.cxx |3 ++-
1 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.8-2708-g283b8fe
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 283b8fe1ed285f15ee3b408ec070e8a98bb29413 (commit)
via e6412e084ed6ba77c17292e3e7c5b9d8e2450bab (commit)
from 53c3ca3a59790e99b5fc94bc8d99dc20d0379c5b (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=283b8fe1ed285f15ee3b408ec070e8a98bb29413
commit 283b8fe1ed285f15ee3b408ec070e8a98bb29413
Merge: 53c3ca3 e6412e0
Author: Bill Hoffman bill.hoff...@kitware.com
AuthorDate: Wed Apr 25 17:06:12 2012 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Wed Apr 25 17:06:12 2012 -0400
Merge topic 'mumps_coverage' into next
e6412e0 Add support to ctest for GTM mumps coverage.
diff --cc Source/CTest/cmCTestCoverageHandler.cxx
index ae06b0f,6c99928..23d2637
--- a/Source/CTest/cmCTestCoverageHandler.cxx
+++ b/Source/CTest/cmCTestCoverageHandler.cxx
@@@ -751,34 -760,19 +760,46 @@@ int cmCTestCoverageHandler::HandlePHPCo
}
return static_castint(cont-TotalCoverage.size());
}
+ //--
+ int cmCTestCoverageHandler::HandleGTMCoverage(
+ cmCTestCoverageHandlerContainer* cont)
+ {
+ cmParseGTMCoverage cov(*cont, this-CTest);
+ std::string coverageFile = this-CTest-GetBinaryDir() +
/gtm_coverage.mcov;
+ if(cmSystemTools::FileExists(coverageFile.c_str()))
+ {
+ cov.ReadGTMCoverage(coverageFile.c_str());
+ }
+ return static_castint(cont-TotalCoverage.size());
+ }
+struct cmCTestCoverageHandlerLocale
+{
+ cmCTestCoverageHandlerLocale()
+{
+if(const char* l = cmSystemTools::GetEnv(LC_ALL))
+ {
+ lc_all = l;
+ }
+if(lc_all != C)
+ {
+ cmSystemTools::PutEnv(LC_ALL=C);
+ }
+}
+ ~cmCTestCoverageHandlerLocale()
+{
+if(!lc_all.empty())
+ {
+ cmSystemTools::PutEnv((LC_ALL= + lc_all).c_str());
+ }
+else
+ {
+ cmSystemTools::UnsetEnv(LC_ALL);
+ }
+}
+ std::string lc_all;
+};
+
//--
int cmCTestCoverageHandler::HandleGCovCoverage(
cmCTestCoverageHandlerContainer* cont)
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=e6412e084ed6ba77c17292e3e7c5b9d8e2450bab
commit e6412e084ed6ba77c17292e3e7c5b9d8e2450bab
Author: Bill Hoffman bill.hoff...@kitware.com
AuthorDate: Wed Apr 25 17:04:28 2012 -0400
Commit: Bill Hoffman bill.hoff...@kitware.com
CommitDate: Wed Apr 25 17:04:28 2012 -0400
Add support to ctest for GTM mumps coverage.
diff --git a/Source/CMakeLists.txt b/Source/CMakeLists.txt
index f9d1c03..1ef67da 100644
--- a/Source/CMakeLists.txt
+++ b/Source/CMakeLists.txt
@@ -423,6 +423,7 @@ SET(CTEST_SRCS cmCTest.cxx
CTest/cmCTestConfigureHandler.cxx
CTest/cmCTestCoverageCommand.cxx
CTest/cmCTestCoverageHandler.cxx
+ CTest/cmParseGTMCoverage.cxx
CTest/cmParsePHPCoverage.cxx
CTest/cmCTestEmptyBinaryDirectoryCommand.cxx
CTest/cmCTestGenericHandler.cxx
diff --git a/Source/CTest/cmCTestCoverageHandler.cxx
b/Source/CTest/cmCTestCoverageHandler.cxx
index 309abb1..6c99928 100644
--- a/Source/CTest/cmCTestCoverageHandler.cxx
+++ b/Source/CTest/cmCTestCoverageHandler.cxx
@@ -11,6 +11,7 @@
*/
#include cmCTestCoverageHandler.h
#include cmParsePHPCoverage.h
+#include cmParseGTMCoverage.h
#include cmCTest.h
#include cmake.h
#include cmMakefile.h
@@ -373,21 +374,29 @@ int cmCTestCoverageHandler::ProcessHandler()
}
int file_count = 0;
file_count += this-HandleGCovCoverage(cont);
+ error = cont.Error;
if ( file_count 0 )
{
return error;
}
file_count += this-HandleTracePyCoverage(cont);
+ error = cont.Error;
if ( file_count 0 )
{
return error;
}
file_count += this-HandlePHPCoverage(cont);
+ error = cont.Error;
if ( file_count 0 )
{
return error;
}
+ file_count += this-HandleGTMCoverage(cont);
error = cont.Error;
+ if ( file_count 0 )
+{
+return error;
+}
std::setstd::string uncovered = this-FindUncoveredFiles(cont);
@@ -751,6 +760,18 @@ int cmCTestCoverageHandler::HandlePHPCoverage(
}
return static_castint(cont-TotalCoverage.size());
}
+//--
+int cmCTestCoverageHandler::HandleGTMCoverage(
+ cmCTestCoverageHandlerContainer* cont)
+{
+ cmParseGTMCoverage cov(*cont, this-CTest);
+ std::string coverageFile = this-CTest-GetBinaryDir() +
/gtm_coverage.mcov;
+ if(cmSystemTools::FileExists
Re: [CMake] multi-stage tests with valgrind
On 4/24/2012 12:07 PM, Leif Walsh wrote: Also, it would be nice if there was a way to specify that only some of the commands should be run with valgrind, but that may be asking too much. What I usually do is use the --trace-children option. I have even patched (accepted upstream now), valgrind to stop tracing when it runs certain programs. This is how cmake is tested through gmake. -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-developers] ninja bug
On 4/18/2012 5:14 PM, Richard Wackerbarth wrote: Bill, I hope that your question was not directed at me. As far as Ninja is concerned, I just set up the build-bot and check to see that it runs each night. In general, I have presumed that our interest is on the CMake side. Therefore, except for one build, the version of Ninja was been frozen weeks ago when I set it up. Should I need to upgrade, I need to be told to do so. Looks like you should do a ninja upgrade: Hi Bill, I think that newer versions of ninja contain a workaround for this problem: https://github.com/martine/ninja/pull/245 They claim this is fixed. Can you try and see? Thanks. -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
[cmake-developers] ninja bug
Any of the ninja folks have an idea why this test fails on FreeBSD: http://open.cdash.org/testDetails.php?test=140695467build=2197189 Run Build Command:/usr/local/bin/ninja ninja: ERROR: dependency cycle: CMakeFiles/bar.dir/bar.cxx.o - CMakeFiles/bar.dir/bar.cxx.o I am guessing something wrong with the output of -M on the machine? -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] ninja bug
On 4/18/2012 1:12 PM, Richard Wackerbarth wrote: Let me know if someone needs information from the run which has not been posted to the dashboard. I can bring the machine online and retrieve things. Actually, if you could send me the .d files in that test directory that might shed some light on the issue. -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] ninja bug
On 4/18/2012 1:12 PM, Richard Wackerbarth wrote: Let me know if someone needs information from the run which has not been posted to the dashboard. I can bring the machine online and retrieve things. OK, so looking at the .d files, they are wrong. I see this: CMakeFiles/bar.dir/bar.cxx.o CMakeFiles/bar.dir/bar.cxx.o: \ /home/dashboard/BotFarm/Chameleon-12/CMake/Ninja/CMake/Tests/BuildDepends/Project/bar.cxx \ regen.h noregen.h On other machines it looks like this: CMakeFiles/bar.dir/bar.cxx.o: \ /home/dashboard/BotFarm/Chameleon-12/CMake/Ninja/CMake/Tests/BuildDepends/Project/bar.cxx \ regen.h noregen.h Is there a known problem with gcc-4.2.2 and ninja? -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] ninja status
On 4/7/2012 5:03 PM, Peter Collingbourne wrote: On Sat, Apr 07, 2012 at 10:00:41PM +0200, Peter Kümmel wrote: On 07.04.2012 21:56, Peter Kümmel wrote: By default Ninja support is not enabled on Windows and Mac, somehow it was build the last times but I touched the cmake code there and introduced a FORCE: http://cmake.org/gitweb?p=stage/cmake.git;a=commitdiff;h=f93e81858b5e1243714ed7f26aadfc791a7b0ff0 I wonder how Ninja was enabled on the build server? Manually by editing CMakeCache.txt? I believe they just use -DCMAKE_ENABLE_NINJA=ON. I don't see why your change is necessary at all, please revert it. Thanks, Yes, please reverse the change. We want ninja off on Mac and Windows by default until all of the tests are passing. -DCMAKE_ENABLE_NINJA=ON will work, or you can put it in the CMakeCache.txt with a dashboard script. Thanks. -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] ninja status
On 4/3/2012 7:53 PM, Nicolas Desprès wrote: On next 68160664982d8f42ccfa8d68de778df823b52979 and on master 5e9c7731e16fc077a3637a02cb983d397329a23a with Ninja: The following tests FAILED: 1 - CMake.Install (Failed) 54 - ExportImport (Failed) 61 - Qt4Deploy (Failed) 84 - SimpleInstall (Failed) 86 - CPackComponents (Failed) 129 - BundleGeneratorTest (Failed) 227 - CMake.CheckSourceTree (Failed) I think I found the reason at least on one machine why builddpends is failing on the Mac: http://open.cdash.org/testDetails.php?test=140438743build=2155826 FAILED: /usr/bin/c++-arch ppc -arch i386 -isysroot /Developer/SDKs/MacOSX10.6.sdk -I. -MMD -MT CMakeFiles/foo.dir/foo.cxx.o -MF CMakeFiles/foo.dir/foo.cxx.o.d -o CMakeFiles/foo.dir/foo.cxx.o -c foo.cxx c++-4.2: -E, -S, -save-temps and -M options are not allowed with multiple -arch flags For multi-arch builds the -MF flag messes up for computing depends! The Free BSD build gets this error: http://open.cdash.org/testDetails.php?test=141544060build=2155994 ninja: ERROR: dependency cycle: CMakeFiles/bar.dir/bar.cxx.o - CMakeFiles/bar.dir/bar.cxx.o Any ideas? -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] Trying to build Paraview for Visual Studio Express 2010
On 3/14/2012 1:21 PM, Francisco Caraballo wrote: Hello everyone. I'm using CMAKE to build Paraview with Visual Studio Express 2010. I'm having a problem with the generated solution. The problem is that one of the entries generated for included libraries (the MPI libraries) should be semi colon separated but it is space separated. The result of this is that the linker generates a lot of errors when building the project. This is the problematic entry: LINK : fatal error LNK1104: cannot open file 'C:\Program Files (x86)\MPICH2\lib\mpi.lib C:\Program Files (x86)\MPICH2\lib\cxx.lib' I tried to fix it by changing the included libraries manually project by project, but it is taking way too long. How can I solve this? I'm not familiar enough with CMAKE's architecture to pinpoint what I need to change. I have reproduced your problem. Adding the ; manually worked for me. The problem is in FindMPI.cmake. It is already fixed in master of CMake. Here is the bug report and the fix: http://public.kitware.com/Bug/view.php?id=12874 -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] portable way for specifying whether everything or selective libs should be linked statically or as shared objects?
On 4/2/2012 9:57 PM, Bill Hoffman wrote: Well, you could implement it... :) This is an interesting interface: target_link_libraries(foo STATIC lib1 lib2 SHARED lib3 lib4) I would suggest that you move to the discussion to the cmake-developers list. I had another thought on this. Usually it is good enough to build all of your applications libraries static, and CMake does handle this. If you use the BUILD_SHARED_LIBS variable in your project you can get it to build all the libraries as either static or shared based on the value of this variable. For example: option(BUILD_SHARED_LIBS Build Shared Libraries OFF) add_library(foo foo.c) add_executable(bar bar.c) target_link_libraries(bar foo) IF BUILD_SHARED_LIBS = OFF then you get static foo, if it is ON, then you get a shared foo. The system libraries are another issue... :) -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] portable way for specifying whether everything or selective libs should be linked statically or as shared objects?
On 4/2/2012 9:18 PM, Christoph Anton Mitterer wrote: Hi. I started to switch over all my build systems to CMake recently and am stuck with the following. I thought of the C in CMake (cross-platform) that it means to that most basic tasks are handled for most platforms/compilers in a transparent way, but this seems all but be the case unfortunately. Nothing is perfect. :) This starts with commands like add_definitions where one have to use -D as parameter suffix (well eventually there could be compilers which don't use -D as option for this)... and ends with the following what I though would really be one of the basics in business. I was concern about this for a while, however, we have never seen a compiler that did not take -D. :) Actually, I ported to a VMS compiler once and it used a different flag, but I was able to fix it from the CMake source level, translating the -D to the correct flag for that compiler. So, -D is not really an issue, as CMake can correct for it if need be. The CMake api for definitions is -D. I'd like to allow users of my build system to specify whether - everything shall be linked statically (i.e. what gcc's --static does) - selectively select libraries (for which I allow it) to be linked statically as shared objects or to be dynamically loaded[0]. Isn't this possible? If it is how? I mean I've googled obviously and found ugly looking hacks where you set some magic variables to --static (e.g.)... but this is then absolutely importable. Rather I'd have expected some clean interface e.g. target_link_libraries(foo STATIC lib1 lib2 SHARED lib3 lib4) where obviously lib1/2 are linked statically and 3/4 as shared objects. That would be nice, and has been on the todo list for a while. However, it has never been important enough for someone to actually implement. Any ideas?! :-) Well, you could implement it... :) This is an interesting interface: target_link_libraries(foo STATIC lib1 lib2 SHARED lib3 lib4) I would suggest that you move to the discussion to the cmake-developers list. -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] Fwd: Fwd: Help with CMAKE
On 3/29/2012 6:19 PM, Sweety Pie wrote: Well after installing the Windows platform SDK am getting these msgs in the CMake screen: 1- The C compiler cl is not able to compile a simple test program. Although the VS can perfectly run all the codes I have previously. The other error is this: LINK : fatal error LNK1104: cannot open file 'OLDNAMES.lib' Any ideas?? Try the debug try compile thing I mentioned. -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] Fwd: Fwd: Help with CMAKE
On 3/29/2012 9:52 AM, Sweety Pie wrote: I have installed the Windows Platform SDK but the same error shows up:( I didnt get what do you mean by : Run CMake with --debug-trycompile ?? cmake --debug-trycompile ../path/to/yoursource This will run cmake in mode where it does not delete the results of try compile tests (which are failing for you). The files will be in CMakeFiles/CMakeTmp after you run with debug trycompile. You then load up the .sln file and see what happens when you build. However, from your original post you can see: 1LINK : fatal error LNK1104: cannot open file 'MSVCRTD.lib' This means for what ever reason the linker can not find the run time library for visual studio. That library is part of the SDK, however, it would seem that your SDK is install wrong. If you google fatal error LNK1104: cannot open file 'MSVCRTD.lib', there are lots of others with this issue. -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] Fwd: Fwd: Help with CMAKE
On 3/28/2012 2:01 AM, Sweety Pie wrote: Any one can advice plz??? Run CMake with --debug-trycompile, then load the .sln file found in the CMakeTmp directory from the IDE, and see what the errors actually are. -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
[Cmake-commits] CMake branch, next, updated. v2.8.7-3304-g954a27c
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 954a27c27832fda0e10826159c18ab08a3461346 (commit)
via 2f9ad7c6e6067b162d58d8a8628ba2c38106a6e9 (commit)
from 10310a62e06c075e713e03187d2d89c4b0e727fd (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=954a27c27832fda0e10826159c18ab08a3461346
commit 954a27c27832fda0e10826159c18ab08a3461346
Merge: 10310a6 2f9ad7c
Author: Bill Hoffman bill.hoff...@kitware.com
AuthorDate: Tue Mar 20 15:21:25 2012 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Tue Mar 20 15:21:25 2012 -0400
Merge topic 'findmpi_look_in_implicit_dirs' into next
2f9ad7c Fix FindMPI for the intel compiler on linux by looking in implict
directories.
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=2f9ad7c6e6067b162d58d8a8628ba2c38106a6e9
commit 2f9ad7c6e6067b162d58d8a8628ba2c38106a6e9
Author: Bill Hoffman bill.hoff...@kitware.com
AuthorDate: Tue Mar 20 15:18:53 2012 -0400
Commit: Bill Hoffman bill.hoff...@kitware.com
CommitDate: Tue Mar 20 15:18:53 2012 -0400
Fix FindMPI for the intel compiler on linux by looking in implict
directories.
Use the CMAKE_LANG_IMPLICIT_LINK_DIRECTORIES to look for libraries
that are in the -showme output from mpilang programs. This is because
some libraries reported by -showme are found there, and FindMPI will
fail if they are not found.
diff --git a/Modules/FindMPI.cmake b/Modules/FindMPI.cmake
index 1be4ccf..ae50ca7 100644
--- a/Modules/FindMPI.cmake
+++ b/Modules/FindMPI.cmake
@@ -354,6 +354,20 @@ function (interrogate_mpi_compiler lang try_libs)
# Extract the set of libraries to link against from the link command
# line
string(REGEX MATCHALL (^| )-l([^\ ]+|\[^\]+\) MPI_LIBNAMES
${MPI_LINK_CMDLINE})
+# add the compiler implicit directories because some compilers
+# such as the intel compiler have libraries that show up
+# in the showme list that can only be found in the implicit
+# link directories of the compiler. Do this for C++ and C
+# compilers if the implicit link directories are defined.
+if (DEFINED CMAKE_CXX_IMPLICIT_LINK_DIRECTORIES)
+ set(MPI_LINK_PATH
+${MPI_LINK_PATH};${CMAKE_CXX_IMPLICIT_LINK_DIRECTORIES})
+endif ()
+
+if (DEFINED CMAKE_C_IMPLICIT_LINK_DIRECTORIES)
+ set(MPI_LINK_PATH
+${MPI_LINK_PATH};${CMAKE_C_IMPLICIT_LINK_DIRECTORIES})
+endif ()
# Determine full path names for all of the libraries that one needs
# to link against in an MPI program
---
Summary of changes:
Modules/FindMPI.cmake | 14 ++
1 files changed, 14 insertions(+), 0 deletions(-)
hooks/post-receive
--
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-commits
Re: [cmake-developers] depend problem on windows
On 3/17/2012 8:26 PM, Peter Collingbourne wrote: Most likely some object files were not rebuilt as a result of header file changes. This will happen if the compiler does not support emitting dependency files, such as cl.exe. I think there are a couple of ways we could consider supporting cl.exe here: 1) Integrate CMake's built in dependency scanner. This will require some thought because the dependency scanner works on a per-target basis and Ninja reads dependency files on a per-file basis. 2) Come up with a way to use cl.exe's /showIncludes option to build a dependency list. There has been some discussion of this topic on the Ninja mailing list: https://groups.google.com/group/ninja-build/search?group=ninja-buildq=showincludesqt_g=Search+this+group Oh my So, the windows ninja generator IMO is totally useless right now... Without depend information on .h files incremental builds just won't work. I wonder if this is why the BuildDepend test is failing... If not, we should certainly add a test that touches a .h file and makes sure things rebuild. BuildDepend is also failing on the Mac, does ninja have the same issue with llvm? This looks like it should work: https://github.com/sgraham/ninja/blob/master/misc/cldeps.cc https://groups.google.com/group/ninja-build/browse_thread/thread/5d73ad7d26fba84d/898d7f0c808a32b0?lnk=gstq=showincludes#898d7f0c808a32b0 Is there a chance of getting this moved to master in ninja? Can we move it to the ninja windows binary that we are using for CMake? -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] Wrong cl.exe getting picked up
On 3/14/2012 6:39 PM, James Bigler wrote:
I have a system with several copies of Visual Studio installed.
When I set the generator for Visual Studio 9 2008 it ends up picking
up a different compiler:
CMAKE_C_COMPILER:FILEPATH=C:/Program Files (x86)/SCE/Common/VSI/bin/cl.exe
I think this is because of the following code in
CMakeDetermineCCompiler.cmake (which I can't figure out how it's invokes
by the cmake-gui or cmake.exe):
# Find the compiler.
IF (_CMAKE_USER_CXX_COMPILER_PATH)
FIND_PROGRAM(CMAKE_C_COMPILER NAMES ${CMAKE_C_COMPILER_LIST} PATHS
${_CMAKE_USER_CXX_COMPILER_PATH} DOC C compiler NO_DEFAULT_PATH)
ENDIF (_CMAKE_USER_CXX_COMPILER_PATH)
FIND_PROGRAM(CMAKE_C_COMPILER NAMES ${CMAKE_C_COMPILER_LIST} DOC C
compiler)
IF(CMAKE_C_COMPILER_INIT AND NOT CMAKE_C_COMPILER)
SET(CMAKE_C_COMPILER ${CMAKE_C_COMPILER_INIT} CACHE FILEPATH C
compiler FORCE)
ENDIF(CMAKE_C_COMPILER_INIT AND NOT CMAKE_C_COMPILER)
I believe the CMAKE_C_COMPILER_LIST contains cl as is the default of
CMAKE_GENERATOR_CC for VS generators.
Typically VS isn't in the default path, so the first two FIND_PROGRAM
commands don't yield any usable results. Then the next block sets the
CMAKE_C_COMPILER to cl, and everything is OK, because if it's run from
within the project, VS sets the paths so its cl.exe is first.
However if there is another cl.exe in the system PATH, then that version
will get picked up by the second FIND_PROGRAM, and thus cause a bit of
trouble later on when the copies of cl.exe aren't the same.
Does this seem like a bug to anyone? It seems like if you would want cl
to point to the same version as your copy of Visual Studio. Perhaps
$(VCInstallDir) could be used with a custom command to generate what VS
thinks the path should be?
Anyone have any thoughts?
I'm using CMake 2.8.2 and 2.8.6 on windows.
So, with the IDE generators CMake should not even look for cl. It does
not use that value anyway.
-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-developers] new ninja rebuild too much issue
On 3/14/2012 7:34 AM, Nicolas Desprès wrote: Nope if you like in the generated build.ninja build.ninja appears only once as an output using the RERUN_CMAKE rule. I rather think it is a bug in ninja of the restat implementation. What is the way to debug this? Can you get ninja to tell you why it is choosing to do a build of a file? This is quite reproducible. -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] ninja bug on windows
On 3/13/2012 10:39 PM, Peter Collingbourne wrote:
Maybe another time we can think about ways to improve PCH support,
but for now I guess we can add an OR Ninja to this test and add
OBJECT_OUTPUTS support to the Ninja generator.
I tried making that blog active for ninja and a I get a new error:
122: ninja: ERROR: 'PCH\foo_precompiled.pch', needed by
'CMakeFiles\foo.dir\foo1.c.obj', missing and no known rule to make it
So, Ninja is not handling OBJECT_OUTPUTS and OBJECT_DEPENDS correctly?
SET_SOURCE_FILES_PROPERTIES(foo_precompile.c PROPERTIES
OBJECT_OUTPUTS ${PCH_DIR}/foo_precompiled.pch)
# These source files use the precompiled header.
SET_SOURCE_FILES_PROPERTIES(${foo_SRCS} PROPERTIES
OBJECT_DEPENDS ${PCH_DIR}/foo_precompiled.pch)
-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
[cmake-developers] Ninja rebuild_cache fails with spaces in the path (windows and linux)
$ ninja rebuild_cache [1/1] Running CMake to regenerate build system... FAILED: cmd.exe /c cd C:\Users\hoffman\Work\My Builds\cmake-ninja C:\Users\hoffman\Work\My Builds\cmake-gmake\bin\cmake.exe -HC:/Users/hoffman/Work/My Builds/cmake -BC:/Users/hoffman/Work/My Builds/cmake-ninja CMake Error: The source directory C:/Users/hoffman/Work/My Builds/cmake-ninja/Builds/cmake-ninja does not exist. Specify --help for usage, or press the help button on the CMake GUI. ninja: build stopped: subcommand failed. This also fails on linux. -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] new ninja rebuild too much issue
On 3/14/2012 1:42 PM, Nicolas Desprès wrote: $ ../_build/bin/cmake -DCMAKE_ENABLE_NINJA=OFF . $ ../_build/bin/cmake -DCMAKE_ENABLE_NINJA=ON . $ ninja ninja: no work to do. $ ../_build/bin/cmake -DCMAKE_ENABLE_NINJA=OFF . $ ninja [...compile 200 outputs...] Duh, of course, my bad. It is the -DCMAKE_ENABLE_NINJA that is doing it -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] ninja bug on windows
On 3/13/2012 5:58 PM, Peter Kümmel wrote:
Not perfect because you tested it on an old build ;)
OK, I did a clean build tree, and it works now, thanks.
I just checked in a fix for
LinkDirectory
The remaining failing tests on windows are:
BuildDepends, ModuleDefinition, Plugin, and PrecompiledHeader
BuildDepends - not sure what is up with this one, but it fails on the
OSX as well.
ModuleDefinition - this one is because enable exports is not implemented
for ninja yet, the properties for that are done like this:
SET_TARGET_PROPERTIES(example_exe PROPERTIES
ENABLE_EXPORTS 1
OUTPUT_NAME example
# Test placing exe import library in unique directory.
ARCHIVE_OUTPUT_DIRECTORY ${CMAKE_ARCHIVE_OUTPUT_DIRECTORY}/exe
)
Plugin - fails for the same reason as ModuleDefinition
PrecompiledHeader - This one seems to be a dependency problem.
The first time you run it you get this:
122: Run Build Command:C:/cygwin/bin/ninja.exe
[3/4] Building C object CMakeFiles\foo.dir\foo1.c.obj
122: FAILED: C:\PROGRA~2\MICROS~1.0\VC\bin\cl.exe /nologo /DWIN32
/D_WINDOWS /W3 /Zm1000 /D_DEBUG /MDd /Zi /Ob0 /Od /RTC1
/Yufoo_precompiled.h /FIfoo_precompiled.h /FpC:/Users/hoffman/Work/My
Builds/cmake-ninja/Tests/PrecompiledHeader/PCH/foo_precompiled.pch
/FoCMakeFiles\foo.dir\foo1.c.obj /Fdfoo.pdb -c C:\Users\hoffman\Work\My
Builds\cmake\Tests\PrecompiledHeader\foo1.c
122:
122: foo1.c
122: C:\Users\hoffman\Work\My
Builds\cmake\Tests\PrecompiledHeader\foo1.c : fatal error C1083: Cannot
open precompiled header file: 'C:/Users/hoffman/Work/My
Builds/cmake-ninja/Tests/PrecompiledHeader/PCH/foo_precompiled.pch':
Permission denied
[3/4] Building C object CMakeFiles\foo.dir\foo_precompile.c.obj out:
foo_precom[3/4] Building C object CMakeFiles\foo.dir\foo2.c.obj
out: foo2.c
122: ninja: build stopped: subcommand failed.
1/1 Test #122: PrecompiledHeader ***Failed1.96 sec
If I run the test again, it passes. Might be that ninja is doing more
in parallel than gmake, nmake or visual studio.
-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
[cmake-developers] new ninja rebuild too much issue
It seems that if the CMakeCache.txt changes, and cmake re-runs, ninja rebuilds almost ever single .obj file. For example, if I turn on and off CMAKE_ENABLE_NINJA, Then it rebuilds all the .obj files instead of relinking just a few executables since the .obj files are there all ready. I had a report of this from someone else at Kitware working on a larger project. They said if they changed options with ccmake, that ninja rebuild the whole thing. Is there a way to debug ninja and have it print out why it is building something? Here is the example: $ ninja [1/1] Re-running CMake... -- Enable ninja generator. -- Found Qt4: C:/Users/hoffman/Work/qt-everywhere-opensource-src-4.7.4/bin/qmake.exe (found suitable version 4.7.4, required is 4.4.0) -- Found Qt4: C:/Users/hoffman/Work/qt-everywhere-opensource-src-4.7.4/bin/qmake.exe (found version 4.7.4) -- No CTest.UpdateCVS test with cygwin cvs.exe outside cygwin! -- Configuring done -- Generating done -- Build files have been written to: C:/Users/hoffman/Work/My Builds/cmake-ninja [1/206] Building CXX object Source\CMakeFiles\CMakeLib.dir\cmGlobalVisualStudio7[2/206] Building CXX object Source\CMakeFiles\CMakeLib.dir\cmGlobalVisualStudio7 This should be an almost no-op. Is it because everything depends on the build.ninja file? -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
[Cmake-commits] CMake branch, next, updated. v2.8.7-3181-g2771c36
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 2771c36f9476e0d7f948ad7f27665c675da77b44 (commit)
via c72fc37db884ac5c3249e7560945efb23559dd9f (commit)
from c62e13526d19b23d8dcdc1899d5147e58d8b7391 (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=2771c36f9476e0d7f948ad7f27665c675da77b44
commit 2771c36f9476e0d7f948ad7f27665c675da77b44
Merge: c62e135 c72fc37
Author: Bill Hoffman bill.hoff...@kitware.com
AuthorDate: Tue Mar 13 17:03:13 2012 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Tue Mar 13 17:03:13 2012 -0400
Merge topic 'ninja-generator' into next
c72fc37 Ninja generator fix for PDB files with spaces in the path.
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=c72fc37db884ac5c3249e7560945efb23559dd9f
commit c72fc37db884ac5c3249e7560945efb23559dd9f
Author: Bill Hoffman bill.hoff...@kitware.com
AuthorDate: Tue Mar 13 17:01:25 2012 -0400
Commit: Bill Hoffman bill.hoff...@kitware.com
CommitDate: Tue Mar 13 17:01:25 2012 -0400
Ninja generator fix for PDB files with spaces in the path.
This calls ConvertToOutputFormat on the PDB paths for pdb file paths
used in both library creation and the building of object files.
diff --git a/Source/cmNinjaNormalTargetGenerator.cxx
b/Source/cmNinjaNormalTargetGenerator.cxx
index af7bcd6..439f734 100644
--- a/Source/cmNinjaNormalTargetGenerator.cxx
+++ b/Source/cmNinjaNormalTargetGenerator.cxx
@@ -372,7 +372,8 @@ void cmNinjaNormalTargetGenerator::WriteLinkStatement()
targetOutputImplib.c_str(), cmLocalGenerator::SHELL);
}
- vars[TARGET_PDB] = this-GetTargetPDB();
+ vars[TARGET_PDB] = this-GetLocalGenerator()-ConvertToOutputFormat(
+this-GetTargetPDB().c_str(), cmLocalGenerator::SHELL);
std::vectorcmCustomCommand *cmdLists[3] = {
this-GetTarget()-GetPreBuildCommands(),
diff --git a/Source/cmNinjaTargetGenerator.cxx
b/Source/cmNinjaTargetGenerator.cxx
index 8fa367f..b9f997d 100644
--- a/Source/cmNinjaTargetGenerator.cxx
+++ b/Source/cmNinjaTargetGenerator.cxx
@@ -464,7 +464,8 @@ cmNinjaTargetGenerator
cmNinjaVars vars;
vars[FLAGS] = this-ComputeFlagsForObject(source, language);
vars[DEFINES] = this-ComputeDefines(source, language);
- vars[TARGET_PDB] = this-GetTargetPDB();
+ vars[TARGET_PDB] = this-GetLocalGenerator()-ConvertToOutputFormat(
+this-GetTargetPDB().c_str(), cmLocalGenerator::SHELL);
cmGlobalNinjaGenerator::WriteBuild(this-GetBuildFileStream(),
comment,
---
Summary of changes:
Source/cmNinjaNormalTargetGenerator.cxx |3 ++-
Source/cmNinjaTargetGenerator.cxx |3 ++-
2 files changed, 4 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
Re: [CMake] Defer compiler to different file in Visual Studio
On 3/12/2012 3:28 PM, Andreas Haferburg wrote:
Hello,
I'm currently evaluating Lazy C++ [1], which generates both header and
source files. I'm using add_custom_command() to invoke the generator on
*.lzz file, and for each .lzz file it generates one .hpp file and one
.cpp file. What I'm missing is the ability to compile the file I'm
currently editing from within Visual Studio.
With .cpp files it's possible to compile just one file, e.g. by
right-clicking it in the Solution Explorer, then selecting Compile. Or
even better, bind it to a hotkey.
So what I'd like to do is for each lzz file, set the compile command to
compile the corresponding cpp file. I can't imagine it being that hard,
since one would merely have to change the file extension in the command
line from cpp to lzz. Any ideas?
I'm not sure though, this might be more of a Visual Studio-specific
question than a CMake-specific one.
Lzz is not a compiler, but rather a code generator. I would set things
up so that you do something like this:
create_lzz_source_list(MY_CPP_HH_SOURCES foo.lzz bar.lzz car.zzz)
add_library(mylib ${MY_CPP_HH_SOURCES})
# create_lzz_sources would be a function that creates a bunch of custom
commands that run lzz on each lzz input file and create a .cpp and .hh
file. So, there should be a custom command for each .cpp and .hh file.
You should be able to click on one of those can select compile, and it
will run that file.
This is the exact type of thing that is done for the VTK code wrapper code.
-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] Defer compiler to different file in Visual Studio
On 3/12/2012 5:00 PM, Andreas Haferburg wrote:
Yea, that's pretty much what I've got so far. And yes, I realize that's
the way it's *supposed* to be set up. ;) I've posted my CMakeLists.txt
here if you want to have a look:
http://stackoverflow.com/a/9669388/872616
The only time I would really like to have anything to do with generated
files is if something goes wrong with the generation, but not during
normal development. I'd like to set up the tool chain such that I only
have to touch the .lzz files, and the .hpp/.cpp would be completely
hidden away in the build dir. Just as normally you wouldn't want to have
anything to do with .obj files, you know?
I don't think you can do that. However, you can make it a little nicer
with this change:
MAIN_DEPENDENCY ${CMAKE_CURRENT_SOURCE_DIR}/${filename}
From
Note that MAIN_DEPENDENCY is completely optional and is used as a
suggestion to visual studio about where to hang the custom command. In
makefile terms this creates a new target in the following form:
cmake --help-command add_custom_command
OUTPUT: MAIN_DEPENDENCY DEPENDS
COMMAND
However, when you right click on A.lzz and it will run lzz, and not the
full compiler cycle. You will have to right click on the generated .cpp
file to run the actual compiler. There is no way to collapse that into
one step.
-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
[cmake-developers] ninja bug on windows
I am seeing that ninja always wants to relink the executables for me every time it is run. The output is this: $ ninja [1/9] Linking C static library Utilities\cmlibarchive\libarchive\cmlibarchive.lib [2/9] Linking CXX executable bin\cmake.exe [3/9] Linking CXX executable bin\cmw9xcom.exe [4/9] Linking CXX executable bin\cpack.exe [5/9] Linking CXX executable bin\ctest.exe [6/9] Linking CXX executable Tests\CMakeLib\CMakeLibTests.exe [7/9] Generating ../Docs/ctest.txt [8/9] Generating ../Docs/cpack.txt [9/9] Generating ../Docs/cmake.txt Looks like the problem is libarchive getting recreated each time. -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] Ninja + CMake on a dashboard?
On 3/9/2012 12:21 PM, Steven Wilson wrote: Where does the Ninja generator currently live? Ie which branch in the sources, etc? I am keen to see support for the Ninja generator on Mac/Linux/Windows and would not mind working on it. Thanks, Steve The ninja support is in the next branch right now. Where is stands: - Linux seems to be all done - Windows is close, still a few failing tests, and needs to use a special ninja: http://sourceforge.net/projects/cmakescript/files/ninja.exe/download - The Mac needs the most work, as Framework and App bundle creation is not yet implemented. I am working on getting nightly dashboards for all three linux, windows and Mac going. I am going to turn on the ninja build by default on linux, and have an advanced cache option that will default to off for windows and mac. When the next version comes out it will be enabled on all platforms that are passing all the tests (currently only linux). The topic where the work happens is on the stage, and is called stage/ninja-generator. -Bill -- Bill Hoffman Kitware, Inc. 28 Corporate Drive Clifton Park, NY 12065 bill.hoff...@kitware.com http://www.kitware.com 518 881-4905 (Direct) 518 371-3971 x105 Fax (518) 371-4573 -- 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.7-3139-g6dc37e9
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 6dc37e91431b70c6f4ee55744b26eb103ee067f1 (commit)
via d2d492f492a8a6082345e439a9c15418f0d483db (commit)
from c5d6d48e1085d8ebe354a2260006181e4d301036 (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=6dc37e91431b70c6f4ee55744b26eb103ee067f1
commit 6dc37e91431b70c6f4ee55744b26eb103ee067f1
Merge: c5d6d48 d2d492f
Author: Bill Hoffman bill.hoff...@kitware.com
AuthorDate: Fri Mar 9 14:36:43 2012 -0500
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Fri Mar 9 14:36:43 2012 -0500
Merge topic 'ninja-generator' into next
d2d492f Add a cache option CMAKE_ENABLE_NINJA to enable the ninja generator.
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=d2d492f492a8a6082345e439a9c15418f0d483db
commit d2d492f492a8a6082345e439a9c15418f0d483db
Author: Bill Hoffman bill.hoff...@kitware.com
AuthorDate: Fri Mar 9 14:28:21 2012 -0500
Commit: Bill Hoffman bill.hoff...@kitware.com
CommitDate: Fri Mar 9 14:28:21 2012 -0500
Add a cache option CMAKE_ENABLE_NINJA to enable the ninja generator.
Make the option default to on, for platforms where CMake passes
all tests with the ninja generator. This is currently only Linux.
diff --git a/Source/CMakeLists.txt b/Source/CMakeLists.txt
index eb4327c..18f9b8b 100644
--- a/Source/CMakeLists.txt
+++ b/Source/CMakeLists.txt
@@ -353,7 +353,18 @@ IF (WIN32)
ENDIF(NOT UNIX)
ENDIF (WIN32)
-if(NOT WIN32)
+# turn on Ninja by default
+set(_CMAKE_DEFAULT_NINJA_VALUE TRUE)
+# turn it off for platforms where it does not pass all the
+# tests
+if(WIN32 OR APPLE)
+ SET(_CMAKE_DEFAULT_NINJA_VALUE FALSE)
+endif()
+SET(CMAKE_ENABLE_NINJA ${_CMAKE_DEFAULT_NINJA_VALUE} CACHE BOOL
+Enable the ninja generator for CMake. currently not fully working for
Windows or OSX)
+MARK_AS_ADVANCED(CMAKE_ENABLE_NINJA)
+IF(CMAKE_ENABLE_NINJA)
+ MESSAGE(STATUS Enable ninja generator.)
SET(SRCS ${SRCS}
cmGlobalNinjaGenerator.cxx
cmGlobalNinjaGenerator.h
@@ -368,7 +379,9 @@ if(NOT WIN32)
cmNinjaUtilityTargetGenerator.h
)
ADD_DEFINITIONS(-DCMAKE_USE_NINJA)
-endif()
+ELSE()
+ MESSAGE(STATUS Disable ninja generator.)
+ENDIF()
# create a library used by the command line and the GUI
ADD_LIBRARY(CMakeLib ${SRCS})
---
Summary of changes:
Source/CMakeLists.txt | 17 +++--
1 files changed, 15 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-developers] Rename Ninja generator?
I am wondering if we want to call the Ninja generator something like: Ninja Makefiles... It is not totally accurate, but it avoids code like this: IF(CMAKE_GENERATOR MATCHES Makefiles OR CMAKE_GENERATOR MATCHES Ninja) Also, it is more likely to work with existing cmake build files. I had to do the same thing with jom. Although with jom, it pretty much is a makefile. Thoughts? -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] Ninja windows
On 3/7/2012 5:24 PM, David Cole wrote: That might be fixed just now (perhaps) by stuff that I merged into 'next' this afternoon. Try with the very latest next of CMake. (One of the commits from Peter K. had not yet been merged into next and it dealt with directory creation...) That fixed it. I pulled from next again and it created the directories. -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
[CMake] Blog about CMake Fortran support
I worked with Julie Langou and Brad King to write a blog about Fortran support in CMake. It can be found here: http://www.kitware.com/blog/home/post/231 If anyone is interested in helping with the new cmake_add_fortran_subdirectory macro just send me an email, or bring it up on the cmake-developers list. Thanks. -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-developers] Build faild on Darwin? Don't know why?
On 3/6/2012 2:43 AM, Eric Noulard wrote: Did you see this bug report: http://public.kitware.com/Bug/view.php?id=13017 this may explain the sporadic failure on MacOS? Now I see that there is already a retry loop, [...] // since we get random dashboard failures with this one // try running it more than once int numTries = 4; bool res = false; while(numTries 0) [...] but if anti-virus is the reason for hdiutil failure may be there is a way to tell the anti-virus to stay away from mounted image? Our mac's do not have anti-virus. So, that is not the problem -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] Ninja windows
On 3/6/2012 12:17 PM, Peter Collingbourne wrote: The Ninja generator is disabled on Windows as it still doesn't yet work correctly with Ninja's master branch. It works to some degree with someone else's branch, but one of the required features on that branch (response file support) was recently merged into Ninja master, so hopefully someone on Windows will be able to add the necessary support to CMake soon. I would hold off on setting up a dashboard for Windows until we can at least build CMake with Ninja master. I am a bit confused. What are the features on someone else's branch that the CMake generator needs? What will it take to get this: http://sourceforge.net/projects/cmakescript/files/cmake-2.8.7.20120202-Ninja.exe into the CMake source tree? I would be OK, with a non-standard ninja as long as those patches are eventually going to be in ninja. I don't like having ninja windows cmake support outside of the main cmake dev tree. Could we do this: 1. integrate cmake windows ninja support into next 2. run a dashboard that uses a given ninja binary? My goal would be to make sure cmake windows ninja keeps building and working and other ninja work does not break the existing cmake windows support. I have been asking Windows developers to enable the generator locally for their own development by commenting out the IF(NOT WIN32) block. Perhaps once we set up Windows dashboards it would be better to introduce an internal variable (CMAKE_USE_NINJA?) which can be used to enable this generator on Windows, and have the dashboards use it. I would rather have it on by default and print some warning if it finds the wrong ninja, one that does not have the required patches. -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] Ninja windows
On 3/6/2012 1:29 PM, Peter Collingbourne wrote: We can certainly do that, but the ninja binary would need to be switched as soon as we get around to using rspfile in Ninja (and no sooner). OK, so is there a ninja binary that I can download right now that will work if I change the cmake files for cmake to build the ninja generator on windows? If so, where is it? My idea is to try it on my machine. If it works I will push the change into next that enables ninja on windows and setup a dashboard that pulls ninja from that spot each night. When cmake is changed to work with master ninja if someone updates that binary, then it will pull that and just work. That is what I have been doing with jom. -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
[CMake] Updated: CMake 2.8.7-1
CMake 2.8.7-1 is now available on Cygwin mirrors. Some of the notable changes in this release are: - improved Eclipse support - incremental improvements to the AUTOMOC feature added in the previous release - more cryptographic hash implementations (SHA1, SHA224, SHA256, SHA384, SHA512) - file(...) and string(...) command additions for computing hash values - added LINK_PUBLIC and LINK_PRIVATE options to target_link_libraries command - new module: DeployQt4 - and, as always, various minor bug fixes Similar to the previous release, we do not have pre-built binaries for the SunOS anymore. However, now we have two sets of installers for the Mac. The Darwin versions are for Mac OSX 10.4 and later, and are ppc;i386 universal binaries. The Darwin64 versions are for 10.6 and later, and are x86_64;i386 universal binaries. There was a bit of a network connectivity snag in building the binaries for the AIX platform today... Because of this, the tarballs for AIX will not be available until sometime next week. Following is the complete list of changes in this release. Please try this version of CMake on your projects and report any issues to the list or the bug tracker. Thanks for using CMake! -Bill Changes in CMake 2.8.7 (since 2.8.7-rc2) None Changes in CMake 2.8.7-rc2 (since 2.8.7-rc1) Alex Neundorf (5): automoc: default to strict mode, use CMAKE_AUTOMOC_RELAXED_MODE automoc: improved warning message in relaxed mode Remove trailing whitespace Add comment about one more problem of the C depency scanner. fix #12262: dependency scanning for ASM files Bill Hoffman (1): Fix the case where cmake --build failed with two project cmds in one file. Brad King (11): KWSys: Correctly handle empty environment variables FortranCInterface: Work around mingw32-make trouble with parens Xcode: Create separate rerun dependencies for subprojects (#12616) Fix Intel Fortran .vfproj files for VS 10 HP: Drive shared library linking with compiler front end Follow all dependencies of shared library private dependencies Do not link private dependent shared libraries on OS X 10.4 Avoid clobbering variable 'OUTPUT' in compiler tests (#12628) Fix and simplify Fortran test compiler compatibility check CTest: Recognize Intel errors without space before colon (#12627) Windows-GNU: Remove extra quotes in GNUtoMS rule variable David Cole (4): Release: Increase timeout for slow-testing cygwin build Modules: Use windres as rc compiler base name for cross-compiles (#12480) Tests: Only really run MFC test if we can build MFC apps (#11213) FindBoost: Quote possibly empty string argument (#12273) Eric NOULARD (1): CPackRPM fix #0012608 and unoticed related bug Johan Fänge (1): CMake: Fix progress reporting for custom targets (#12441) Mike McQuaid (2): Unset configurations variable when no build type. Improve component support and output indentation. Raphael Kubo da Costa (2): Remove the apparently outdated README in Source/QtDialog. QtDialog: Set Ctrl+Q as the shortcut for quitting the program. Tim Gallagher (2): FindLAPACK: Correct CMAKE_FIND_LIBRARY_SUFFIXES spelling (#12624) FindLAPACK: List thread libs to avoid link errors (#12625) Valat Sébastien (1): CTest: Do not get CDash version without drop site (#12618) Changes in CMake 2.8.7-rc1 (since 2.8.6) Aaron Ten Clay (1): VS: Add support for three new project properties (#12586) Alex Neundorf (60): fix #12392: handle CMAKE_CXX_COMPILER_ARG1 for Eclipse projects fix #12262: use the C dependency scanner also for ASM files fix #12465: detect the masm compiler ID (MSVC) Silence make on OpenBSD in FindPackageModeTest(#12508) Remove trailing whitespace Find Ruby on OpenBSD when installed from ports (#12507) Eclipse generator: detect Eclipse version Detect whether the current Eclipse version supports VirtualFolders Eclipse: don't create VirtualFolders if not supported Eclipse: better message when Eclipse version could not be determined automoc:run moc on the header if the source file contains include foo.moc Add copyright notices automoc: always run moc on the cpp file if there is a foo.moc included Eclipse: add virtual folder for each target Eclipse: move code for generating links to projects into separate function Eclipse: move code for generating links to targets into separate function Eclipse: add Build and Clean targets to targets Eclipse: detect number of CPUs, set CMAKE_ECLIPSE_MAKE_ARGUMENTS accordigly Eclipse: fix #12417, don't create wrong src pathentries FindLibXslt: also search libexslt and xsltproc don't crash in automoc
Re: [CMake] Where can I get the latest version of CMake for cygwin?
On 3/3/2012 10:13 AM, marco atzeri wrote: Bill, a simple RFU (request for upload) at cygwin-apps mailing list, with the link at your files http://www.cmake.org/files/v2.8/cmake-2.8.7-1.tar.bz2 http://www.cmake.org/files/v2.8/cmake-2.8.7-1-src.tar.bz2 will allow a larger audience and the correct deployment of your package. ' Yes, I know. I will try to be quicker about it in the future. It is there now. -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] Ninja + CMake on a dashboard?
On 3/6/2012 10:52 AM, Nicolas Desprès wrote: +1 for publishing I think it will boost up the development, bringing more people to work on it. It would be nice to fix the stuff that we know about, as people will of course start reporting bugs as soon as they find them. I guess as long as we note the limitations. Along the lines of the Windows support, what is the status? I don't see ninja support in the next branch of cmake. Just built it and there is no ninja generator yet. I would be happy to setup an experimental ninja windows generator dashboard for windows. However, we need the support to be in next. -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] Ninja + CMake on a dashboard?
On 3/6/2012 1:47 PM, Peter Collingbourne wrote: Obviously things won't work perfectly (if at all) for things like GUI applications or bundles. But there are a number of command line tools (such as LLVM/Clang) which do not use any of the OS X packaging stuff. I myself have used the generator to build LLVM/Clang on a Mac and I know a few people who do that regularly. I don't think we should exclude an entire platform just because things won't work for a subset of users, especially when it is easy to detect such cases and we can warn/error out. GUI on Mac is a big part of Mac users. This means no Qt application will work. It is a pretty big hole for that platform... -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] Updated: CMake 2.8.7-1
On 3/6/2012 12:53 PM, Robert Dailey wrote: Could you list the mirror URLs for me that were updated? I'm trying a few that are listed in the setup.exe for cygwin but I'm not seeing the new version. Still shows 2.8.4 for the mirrors I tried. Give it some time. I have no control over the mirrors getting updated. They just do over time. By this time next week, I would think all of them should be OK. -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] CMake configuration times with Microsoft Visual C++
On 3/6/2012 9:09 PM, Clifford Yapp wrote: We use the same configuration tests on all platforms in an effort to avoid having large chunks of platform-specific code in our build files, but we pay a price for this on Windows - the same test process is more than an order of magnitude slower with MSVC than (say) Linux. Does CMake launch the MSVC C++ compiler each time it needs to do a TRY_COMPILE or similar test? If so, does anybody know of any techniques for combining tests or some way to run a cl.exe instance as a daemon to which multiple files can be fed without needing a full restart of cl.exe? No, good way to do this on windows. The best you can do is to make sure it tries the windows stuff first, and that you remove as many try-compiles as possible when on Windows. Not only does CMake launch cl.exe, but it will also launch devenv.com with command line build arguments :) It is the only way to make sure that the compile environments are exact. So, you can optimize a build for windows with a bit of work, but there is nothing easy to do from CMake to make this faster. -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] Where can I get the latest version of CMake for cygwin?
On 3/2/2012 1:57 PM, Robert Dailey wrote: Latest version of CMake on the Cygwin installer is 2.8.4. I need 2.8.7. Where can I get 2.8.7 for Cygwin? We have them built, but I have been very bad at not getting them uploaded to the server. You can find them here: http://www.cmake.org/files/v2.8/cmake-2.8.7-1.tar.bz2 Should be able to install like this: cd / tar xvfj ~/Downloads/cmake-2.8.7-1.tar.bz2 I will try and get it up very soon. -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] Visual Studio 10 - GenerateDebugInformation always false
On 3/1/2012 9:00 AM, David Cole wrote: Are you using CMake 2.8.7? If not, please upgrade and try with that version. If there's still a problem after that, let us know. It might also be flags that you are setting in your project or cache that is doing this. Do you set CMAKE_CXX_FLAGS? -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
[Cmake-commits] CMake branch, next, updated. v2.8.7-2972-g62bb3fb
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 62bb3fb93b8077a3bdee8566f3d63177bbe088c6 (commit)
via 2557a080543a37f92e1908420842db8c90685304 (commit)
from b71538d30faa0d5ab0dbc4636a6f19e7e0e90f61 (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=62bb3fb93b8077a3bdee8566f3d63177bbe088c6
commit 62bb3fb93b8077a3bdee8566f3d63177bbe088c6
Merge: b71538d 2557a08
Author: Bill Hoffman bill.hoff...@kitware.com
AuthorDate: Wed Feb 29 22:29:13 2012 -0500
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Wed Feb 29 22:29:13 2012 -0500
Merge topic 'inject_code_via_variable' into next
2557a08 Fix typo in error message, and remove redundent test.
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=2557a080543a37f92e1908420842db8c90685304
commit 2557a080543a37f92e1908420842db8c90685304
Author: Bill Hoffman bill.hoff...@kitware.com
AuthorDate: Wed Feb 29 22:28:06 2012 -0500
Commit: Bill Hoffman bill.hoff...@kitware.com
CommitDate: Wed Feb 29 22:28:06 2012 -0500
Fix typo in error message, and remove redundent test.
diff --git a/Source/cmProjectCommand.cxx b/Source/cmProjectCommand.cxx
index 4c1abcf..fcf0a49 100644
--- a/Source/cmProjectCommand.cxx
+++ b/Source/cmProjectCommand.cxx
@@ -88,7 +88,7 @@ bool cmProjectCommand
if(!readit !cmSystemTools::GetFatalErrorOccured())
{
std::string m =
-could not find load file:\n
+could not find file:\n
;
m += include;
this-SetError(m.c_str());
diff --git a/Tests/CMakeOnly/CMakeLists.txt b/Tests/CMakeOnly/CMakeLists.txt
index 629f578..a1551ca 100644
--- a/Tests/CMakeOnly/CMakeLists.txt
+++ b/Tests/CMakeOnly/CMakeLists.txt
@@ -23,8 +23,6 @@ add_CMakeOnly_test(AllFindModules)
add_CMakeOnly_test(TargetScope)
-add_CMakeOnly_test(ProjectInclude)
-
add_test(CMakeOnly.ProjectInclude ${CMAKE_CMAKE_COMMAND}
-DTEST=ProjectInclude
-DCMAKE_ARGS=-DCMAKE_PROJECT_ProjectInclude_INCLUDE=${CMAKE_CURRENT_SOURCE_DIR}/ProjectInclude/include.cmake
---
Summary of changes:
Source/cmProjectCommand.cxx|2 +-
Tests/CMakeOnly/CMakeLists.txt |2 --
2 files changed, 1 insertions(+), 3 deletions(-)
hooks/post-receive
--
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-commits
[cmake-developers] Nightly Binary not building on windows
The nightly binary for CMake is not building because of a test failure: http://open.cdash.org/testDetails.php?test=136868750build=2046004 CMake Error at CMakeLists.txt:52 (message): Subversion_VERSION_SVN has unexpected content Call Stack (most recent call first): CMakeLists.txt:74 (check_version_string) The following tests FAILED: 185 - CMakeOnly.AllFindModules (Failed) Any ideas? -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] Nightly Binary not building on windows
On 2/28/2012 1:14 PM, Eric Noulard wrote: 2012/2/28 Bill Hoffmanbill.hoff...@kitware.com: The nightly binary for CMake is not building because of a test failure: http://open.cdash.org/testDetails.php?test=136868750build=2046004 CMake Error at CMakeLists.txt:52 (message): Subversion_VERSION_SVN has unexpected content Call Stack (most recent call first): CMakeLists.txt:74 (check_version_string) The following tests FAILED: 185 - CMakeOnly.AllFindModules (Failed) This commit cffce2ffb366cd5c598f56e8f0789124a6d1b7a9 added at least this check_version_string(SUBVERSION Subversion_VERSION_SVN) Subversion_VERSION_SVN seems empty (from the error message)? The module is named FindSubversion.cmake make be check_version_string(SUBVERSION Subversion_VERSION_SVN) should simply be: check_version_string(Subversion Subversion_VERSION_SVN) upper/lower case trouble? Mixed-case leads to trouble since (from FindSubversion.cmake) we have: # Subversion_FOUND - true if the command line client was found # SUBVERSION_FOUND - same as Subversion_FOUND, set for compatiblity reasons OK, the problem is that svn is not working on the machine: $ /cygdrive/c/Program\ Files\ \(x86\)/Subversion/svn info svn: Can't determine the user's config path However, this should not be an error. That is the point of this test. Even if something is wrong, it should not error out. It should continue unless it is required. Perhaps the check_version_string function should be made aware that it should only error out if REQUIRED is set. -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] Nightly Binary not building on windows
On 2/28/2012 1:38 PM, David Cole wrote: Wait for Eike to reply here. He's been requiring version variables to be set if the package is found in this test. I'm sure he'll either patch this up so it works or exclude svn from the version variable test depending on how hard it is to detect this situation... If the package is not required, then we can not error out if it finds a bad copy of some software and can't figure out the version number. No matter what find_package(foo) Can not cause an error at CMake time. -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] Nightly Binary not building on windows
On 2/28/2012 1:57 PM, Brad King wrote:
On 2/28/2012 1:53 PM, Bill Hoffman wrote:
No matter what
find_package(foo)
Can not cause an error at CMake time.
That isn't the line causing the error. It's the AllFindModules test
that wants to know that the returned version information is as expected.
This is a real test failure because the FindSubversion module is not
properly detecting the version number of svn. The Find module needs
to be fixed for this case.
-Brad
I disagree... :)
The test does this:
message(STATUS module: ${module})
include(${module})
That should not error out if it finds a bad version of software that
gives a bogus version string. I thought you could include any module
and not get a cmake error at configure time unless you set required.
-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] mingw vs MSYS makefiles
On 2/24/2012 5:25 AM, Andrea Crotti wrote: Ideally yes, unfortunately it's not really possible to avoid the python call, without rewriting a lot of code in CMake/C (which is not a good idea). I will check what is the requirement, if the MinGW make is fine then I'll just use that otherwise I'll debug the problem with the MSYS.. Well, the problem is something is calling python with the wrong path, it is using the msys path, but the calling program can not start python from /c/python. From what you sent it is hard to tell what the calling program is that is trying to launch python. You should look at the generated Makefiles and see what is going on. Also, how is python called from your CMake code? -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 VTK_WRAP_PYTHON
On 2/23/2012 10:46 AM, elhadj meljane wrote:
Hi all
I am trying to cmake a CMakeLIsts.txt and I am getting the following error
CMake Error at CMakeLists.txt:50 (VTK_WRAP_PYTHON):
Unknown CMake command VTK_WRAP_PYTHON
here is the line that the cmake does not like in the CMakeLists file
VTK_WRAP_PYTHON(cpptrackingPython PYTHON_SOURCES ${WRAP_LIST})
I do have vtk-5.2 and python Python 2.6.5 installed on my machine. I
tried VTK_WRAP_PYTHON2 and VTK_WRAP_PYTHON3 and I got the same error.
the code that I m having trouble with, worked three years ago without
any problem (I didn't develop this code I am just using it ...) now that
I changed the machine, I am getting this error.
Thanks for your help!
This is really a question for the VTK mailing list.
-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] mingw vs MSYS makefiles
On 2/23/2012 2:12 PM, Kenneth Boyd wrote: On 2/23/2012 5:20 AM, Andrea Crotti wrote: I have MinGW installed in my system and today I added the bin directory to the path, so I was able to run all the commands also from a standard shell. But now CMake complains: CMake Error at c:/Program Files/CMake 2.8/share/cmake-2.8/Modules/CMakeMinGWFindMake.cmake:20 (MESSAGE): sh.exe was found in your PATH, here: C:/MinGW/msys/1.0/bin/sh.exe For MinGW make to work correctly sh.exe must NOT be in your path. Run cmake from a shell that does not have sh.exe in your PATH. If you want to use a UNIX shell, then use MSYS Makefiles. So well I thought I could just use the MSYS Makefiles instead, but reconfiguring and with the same target that doesn't work: Scanning dependencies of target cleanup_system process_begin: CreateProcess(NULL, /c/python25/python.exe h:/git_projs/PSI_Hamburg/utils/utils/bin/clean_global.py, ...) failed. make (e=2): The system cannot find the file specified. epd-make[3]: *** [CMakeFiles/cleanup_system] Error 2 epd-make[2]: *** [CMakeFiles/cleanup_system.dir/all] Error 2 epd-make[1]: *** [CMakeFiles/run_as_user.dir/rule] Error 2 epd-make: *** [run_as_user] Error 2 Does it mean that I have something which is not portable in my CMakeLists? The solution might be remove the MinGW bin from the path of course, but I would lose the nice commands from each shell and I would also like to understand what is going on.. The MingW platform file is explicitly programmed to reject MingW bash. Bill Hoffman implicitly rejected my offer to provide a patch to enable a new generator as of CMake 2.6.2: http://public.kitware.com/Bug/view.php?id=7870 . Without a policy reversal on his part, I would assume this platform (which is also mine) is intentionally unsupported. gmake behaves differently if /bin/sh is in the PATH. The makefiles for MinGW Makefiles are written for gmake running in the mode where it does not have /bin/sh. The makefiles for Msys Makefiles are written so that they work with /bin/sh mode of gmake. It all has to do with which shell is running the commands from gmake. In the MinGW case, it is using a windows cmd.com shell, and in the Msys case it is using /bin/sh. They are of course very different. There is no way to force gmake to use a particular shell, it is all based on what is in the PATH. About bug 7870, I am not sure that I understood that you were proposing a new generator. I thought the bug was more about getting bootstrap to work. It does seem that there is an issue with allowing make.exe to work. I think if you set CMAKE_MAKEPROGRAM to make.exe it should work. A patch that found different make.exe or make-mingw and then tested them would not be rejected. I still don't see how we can avoid having separate generators for MinGW and Msys, and I certainly don't think a third one would help reduce confusion. Also, I think someone might have fixed the bootstrap issues with Msys at this point, but I am not sure... A lot has changed since 2008 when that bug was created... -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] mingw vs MSYS makefiles
On 2/23/2012 3:40 PM, Kenneth Boyd wrote: On 2/23/2012 1:46 PM, Bill Hoffman wrote: Right. Unfortunately, I have MingW installed from official tarballs, rather than the MSYS executable installer; the MSYS installer *.exe critically failed for me back in 2001, so once I got a working install procedure from official tarballs I stuck with it. What is happening is that I have an official MingW /bin/sh in my path (which triggers MSYS), but the pathnames required by windows-side tools such as MingW32 gcc are still Windows-ish (MingW). AFAIK, if /bin/sh is in your PATH gmake goes into shell mode and you can not use windows style shell stuff in the makefile. If you take out the check that I put in, it should fail in some other way. I put the check in early with a message to avoid people getting the weird errors later. It does seem that there is an issue with allowing make.exe to work. I think if you set CMAKE_MAKEPROGRAM to make.exe it should work. Ok. A patch that found different make.exe or make-mingw and then tested them would not be rejected. I still don't see how we can avoid having separate generators for MinGW and Msys, and I certainly don't think a third one would help reduce confusion. I'm assuming that the Msys generator is intended for the results of the MSYS installer *.exe . As such, I'd prefer to assume the current MSYS generator is known-good for that case. My impression (please correct if inaccurate) is that it would be preferable to have the final patch augment the MSYS generator to discern which filepath convention is expected. I don't see what case your 3rd generator will handle. Seems to me there are only two cases regardless of how it was installed: 1. you have /bin/sh in your PATH and gmake runs commands via /bin/sh 2. you do not have /bin/sh in your PATH and gmake runs commands via the native windows shell. I wonder if the plain Unix Makefiles generator would work for you? -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] mingw vs MSYS makefiles
On 2/23/2012 5:18 PM, Alan W. Irwin wrote: make commands. One is called MinGW/bin/mingw32-make.exe and is used by the MinGW Makefiles generator while the other is called MinGW/msys/1.0/bin/make.exe and is used by the MSYS Makefiles generator. I presume those two executables correspond to various forks of gmake. The difference is the c runtime that they use. The MinGW one uses the Microsoft run time and so understands MS paths (c: and \). The msys one links to the msys runtime, and understands msys stuff like /c/foo instead of c:/foo. Both of these things aside, gmake upstream does look for sh: http://unxutils.sourceforge.net/ has the following info : From v3.77 upwards, make searches for a sh.exe on the path. If it does not find one, it switches to win32 make mode that is it uses intermediate batch files for command processing. So, both versions of gmake are actually the same source code but they are built with different c run time libraries. -- Bill Hoffman Kitware, Inc. 28 Corporate Drive Clifton Park, NY 12065 bill.hoff...@kitware.com http://www.kitware.com 518 881-4905 (Direct) 518 371-3971 x105 Fax (518) 371-4573 -- 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] mingw vs MSYS makefiles
On 2/23/2012 6:20 AM, Andrea Crotti wrote: So well I thought I could just use the MSYS Makefiles instead, but reconfiguring and with the same target that doesn't work: Scanning dependencies of target cleanup_system process_begin: CreateProcess(NULL, /c/python25/python.exe h:/git_projs/PSI_Hamburg/utils/utils/bin/clean_global.py, ...) failed. make (e=2): The system cannot find the file specified. epd-make[3]: *** [CMakeFiles/cleanup_system] Error 2 epd-make[2]: *** [CMakeFiles/cleanup_system.dir/all] Error 2 epd-make[1]: *** [CMakeFiles/run_as_user.dir/rule] Error 2 epd-make: *** [run_as_user] Error 2 I don't think anyone really addressed your question. Your question seems to have taken on a whole new life The problem seems to be that your cmake file is creating makefiles that use a python program in them. For some reason python is not working from an msys shell for you. You should debug that, and try to figure out how to get a python that does work, or figure out why this python is failing under msys. Moral of the story, don't depend on python in your build, use cmake scripts if possible, or c programs that you 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://www.cmake.org/mailman/listinfo/cmake
[CMake] Announce: Kitware Holding CMake course April 2 in Lyon France
Kitware will be holding a developers training course on April 2, 2012 in Lyon, France. This 1-day course will cover CMake, CTest, CPack and CDash. Please visit our web site for more information and registration details (early registration ends March 19th!) at either: http://www.kitware.com/products/protraining.php?course=04/02/2012 (in English) or http://www.kitware.fr/products/protraining.php?course=04/02/2012 (in French) Note that the course will be taught in English. If you have any questions, please contact us at courses at kitware.com or formations at kitware.fr -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-developers] ninja spaces in the path do not work on linux
On 2/17/2012 12:26 PM, Nicolas Desprès wrote: I think it is a bug in the generator which do not escape the space properly using the $ character as supported by Ninja. -- Nicolas Desprès Will you be able to fix that? Thanks. -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] ninja spaces in the path do not work on linux
On 2/17/2012 3:16 PM, Nicolas Desprès wrote: I think yes. It is just a matter of time. My weekend is already overloaded. I'll try to do it. If Peter or someone else in the community comes up with a patch before me everybody would be happy :-) I'll try to do my best. I could give it a try if you pointed me to the right spot in the code... -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] ninja broken on windows?
On 2/16/2012 2:57 PM, Peter Kümmel wrote: They are not interested. There is another patch in the pipeline but with this the current generator doesn't work. Use the official ninja and drop Win atm. Bummer. I am most interested in windows. Would love to stop using gmake... Seems like they are doing lots of stuff with .d files for windows. So, they seem interested in supporting the platform. Is there something we can change in the cmake generator to make it work with the way ninja is today, and will be for the foreseeable future? -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] ninja broken on windows?
On 2/16/2012 5:19 PM, David Cole wrote: On Thu, Feb 16, 2012 at 5:08 PM, Richard Wackerbarth rich...@nfsnet.org mailto:rich...@nfsnet.org wrote: What are we trying to accomplish here? 2 things: (1) Keep the CMake ninja generator working with the changing state of the CMake code base (primary) (2) Understanding what version of ninja works good on all the platforms on which it is built I just created a ctest script that will pull a clean ninja from git://github.com/martine/ninja.git, build ninja, then use that ninja to run a dashboard of CMake. I did find out that the ninja generator is not part of the cmake bootstrap. So, that test can not run. We might want to add that feature. I am on the fence on that one. We could just disable the test like we do for Xcode. Anyway the script (work in progress) is here: http://www.cdash.org/CDash/viewNotes.php?buildid=2012841 In the nightly section of CMake: http://www.cdash.org/CDash/index.php?project=CMake The results are here: exarius-linux.kitware Linux64-ninja Summary here: http://www.cdash.org/CDash/buildSummary.php?buildid=2012841 -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
[cmake-developers] Ninja help
Where at are the versions of Ninja that I need to use with CMake for: Windows: Mac: Linux: I have seen several git branches mentioned in emails, and it is not clear to me where to get the right Ninja for CMake on all platforms. To setup nightly testing, is there a master git branch that we should test against? This would let us know if Ninja breaks CMake support right away. Thanks. -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] Ninja help
On 2/15/2012 11:20 AM, Nicolas Desprès wrote: For compiling and testing you can find all the information in the HACKING file. Well, this is ugly: --HACKING Windows development on Windows: - install mingw, msys, and python - in the mingw shell, put Python in your path, and: python bootstrap.py - to reconfigure, run 'python configure.py' - remember to strip the resulting executable if size matters to you - you'll need to rename ninja.exe into my-ninja.exe during development, otherwise ninja won't be able to overwrite itself when building --HACKING It would be really nice if ninja had a CMake build system with it for windows development. It basically looks like a bunch of c++ files. Having to have python to build ninja is a pain for setting up a visual studio ninja dashboard. -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] Ninja help
On 2/15/2012 1:01 PM, David Cole wrote: But this is true with every CMake generator *except* for the Unix Makefiles generator. And you don't have to build it twice. On most of our other dashboards, we simply use an installation of a recent stable release as the CMake/ctest that drives the dashboard. Right, so just build the most recent ninja capable cmake you can, and use that to drive the dashboard. BTW, I am working on seeing how the windows build works, and the stage/ninja-generator branch does not build ninja stuff on windows. # Ninja only works on UNIX. IF(UNIX) I assume this is old, and should be fixed? -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
[cmake-developers] ninja spaces in the path do not work on linux
- On linux spaces in the path do not work, I get this error: http://www.cdash.org/CDash/viewBuildError.php?buildid=2009436 -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] ninja broken on windows?
On 2/15/2012 5:52 PM, Peter Kümmel wrote: In summary: - use the CMakeLists.txt from https://github.com/syntheticpp/ninja/tree/cmake - on Windows use ninja from https://github.com/syntheticpp/ninja/tree/token-splitter and wait and see what happens with official ninja I can live without the CMakeLists.txt to build ninja. The python thing works pretty easy. However, having to pull different clones of ninja to test for Windows ninja cmake builds is an issue. What are the chances of this being accepted upstream? Are there objections? -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] Ninja + CMake on a dashboard?
On 2/15/2012 10:27 AM, Nicolas Desprès wrote: = I may have an Ubuntu box and maybe a OS X 10.7 machine, depending on what is required. What do I have to setup? Is the machine required to be up and running all the time? Cheers, It is required that the machine submit once a day. To submit it needs to pull from git and send xml to CDash. There is some info from here: http://www.cmake.org/cmake/resources/testing.html Ninja will be a bit tricky to setup, as you will most likely have to pull ninja from some git somewhere and build that first before you can use it for the CMake dashboard. -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] Ninja + CMake on a dashboard?
On 2/15/2012 11:03 AM, Nicolas Desprès wrote: What's happens if it misses some day because the machine is not running for any reason ? Weekend, maintenance, etc... ? Not a bit deal, unless it is missing more often than not. I would say 95% up would be fine. If it is up and down all the time, it is more annoying than useful. That's should not be a problem since I already have this kind of setup on my machine. That would be great. -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] ctest return code
On 2/15/2012 2:44 PM, Tom Deblauwe wrote: Hello, In attachment a project which illustrates the problem. Just change the directory in the ctest script continuous_dashboard.cmake to where your source is. Then i run ctest in my bash script. I'm in git bash on windows now, but I get the problem on linux too. tdb@PCTDBP /c/werk/cmake_tests $ ctest -S dashboard/continuous_dashboard.cmake -VV \ ... 1: Test timeout computed to be: 600 1/1 Test #1: testMylibTest ***Failed 0.05 sec 0% tests passed, 1 tests failed out of 1 Total Test time (real) = 2.44 sec The following tests FAILED: 1 - testMylibTest (Failed) Then after ctest exits I do: tdb@PCTDBP /c/werk/cmake_tests $ echo $? 0 As you can see: the test failed, but ctest just returns 0. That is because the ctest -S script worked. If you want it to fail, you will have to modify the continuous_dashboard.cmake script to look at the results of ctest_test and then use a message(FATAL_ERROR tests failed) if there was a failing test. -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] ctest return code
On 2/15/2012 3:57 PM, Tom Deblauwe wrote: It is apparently a combination of the two things, first I had to check the RETURN_VALUE of the ctest_test command and then issue a fatal_error when not zero. Secondly: This works if I test it like you suggest in a command window: the %errorlevel% is set. However in the git bash shell thingy on windows, I always get 0. I tried it now in linux too, and there the echo $? is working and is showing me the error code instead of 0. OK, I was wrong. It should work. It is just git bash that is broken... -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
[Cmake-commits] CMake branch, next, updated. v2.8.7-2632-g2128373
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 2128373082002cd11c2e3802d8346fc6d83df6f3 (commit)
via 087bea35c158f336a3193a97b06bdce3d8ce35f8 (commit)
from 733ac6bd2dc822daa6b6d58a789cbd081ef6a037 (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=2128373082002cd11c2e3802d8346fc6d83df6f3
commit 2128373082002cd11c2e3802d8346fc6d83df6f3
Merge: 733ac6b 087bea3
Author: Bill Hoffman bill.hoff...@kitware.com
AuthorDate: Wed Feb 15 22:46:33 2012 -0500
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Wed Feb 15 22:46:33 2012 -0500
Merge topic 'fix_fortran_dir_two_dirs' into next
087bea3 Allow two cmake_add_fortran_subdirectory calls in the same project.
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=087bea35c158f336a3193a97b06bdce3d8ce35f8
commit 087bea35c158f336a3193a97b06bdce3d8ce35f8
Author: Bill Hoffman bill.hoff...@kitware.com
AuthorDate: Wed Feb 15 22:42:31 2012 -0500
Commit: Bill Hoffman bill.hoff...@kitware.com
CommitDate: Wed Feb 15 22:42:31 2012 -0500
Allow two cmake_add_fortran_subdirectory calls in the same project.
Configure the build_mingw.cmake.in config_mingw.cmake.in files
into the binary directory of the directory being built, not the
top level binary directory for the project.
diff --git a/Modules/CMakeAddFortranSubdirectory.cmake
b/Modules/CMakeAddFortranSubdirectory.cmake
index ddb79fb..abd9100 100644
--- a/Modules/CMakeAddFortranSubdirectory.cmake
+++ b/Modules/CMakeAddFortranSubdirectory.cmake
@@ -50,7 +50,7 @@ include(CheckLanguage)
include(ExternalProject)
include(CMakeParseArguments)
-function(_setup_mingw_config_and_build source_dir)
+function(_setup_mingw_config_and_build source_dir build_dir)
# Look for a MinGW gfortran.
find_program(MINGW_GFORTRAN
NAMES gfortran
@@ -91,11 +91,11 @@ function(_setup_mingw_config_and_build source_dir)
string(REPLACE \\ MINGW_PATH ${MINGW_PATH})
configure_file(
${_MS_MINGW_SOURCE_DIR}/CMakeAddFortranSubdirectory/config_mingw.cmake.in
-${CMAKE_CURRENT_BINARY_DIR}/config_mingw.cmake
+${build_dir}/config_mingw.cmake
@ONLY)
configure_file(
${_MS_MINGW_SOURCE_DIR}/CMakeAddFortranSubdirectory/build_mingw.cmake.in
-${CMAKE_CURRENT_BINARY_DIR}/build_mingw.cmake
+${build_dir}/build_mingw.cmake
@ONLY)
endfunction()
@@ -144,15 +144,15 @@ function(cmake_add_fortran_subdirectory subdir)
endif()
endforeach()
# create build and configure wrapper scripts
- _setup_mingw_config_and_build(${source_dir})
+ _setup_mingw_config_and_build(${source_dir} ${build_dir})
# create the external project
externalproject_add(${project_name}_build
SOURCE_DIR ${source_dir}
BINARY_DIR ${build_dir}
CONFIGURE_COMMAND ${CMAKE_COMMAND}
--P ${CMAKE_CURRENT_BINARY_DIR}/config_mingw.cmake
+-P ${build_dir}/config_mingw.cmake
BUILD_COMMAND ${CMAKE_COMMAND}
--P ${CMAKE_CURRENT_BINARY_DIR}/build_mingw.cmake
+-P ${build_dir}/build_mingw.cmake
INSTALL_COMMAND
)
# make the external project always run make with each build
---
Summary of changes:
Modules/CMakeAddFortranSubdirectory.cmake | 12 ++--
1 files changed, 6 insertions(+), 6 deletions(-)
hooks/post-receive
--
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-commits
[cmake-developers] All 4 nightly builds worked last night!
After a long break, all of the nightly builds are back: http://www.cdash.org/CDash/viewTest.php?onlypassedbuildid=2004336 It has been some time, according to CDash: Tests have been failing since 2012-01-02T00:32:26 EST (42 days) The main trouble was the upgrade in Qt that was required. Thanks all! -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
[cmake-developers] 185 - CMakeOnly.AllFindModules (Failed)
On our linux release machine we are getting an error in the modules that is preventing the release from being made. The error is: CMake Error at CMakeLists.txt:58 (message): GNUPLOT_VERSION_STRING has unexpected content -- Configuring incomplete, errors occurred! CMake Error at Test.cmake:11 (message): CMake failed to configure AllFindModules The gnuplot on that machine is sooo old it does not respond to --version... The linux is very old so that CMake is forward compatible with other machines. -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] MSBuild and automatic project file regenation
I took a look at this, and it is behaving as expected with VS. VS does
NOT have a depend on compile flags. You can change a .vcproj file and
the flags it uses all you want, and VS will NOT rebuild any files
because of that.
So, as far as VS is concerned your source file has not changed and does
not need to rebuild. I modified your example and --build works
perfectly (I change the NUMBER in the CMakeLists.txt and main is rebuilt
with one invocation of cmake --build .)
CMAKE_MINIMUM_REQUIRED(VERSION 2.8 FATAL_ERROR)
PROJECT(BUILD C)
FILE(WRITE ${CMAKE_BINARY_DIR}/main.c #include stdio.h
#include main.h
int main(void)
{
printf(\%d\\n\,NUMBER);
return 0;
}
)
include_directories(${CMAKE_BINARY_DIR})
ADD_EXECUTABLE(main main.c)
set(NUMBER 2)
configure_file(main.h.in main.h)
$ cat ../main.h.in
#define NUMBER @NUMBER@
--
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.7-2550-gd7510a4
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 d7510a4a4f698fdbe1c951c65ce2392e934bb3ff (commit)
via 9fb9416f78a83c59e1260ec1ec0699618be1b95f (commit)
from 3d606bbc5c28a54642cb57e2b2947c0483cf0335 (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=d7510a4a4f698fdbe1c951c65ce2392e934bb3ff
commit d7510a4a4f698fdbe1c951c65ce2392e934bb3ff
Merge: 3d606bb 9fb9416
Author: Bill Hoffman bill.hoff...@kitware.com
AuthorDate: Thu Feb 9 20:36:06 2012 -0500
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Thu Feb 9 20:36:06 2012 -0500
Merge topic 'change_qmake_path' into next
9fb9416 Use upgraded qt on linux build machine.
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=9fb9416f78a83c59e1260ec1ec0699618be1b95f
commit 9fb9416f78a83c59e1260ec1ec0699618be1b95f
Author: Bill Hoffman bill.hoff...@kitware.com
AuthorDate: Thu Feb 9 20:33:58 2012 -0500
Commit: Bill Hoffman bill.hoff...@kitware.com
CommitDate: Thu Feb 9 20:33:58 2012 -0500
Use upgraded qt on linux build machine.
diff --git a/Utilities/Release/magrathea_release.cmake
b/Utilities/Release/magrathea_release.cmake
index 549460e..1b2ae02 100644
--- a/Utilities/Release/magrathea_release.cmake
+++ b/Utilities/Release/magrathea_release.cmake
@@ -10,7 +10,7 @@ CURSES_INCLUDE_PATH:PATH=/usr/i686-gcc-332s/include/ncurses
FORM_LIBRARY:FILEPATH=/usr/i686-gcc-332s/lib/libform.a
CPACK_SYSTEM_NAME:STRING=Linux-i386
BUILD_QtDialog:BOOL:=TRUE
-QT_QMAKE_EXECUTABLE:FILEPATH=/home/kitware/qt-x11-opensource-src-4.3.3-install/bin/qmake
+QT_QMAKE_EXECUTABLE:FILEPATH=/home/kitware/qt-4.43-install/bin/qmake
)
get_filename_component(path ${CMAKE_CURRENT_LIST_FILE} PATH)
include(${path}/release_cmake.cmake)
---
Summary of changes:
Utilities/Release/magrathea_release.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
Re: [CMake] cmake for cygwin
On 2/7/2012 6:19 PM, Robert Dailey wrote: +1 to this as well My bad. I will get to it this week. They don't make it that easy... -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-developers] Ninja generator on Windows
Why does the ninja generator need to use? I am pretty sure the other CMake generators do not need to use. Most of them come from the working directory: cd foo g++ They could be worked around easly by adding a new variable to the rules. Seems like there should be a better way to run a command in a directory. Does ninja have a working directory at all? I guess you are saying there is a way to do this with a variable in the rules... Not sure what that means, but if it works... :) Others comes from the support of PRE_BUILD, POST_BUILD, and custom target / commands with more than one command. In ninja, contrary to make, when specifying a build statement (e.g. foo.o: foo.c foo.h) you can attach only one rule (e.g. one command) and not several like in make. Right, so, if there is more than one command, you can turn it into one command by creating a small cmake script that runs consecutive execute_process calls. They have been several discussion thread for adding basic shell features like in Ninja: - redirection - environment variable - working directory - chainning There is no patch proposal yet AFAIK. Sure, so until then, I think the above should be fine to get this working on windows. No one should be depending on redirection or chaining in cmake projects. -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] Ninja generator on Windows
On 2/2/2012 8:30 AM, Brad King wrote: On 2/1/2012 10:23 PM, Bill Hoffman wrote: On 2/1/2012 4:19 PM, Peter Kümmel wrote: We can't use cmd. Maybe ninja could be fixed. If not, you could come up with something that uses CMake scripts. cmake -E foo.cmake foo.cmake execute_process() Not ideal, but until ninja figures it out, cmake can become the shell for ninja. That won't handle the problem currently facing Ninja. Why not? CMake does not handle in custom commands either. It is expected that custom commands are run one by one. So, a CMake Ninja generator should be able to handle all cases, it might have to create some CMake scripts to do it, but I don't see why we would need anything more from Ninja than the ability to run a single command. -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] Ninja generator on Windows
On 2/2/2012 10:41 AM, Nicolas Desprès wrote: When you use scripts or file like link.txt you lose the power of the special $in and $out variables or variable in general that are expanded in the rule. I am not sure what those are, must be a Ninja thing... With windows, unless you have something like link.txt you are going to run into command line length issues. There is no way to use response files in ninja? -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] Ninja generator on Windows
Sorry for asking a question without looking into the details first... But Why does the ninja generator need to use ? I am pretty sure the other CMake generators do not need to use . -Bill -- Bill Hoffman Kitware, Inc. 28 Corporate Drive Clifton Park, NY 12065 bill.hoff...@kitware.com http://www.kitware.com 518 881-4905 (Direct) 518 371-3971 x105 Fax (518) 371-4573 -- 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] At FOSDEM this Sat.
Alex and I will be speaking at FOSDEM this Saturday, hope to see some of you there. Here is a pointer to the talk: http://www.kitware.com/events/home/event/204 -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] syntax error on Win7 x64
On 2/1/2012 12:35 AM, Dev Guy wrote:
OK I realized my error, I should be using $ENV{MSSDK_ROOT}
If it is a windows path, you need to change it to a posix path for CMake.
file(TO_CMAKE_PATH path result)
-Bill
On Wed, Feb 1, 2012 at 12:02 AM, Dev Guydevguy...@gmail.com wrote:
I am seeing an error from CMake on Win7 x64 that I don't see in WinXP.
The following 2 statements seems to be causing the errors below (I've
double checked that the environment var MSSDK_ROOT exists and is
defined).
include_directories(${ENV[MSSDK_ROOT]}\\Include)
link_directories(${ENV[MSSDK_ROOT]}\\Lib)
CMake Error ===
CMake Warning (dev) at CMakeLists.txt:9 (include_directories):
Syntax error in cmake code at
C:/dev/cpp/Project/safetynet/MonitorTestClient/CMakeLists.txt:9
when parsing string
${ENV[MSSDK_ROOT]}\\Include
syntax error, unexpected cal_SYMBOL, expecting } (18)
Policy CMP0010 is not set: Bad variable reference syntax is an error. Run
cmake --help-policy CMP0010 for policy details. Use the cmake_policy
command to set the policy and suppress this warning.
This warning is for project developers. Use -Wno-dev to suppress it.
CMake Warning (dev) at CMakeLists.txt:10 (link_directories):
Syntax error in cmake code at
C:/dev/cpp/Project/safetynet/MonitorTestClient/CMakeLists.txt:10
when parsing string
${ENV[MSSDK_ROOT]}\\Lib
syntax error, unexpected cal_SYMBOL, expecting } (18)
--
Kind Regards,
Rajinder Yadav
--
Bill Hoffman
Kitware, Inc.
28 Corporate Drive
Clifton Park, NY 12065
bill.hoff...@kitware.com
http://www.kitware.com
518 881-4905 (Direct)
518 371-3971 x105
Fax (518) 371-4573
--
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] At FOSDEM this Sat.
Alex and I will be speaking at FOSDEM this Saturday, hope to see some of you there. Here is a pointer to the talk: http://www.kitware.com/events/home/event/204 -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] 'Parallel' CMakeLists.txt?
On 1/31/2012 10:55 AM, Nicolas Desprès wrote:
Brad,
All these considerations are important but maybe we could just do
first the easy path which is: add a -f option which change the default
name every where, for all sub-directories, try_compile, etc...
Changing for try_compile is going to be a nightmare of sorts... There
are modules like this:
CheckFortran.cmake: file(WRITE
${CMAKE_CURRENT_BINARY_DIR}/CMakeFiles/CheckFortran/CMakeLists.txt
FindSDL_sound.cmake: FILE(WRITE
${PROJECT_BINARY_DIR}/CMakeTmp/CMakeLists.txt
Basically, the concern is this will be hard to test and likely to break
complex projects, and will end up being a half implemented feature.
-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] Compile flag issues and VS Express
On 1/28/2012 10:51 AM, David Cole wrote: Seems reasonable. Is anybody worried that changing the default values of these flags would have a negative impact on any projects out there? (i.e. is it likely that anybody relies on these flags being present and that would somehow break their build without them...? I don't think it's likely, but I'm willing to discuss before making a change in CMake) They were originally put in for VTK/ITK. They would be the projects to try. -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] FindDCMTK.cmake missing a library when it constructs DCMTK_LIBRARIES
On 1/27/2012 4:27 PM, Kent Williams wrote:
Logged it as a bug. I'm not sure why FindDCMTK.cmake is so sad.
Basically it leaves out a library from ${DCMTK_LIBRARIES} namely oflog.
http://www.cmake.org/Bug/view.php?id=12916
--
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
http://www.cmake.org/Wiki/CMake:Module_Maintainers
Maybe you should contact Mathieu Malaterre and see if he is still the
one maintaining it?
-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
[Cmake-commits] CMake branch, next, updated. v2.8.7-2298-gc110741
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 c110741cdfb878d0496f37a8c5a0260cdbb677a4 (commit)
via 4b5e270838275fe0e10e82b3eab175404f4b896b (commit)
via 5d932d8eb76dbf353f313daf6f4b2d26586ad615 (commit)
from 070ec8c4d156c6fa8608964c346abba74b961285 (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=c110741cdfb878d0496f37a8c5a0260cdbb677a4
commit c110741cdfb878d0496f37a8c5a0260cdbb677a4
Merge: 070ec8c 4b5e270
Author: Bill Hoffman bill.hoff...@kitware.com
AuthorDate: Fri Jan 27 11:18:18 2012 -0500
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Fri Jan 27 11:18:18 2012 -0500
Merge topic 'cmake_add_fortran_subdirectory' into next
4b5e270 Use GLOBAL option for imported targets, and update test to require
that.
5d932d8 Merge branch 'imported-target-visibility' into
cmake_add_fortran_subdirectory
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=4b5e270838275fe0e10e82b3eab175404f4b896b
commit 4b5e270838275fe0e10e82b3eab175404f4b896b
Author: Bill Hoffman bill.hoff...@kitware.com
AuthorDate: Fri Jan 27 11:14:00 2012 -0500
Commit: Bill Hoffman bill.hoff...@kitware.com
CommitDate: Fri Jan 27 11:14:00 2012 -0500
Use GLOBAL option for imported targets, and update test to require that.
cmake_add_fortran_directory uses imported targets when using the
mingw fortran compiler. This change makes those targets global
in scope so they act just like the real targets that exist when
a fortran compiler exists and regular add_subdirectory is used.
diff --git a/Modules/CMakeAddFortranSubdirectory.cmake
b/Modules/CMakeAddFortranSubdirectory.cmake
index c9604fa..8cfe2fb 100644
--- a/Modules/CMakeAddFortranSubdirectory.cmake
+++ b/Modules/CMakeAddFortranSubdirectory.cmake
@@ -150,7 +150,7 @@ function(cmake_add_fortran_subdirectory subdir)
)
# create imported targets for all libraries
foreach(lib ${libraries})
-add_library(${lib} SHARED IMPORTED)
+add_library(${lib} SHARED IMPORTED GLOBAL)
set_property(TARGET ${lib} APPEND PROPERTY IMPORTED_CONFIGURATIONS
NOCONFIG)
set_target_properties(${lib} PROPERTIES
IMPORTED_IMPLIB_NOCONFIG ${library_dir}/lib${lib}.lib
diff --git a/Tests/VSGNUFortran/CMakeLists.txt
b/Tests/VSGNUFortran/CMakeLists.txt
index 422350a..229c315 100644
--- a/Tests/VSGNUFortran/CMakeLists.txt
+++ b/Tests/VSGNUFortran/CMakeLists.txt
@@ -17,23 +17,8 @@ if(CMAKE_CONFIGURATION_TYPES)
endforeach()
endif()
-include(CMakeAddFortranSubdirectory)
-# add the fortran subdirectory as a fortran project
-# the subdir is fortran, the project is FortranHello
-cmake_add_fortran_subdirectory(fortran
- PROJECT FortranHello # project name in toplevel CMakeLists.txt
- ARCHIVE_DIR ${CMAKE_ARCHIVE_OUTPUT_DIRECTORY}
- RUNTIME_DIR bin # ${CMAKE_RUNTIME_OUTPUT_DIRECTORY}
- LIBRARIES hello world # target libraries created
- CMAKE_COMMAND_LINE
--DCMAKE_RUNTIME_OUTPUT_DIRECTORY=${CMAKE_RUNTIME_OUTPUT_DIRECTORY}
--DCMAKE_ARCHIVE_OUTPUT_DIRECTORY=${CMAKE_ARCHIVE_OUTPUT_DIRECTORY}
--DCMAKE_LIBRARY_OUTPUT_DIRECTORY=${CMAKE_LIBRARY_OUTPUT_DIRECTORY}
- LINK_LIBRARIES # link interface libraries
- LINK_LIBS hello world # hello needs world to link
- )
-
-include_directories(${VSGNUFortran_BINARY_DIR}/fortran)
+add_subdirectory(subdir)
+include_directories(${VSGNUFortran_BINARY_DIR}/subdir/fortran)
add_subdirectory(c_code)
# use a cmake script to run the executable so that PATH
# can be set with the MinGW/bin in it, and the fortran
diff --git a/Tests/VSGNUFortran/subdir/CMakeLists.txt
b/Tests/VSGNUFortran/subdir/CMakeLists.txt
new file mode 100644
index 000..df018b3
--- /dev/null
+++ b/Tests/VSGNUFortran/subdir/CMakeLists.txt
@@ -0,0 +1,15 @@
+include(CMakeAddFortranSubdirectory)
+# add the fortran subdirectory as a fortran project
+# the subdir is fortran, the project is FortranHello
+cmake_add_fortran_subdirectory(fortran
+ PROJECT FortranHello # project name in toplevel CMakeLists.txt
+ ARCHIVE_DIR ${CMAKE_ARCHIVE_OUTPUT_DIRECTORY}
+ RUNTIME_DIR bin # ${CMAKE_RUNTIME_OUTPUT_DIRECTORY}
+ LIBRARIES hello world # target libraries created
+ CMAKE_COMMAND_LINE
+-DCMAKE_RUNTIME_OUTPUT_DIRECTORY=${CMAKE_RUNTIME_OUTPUT_DIRECTORY}
+-DCMAKE_ARCHIVE_OUTPUT_DIRECTORY=${CMAKE_ARCHIVE_OUTPUT_DIRECTORY}
+-DCMAKE_LIBRARY_OUTPUT_DIRECTORY=${CMAKE_LIBRARY_OUTPUT_DIRECTORY}
+ LINK_LIBRARIES # link interface libraries
+ LINK_LIBS hello world # hello needs world to link
+ )
diff --git a/Tests/VSGNUFortran/fortran/CMakeLists.txt
b/Tests/VSGNUFortran/subdir/fortran/CMakeLists.txt
Re: [CMake] CMake + NSIS on windows
On 1/25/2012 9:28 AM, Andrea Crotti wrote: Since I still don't get CMake + NSIS running on Linux, I was trying to build my software on Windows... CMake and NSIS has never been ported to work on Linux, so no surprise there. I installed CMake and NSIS and all my CMake actually does is to create an installer: cmake_minimum_required(VERSION 2.6) project(try_out) install( # is this automatically the source dir?? DIRECTORY one two DESTINATION test_ddest COMPONENT dirs ) include(CPack) From my understanding I first need to run CMake which actually creates all the files which can be also read from cpack. Now the problem is that it complains the my C compiler is not set correctly. But why does it care in the first place? I mean there are no instructions there which might imply that it needs to compile something, so why should it be set? The project command by default asks for c/c++ compiler. You want: project(NONE) cmake --help-command project Set a name for the entire project. project(projectname [languageName1 languageName2 ... ] ) Sets the name of the project. Additionally this sets the variables projectName_BINARY_DIR and projectName_SOURCE_DIR to the respective values. Optionally you can specify which languages your project supports. Example languages are CXX (i.e. C++), C, Fortran, etc. By default C and CXX are enabled. E.g. if you do not have a C++ compiler, you can disable the check for it by explicitly listing the languages you want to support, e.g. C. By using the special language NONE all checks for any language can be disabled. Thanks, Andrea -- 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 -- Bill Hoffman Kitware, Inc. 28 Corporate Drive Clifton Park, NY 12065 bill.hoff...@kitware.com http://www.kitware.com 518 881-4905 (Direct) 518 371-3971 x105 Fax (518) 371-4573 -- 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] parallel make -j N
On 1/16/2012 12:10 PM, Andrea Galeazzi wrote: I generated a MakeFile Project (MinGW) and I'd like to speed up the build process using -j N option. So I launched: make -j 2 all. Unfortunately I noticed that the Makefile, generated by CMake self, contains this row: $(MAKE) -f CMakeFiles\Makefile2 all , so Makefile2 won't be executed in parallel mode. How can I pass this option to all build steps? -- gmake will do the right thing. when you run a toplevel make with -j2 it will set an env var that is passed down to the $(MAKE) and it should work. I use it all the time. -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] MSBuild and automatic project file regenation
On 1/13/2012 9:10 AM, Michael Hertling wrote: With CMake 2.8.7 and VS 2008, I can report the following findings: (1) Starting out from within an empty build directory: cmake .. followed by cmake --build . configures/builds as expected. (2) Tweaking CMakeLists.txt file only and leaving sources alone. (3) cmake --build . rebuilds the ZERO_CHECK target and, thus, updates the project file to reflect the changes from (2). However, the corresponding target is not rebuilt and, thus, does not reflect the changes from (2). (4) A further cmake --build . does *nothing* - definitely. (5) To get the concerned target rebuilt, I need to apply David's hint, i.e. cmake . cmake --build ., or clean first, i.e. cmake --build . --clean-first. Can you provide an example and how to reproduce this? I find it hard to believe that cmake --build . cmake --build . will not build everything. I get that the ZERO_TARGET does not get things to reload, but I don't see how the second build would not get things up to date. It has nothing to do with the project files depending on the targets. I assume something really changed and there really needs to be a rebuild? What type of thing are you changing in the CMakeLists.txt? -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] Progress report strange behaviour with mixed file permissions
On 1/13/2012 6:41 AM, Mateusz Loskot wrote: David Daniel, thanks! I'll confirm with my friend and follow-up if needed. Best regards, My guess would be that someone did a sudo make install. That would be a reason why you might run make a root. But, you have to be consistent and always use the same user for the same build tree. -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
[cmake-developers] Dashboard issues with ExternalProject (untar bz2 not working?)
ExternalProject is failing in a few places: http://www.cdash.org/CDash/testSummary.php?project=1name=ExternalProjectdate=2012-01-11 Seems to be an issue with bz2 untar: CMake Error: Problem with archive_read_open_file(): Child process exited with status 254 CMake Error: Problem extracting tar: /mnt/kitware/Dashboards/My Tests-HP-UXUB.11.2ia64-aCC/CMake/Tests/ExternalProject/Step1.tar.bz2 -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
[Cmake-commits] CMake branch, next, updated. v2.8.7-2002-g1022a07
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 1022a07cad8158db71a0f15cd9b446b21be96cfd (commit) via 5033f4cd1fbc59b40ac9f923ca97272676764130 (commit) from 696a596929b2f053683e16dbbc4a79a54b46947e (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=1022a07cad8158db71a0f15cd9b446b21be96cfd commit 1022a07cad8158db71a0f15cd9b446b21be96cfd Merge: 696a596 5033f4c Author: Bill Hoffman bill.hoff...@kitware.com AuthorDate: Mon Jan 9 09:54:50 2012 -0500 Commit: CMake Topic Stage kwro...@kitware.com CommitDate: Mon Jan 9 09:54:50 2012 -0500 Merge topic 'cmake_add_fortran_subdirectory' into next 5033f4c fix spelling mistake in MATCHES in if statement for lsb check http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=5033f4cd1fbc59b40ac9f923ca97272676764130 commit 5033f4cd1fbc59b40ac9f923ca97272676764130 Author: Bill Hoffman bill.hoff...@kitware.com AuthorDate: Mon Jan 9 09:54:35 2012 -0500 Commit: Bill Hoffman bill.hoff...@kitware.com CommitDate: Mon Jan 9 09:54:35 2012 -0500 fix spelling mistake in MATCHES in if statement for lsb check diff --git a/Tests/CMakeLists.txt b/Tests/CMakeLists.txt index ed9a73c..f789bdb 100644 --- a/Tests/CMakeLists.txt +++ b/Tests/CMakeLists.txt @@ -179,7 +179,8 @@ IF(BUILD_TESTING) SET(CMAKE_SKIP_VSGNUFortran TRUE) ENDIF() ENDIF() -IF((CMAKE_C_COMPILER MATCHS lsb) AND (CMAKE_Fortran_COMPILER MATCHES ifort)) +IF((CMAKE_C_COMPILER MATCHES lsb) +AND (CMAKE_Fortran_COMPILER MATCHES ifort)) MESSAGE(STATUS Skip VSGNUFortran for ifort and lsb compilers) SET(CMAKE_SKIP_VSGNUFortran TRUE) ENDIF() --- Summary of changes: Tests/CMakeLists.txt |3 ++- 1 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.7-1981-gd1a6b04
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 d1a6b049056ac50af38a75fe68bd7df0aec230b0 (commit)
via b46c42c87117dbe6022f301b0f2e1fd485b7064b (commit)
from c07479619c47bcc30aa551bc46fd90311048126e (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=d1a6b049056ac50af38a75fe68bd7df0aec230b0
commit d1a6b049056ac50af38a75fe68bd7df0aec230b0
Merge: c074796 b46c42c
Author: Bill Hoffman bill.hoff...@kitware.com
AuthorDate: Fri Jan 6 14:04:19 2012 -0500
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Fri Jan 6 14:04:19 2012 -0500
Merge topic 'cmake_add_fortran_subdirectory' into next
b46c42c Use a raw try_compile to test for -lsunquad working on SunOS.
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=b46c42c87117dbe6022f301b0f2e1fd485b7064b
commit b46c42c87117dbe6022f301b0f2e1fd485b7064b
Author: Bill Hoffman bill.hoff...@kitware.com
AuthorDate: Fri Jan 6 14:03:30 2012 -0500
Commit: Bill Hoffman bill.hoff...@kitware.com
CommitDate: Fri Jan 6 14:03:30 2012 -0500
Use a raw try_compile to test for -lsunquad working on SunOS.
diff --git a/Tests/VSGNUFortran/fortran/CMakeLists.txt
b/Tests/VSGNUFortran/fortran/CMakeLists.txt
index 46b2b38..3ee1855 100644
--- a/Tests/VSGNUFortran/fortran/CMakeLists.txt
+++ b/Tests/VSGNUFortran/fortran/CMakeLists.txt
@@ -1,12 +1,36 @@
cmake_minimum_required(VERSION 2.8)
project(FortranHello Fortran C)
+# add a function to test for -lsunquad on sunpro sun systems.
+function(test_sunquad result)
+ set( TEST_DIR ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/CMakeTmp/sunq)
+ file(WRITE ${TEST_DIR}/testsunq.f
+ PROGRAM TEST
+ END
+ )
+ file(WRITE ${TEST_DIR}/CMakeLists.txt
+project(sunq Fortran)
+add_library(sunq SHARED testsunq.f)
+target_link_libraries(sunq sunquad)
+)
+ message(STATUS looking for -lsunquad)
+ try_compile(RESULT ${TEST_DIR} ${TEST_DIR} sunq OUTPUT_VARIABLE OUT)
+ if(${RESULT})
+message(STATUS -lsunquad found)
+ else()
+message(STATUS -lsunquad not found)
+ endif()
+ message(STATUS
+looking for sunquad:\nRESULT=[${RESULT}]\nOUTPUT=[\n${OUT}\n])
+ set(${result} ${RESULT} PARENT_SCOPE)
+endfunction()
+
+# check for the fortran c interface mangling
include(FortranCInterface)
FortranCInterface_HEADER(HelloWorldFCMangle.h
MACRO_NAMESPACE FC_
SYMBOL_NAMESPACE FC_
SYMBOLS hello world)
-
add_library(hello SHARED hello.f)
add_library(world SHARED world.f)
target_link_libraries(hello world)
@@ -14,8 +38,7 @@ if(CMAKE_Fortran_COMPILER_ID MATCHES SunPro)
target_link_libraries(hello fsu)
if(CMAKE_Fortran_PLATFORM_ID MATCHES SunOS)
target_link_libraries(hello sunmath m)
-include(CheckLibraryExists)
-check_library_exists(sunquad Qge CMAKE_HAS_SUNQUAD)
+test_sunquad(CMAKE_HAS_SUNQUAD)
if(CMAKE_HAS_SUNQUAD)
target_link_libraries(hello sunquad)
endif()
---
Summary of changes:
Tests/VSGNUFortran/fortran/CMakeLists.txt | 29 ++---
1 files changed, 26 insertions(+), 3 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.7-1987-gd5a07b3
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 d5a07b316925816e345f9ce2452d2ea47c33d1c0 (commit)
via 42f893d9b4403f12fe8a08b1827673b72715ea42 (commit)
from cd3c3977ccfc2b4faffa4089081e9ea357f96d60 (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=d5a07b316925816e345f9ce2452d2ea47c33d1c0
commit d5a07b316925816e345f9ce2452d2ea47c33d1c0
Merge: cd3c397 42f893d
Author: Bill Hoffman bill.hoff...@kitware.com
AuthorDate: Fri Jan 6 16:49:10 2012 -0500
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Fri Jan 6 16:49:10 2012 -0500
Merge topic 'cmake_add_fortran_subdirectory' into next
42f893d Disable VSGNUFortran test with lsb and ifort compiler
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=42f893d9b4403f12fe8a08b1827673b72715ea42
commit 42f893d9b4403f12fe8a08b1827673b72715ea42
Author: Bill Hoffman bill.hoff...@kitware.com
AuthorDate: Fri Jan 6 16:48:36 2012 -0500
Commit: Bill Hoffman bill.hoff...@kitware.com
CommitDate: Fri Jan 6 16:48:36 2012 -0500
Disable VSGNUFortran test with lsb and ifort compiler
diff --git a/Tests/CMakeLists.txt b/Tests/CMakeLists.txt
index a1d2fcf..ed9a73c 100644
--- a/Tests/CMakeLists.txt
+++ b/Tests/CMakeLists.txt
@@ -179,6 +179,10 @@ IF(BUILD_TESTING)
SET(CMAKE_SKIP_VSGNUFortran TRUE)
ENDIF()
ENDIF()
+IF((CMAKE_C_COMPILER MATCHS lsb) AND (CMAKE_Fortran_COMPILER MATCHES
ifort))
+ MESSAGE(STATUS Skip VSGNUFortran for ifort and lsb compilers)
+ SET(CMAKE_SKIP_VSGNUFortran TRUE)
+ENDIF()
IF(NOT CMAKE_SKIP_VSGNUFortran)
ADD_TEST_MACRO(VSGNUFortran ${CMAKE_COMMAND} -P runtest.cmake)
ENDIF()
---
Summary of changes:
Tests/CMakeLists.txt |4
1 files changed, 4 insertions(+), 0 deletions(-)
hooks/post-receive
--
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-commits
Re: [CMake] Add Custom COmmand and CMAKE_CFG_INTDIR
On 1/4/2012 4:03 PM, Michael Jackson wrote:
I robbed this from the HDF5 project which does something very similar to what I
am doing:
SET (CMD ${CMAKE_RUNTIME_OUTPUT_DIRECTORY}${CFG_INIT}/H5detect${EXE_EXT})
That seems to at least point to the proper location. Now to get Visual Studio
to actually execute the executable.
That is pretty old stuff...
There are better ways to do that in CMake now:
cmake --help-command add_custom_command
Arguments to COMMAND may use generator expressions with the syntax
$ Generator expressions are evaluted during build system
generation to produce information specific to each build
configuration. Valid expressions are:
$CONFIGURATION = configuration name
$TARGET_FILE:tgt= main file (.exe, .so.1.2, .a)
$TARGET_LINKER_FILE:tgt = file used to link (.a, .lib, .so)
$TARGET_SONAME_FILE:tgt = file with soname (.so.3)
This should work:
COMMAND $TARGET_FILE:FilterWidgetCodeGen
-Bill
--
Mike Jacksonwww.bluequartz.net
On Jan 4, 2012, at 3:54 PM, clin...@elemtech.com wrote:
Have you tried excluding the .exe thing? I thought cmake did the right thing
for targets used in custom commands.
Clint
- Reply message -
From: Michael Jacksonmike.jack...@bluequartz.net
Date: Wed, Jan 4, 2012 1:28 pm
Subject: [CMake] Add Custom COmmand and CMAKE_CFG_INTDIR
To: cmake@cmake.org Listcmake@cmake.org
I am having trouble getting add_custom_Command and CMAKE_CFG_INTDIR to work
correctly together. This is what I have so far.
# -- Setup output Directories -
SET (CMAKE_LIBRARY_OUTPUT_DIRECTORY
${PROJECT_BINARY_DIR}/Bin
CACHE PATH
Single Directory for all Libraries
)
# Create our custom executable that will generate most of our QFilterWidget
# classes from information stored in the Filters themselves.
configure_file( ${FilterWidgets_SOURCE_DIR}/CodeGen.cpp.in
${FilterWidgets_BINARY_DIR}/FilterWidgetCodeGen.cpp)
add_executable(FilterWidgetCodeGen
${FilterWidgets_BINARY_DIR}/FilterWidgetCodeGen.cpp)
target_link_libraries(FilterWidgetCodeGen MXA EbsdLib DREAM3DLib)
set(EXE_EXTENSION )
if (WIN32)
set (EXE_EXTENSION .exe)
endif()
# Now run the code to generate the header files which will over write the place
# holder files that were generated from above
add_custom_command(TARGET FilterWidgetCodeGen POST_BUILD
COMMAND FilterWidgetCodeGen${EXE_EXTENSION}
WORKING_DIRECTORY ${CMAKE_LIBRARY_OUTPUT_DIRECTORY})
I know this is going to fail on visual studio, which it did. The issue is, what
combination of CMAKE_CFG_INTDIR and anything else do I use to get this to work?
Thanks
___
Mike JacksonPrincipal Software Engineer
BlueQuartz SoftwareDayton, Ohio
mike.jack...@bluequartz.net www.bluequartz.net
--
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
--
Bill Hoffman
Kitware, Inc.
28 Corporate Drive
Clifton Park, NY 12065
bill.hoff...@kitware.com
http://www.kitware.com
518 881-4905 (Direct)
518 371-3971 x105
Fax (518) 371-4573
--
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 Custom COmmand and CMAKE_CFG_INTDIR
On 1/4/2012 4:27 PM, Michael Jackson wrote: Thanks! The definitely fixed the issue for ALL the platforms. I guess I just have not been keeping up with all the additions to CMake. At what version was this syntax introduced? Looks like about a year ago: http://cmake.org/gitweb?p=cmake.git;a=commit;h=f0cdb6001b3e915fc0d9c1120165d49725440bbd committerBrad King brad.k...@kitware.com Wed, 15 Dec 2010 19:53:48 + (14:53 -0500) -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] Interrupt problems in cmake-gui
On 12/30/2011 8:10 PM, Robert Dailey wrote: I'd like to introduce boost into CMake for this. No way... :) -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
[Cmake-commits] CMake branch, next, updated. v2.8.6-2315-g1f5d914
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 1f5d9142fe572d63aaf96391e08e671642c6994c (commit) via 1c5838a0b8db1bc85056131fd6e79bb2d081ee73 (commit) from a719919e4b447b0fbc93de96329ae5be75ecf7a5 (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=1f5d9142fe572d63aaf96391e08e671642c6994c commit 1f5d9142fe572d63aaf96391e08e671642c6994c Merge: a719919 1c5838a Author: Bill Hoffman bill.hoff...@kitware.com AuthorDate: Tue Dec 27 11:53:10 2011 -0500 Commit: CMake Topic Stage kwro...@kitware.com CommitDate: Tue Dec 27 11:53:10 2011 -0500 Merge topic 'cmake_add_fortran_subdirectory' into next 1c5838a Try to fix for one last sun machine that is failing. http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=1c5838a0b8db1bc85056131fd6e79bb2d081ee73 commit 1c5838a0b8db1bc85056131fd6e79bb2d081ee73 Author: Bill Hoffman bill.hoff...@kitware.com AuthorDate: Tue Dec 27 11:21:14 2011 -0500 Commit: Bill Hoffman bill.hoff...@kitware.com CommitDate: Tue Dec 27 11:21:14 2011 -0500 Try to fix for one last sun machine that is failing. diff --git a/Tests/VSGNUFortran/fortran/CMakeLists.txt b/Tests/VSGNUFortran/fortran/CMakeLists.txt index 1d4d7be..2141d1a 100644 --- a/Tests/VSGNUFortran/fortran/CMakeLists.txt +++ b/Tests/VSGNUFortran/fortran/CMakeLists.txt @@ -13,6 +13,6 @@ target_link_libraries(hello world) if(CMAKE_Fortran_COMPILER_ID MATCHES SunPro) target_link_libraries(hello fsu) if(CMAKE_Fortran_PLATFORM_ID MATCHES SunOS) -target_link_libraries(hello sunmath m) +target_link_libraries(hello sunmath sunquad m) endif() endif() --- Summary of changes: Tests/VSGNUFortran/fortran/CMakeLists.txt |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
Re: [CMake] Compile project as C++ if MSVC
On 12/23/2011 5:43 PM, Pau Garcia i Quiles wrote: Hi Bill, Thank you. I tried that but it's failing: since no project in the whole project tree is defined as C++ (i. e. everything is project(blah C)), the generation step fails with: CMake Error: Error required internal CMake variable not set, cmake may be not be built correctly. Missing variable is: CMAKE_CXX_FLAGS_DEBUG I've opened issue #12639 for this and attached a minimal case, and a workaround: http://public.kitware.com/Bug/view.php?id=12639 I am thinking if you want to compile with C++, you need to enable the c++ language. You can call enable_language(CXX) inside the if. -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
