[cmake-developers] [PATCH] WINCE: Document the WINCE variable
--- Help/manual/cmake-variables.7.rst |1 + Help/variable/WINCE.rst |5 + 2 files changed, 6 insertions(+) create mode 100644 Help/variable/WINCE.rst diff --git a/Help/manual/cmake-variables.7.rst b/Help/manual/cmake-variables.7.rst index 149e4ac..b00c16e 100644 --- a/Help/manual/cmake-variables.7.rst +++ b/Help/manual/cmake-variables.7.rst @@ -192,6 +192,7 @@ Variables that Describe the System /variable/MSVC_VERSION /variable/UNIX /variable/WIN32 + /variable/WINCE /variable/WINDOWS_PHONE /variable/WINDOWS_STORE /variable/XCODE_VERSION diff --git a/Help/variable/WINCE.rst b/Help/variable/WINCE.rst new file mode 100644 index 000..54ff7de --- /dev/null +++ b/Help/variable/WINCE.rst @@ -0,0 +1,5 @@ +WINCE +- + +True when the :variable:`CMAKE_SYSTEM_NAME` variable is set +to ``WindowsCE``. -- 1.7.10.4 -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
[cmake-developers] [CMake 0015150]: Eclipse generator produces very bad symbol browsing quality for plain C, due to __cplusplus being set unconditionally
The following issue has been SUBMITTED. == http://public.kitware.com/Bug/view.php?id=15150 == Reported By:Martin Oberhuber Assigned To: == Project:CMake Issue ID: 15150 Category: CMake Reproducibility:always Severity: major Priority: normal Status: new == Date Submitted: 2014-09-11 05:29 EDT Last Modified: 2014-09-11 05:29 EDT == Summary:Eclipse generator produces very bad symbol browsing quality for plain C, due to __cplusplus being set unconditionally Description: When I import my plain C project generated with the Eclipse CDT4 - Unix Makefiles generator into Eclipse, I see very bad symbol quality: Indexed 'myproject@linux64' (365 sources, 800 headers) in 24.2 sec: 81,605 declarations; 665,941 references; 54 unresolved inclusions; 3,708 syntax errors; 107,398 unresolved names (13%) Note the 13% unresolved names, which means that the calltree (referenced-by) will fail 13% of the time ! This is way too unreliable. Investigation showed that the main problem is cmake generating __cplusplus=1 unconditionally into the Project Properties C/C++ Include Paths. When deleting the incorrect __cplusplus setting I get almost perfect symbol quality: Indexed 'myproject@linux64' (365 sources, 800 headers) in 23.2 sec: 98,095 declarations; 785,956 references; 54 unresolved inclusions; 2,230 syntax errors; 4,732 unresolved names (0.53%) -- Note only 0.53% unresolved names now (in this case due to some Windows headers). Also note that a __cplusplus macro will be added automatically by Eclipse CDT when looking at any *.cpp / *.cxx / *.cc files. So that macro really should not be set hard-coded by the project generator ! Steps to Reproduce: cmake -G Eclipse CDT4 - Unix Makefiles -DCMAKE_BUILD_TYPE=Debug -DCMAKE_ECLIPSE_VERSION=4.4 ../myproject make # Now import the generated project into Eclipse for C/C++ 4.4 Additional Information: Workaround: After importing the generated project, right-click C/C++ Include Paths and manually delete the __cplusplus macro setting. == Issue History Date ModifiedUsername FieldChange == 2014-09-11 05:29 Martin OberhuberNew Issue == -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] [PATCH] WINCE: Document the WINCE variable
On 09/11/2014 05:07 AM, Pascal Bach wrote: Help/manual/cmake-variables.7.rst |1 + Help/variable/WINCE.rst |5 + Applied, thanks: Help: Document the WINCE variable http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=4b4555de -Brad -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] Alternate if() without implicit variable expansion
On 09/10/2014 03:42 PM, Nils Gladitz wrote: extract everything into its own class cmConditionEvaluator and have it keep everything that was being passed around as members instead. Good work. I think the net change is now in good shape. To make it easier to review now and bisect in the future, please rewrite the topic to start with refactoring cmIfCommand to split out the cmConditionEvaluator, and then add the rest of the changes. Thanks, -Brad -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] Alternate if() without implicit variable expansion
On 11.09.2014 15:04, Brad King wrote: Good work. I think the net change is now in good shape. To make it easier to review now and bisect in the future, please rewrite the topic to start with refactoring cmIfCommand to split out the cmConditionEvaluator, and then add the rest of the changes. Thanks. Is there a trick to recreate the history in that order or would I have to start from scratch? Nils -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] Alternate if() without implicit variable expansion
On 09/11/2014 09:20 AM, Nils Gladitz wrote:
Is there a trick to recreate the history in that order or
would I have to start from scratch?
First rewrite the branch to squash your updates back into
the first commit, leaving all my CMP0054 warning commits
later in the topic. Then start a new branch from the
squashed commit containing only your part of the changes.
Note the sha1 of this commit, say a01b2c3. Then edit it
to *remove* the changes besides the refactoring and amend
the commit. The result should be just one commit with the
refactoring parts.
Then you can use the git commit-tree plumbing to create
a commit with the tree object of your original change but
set its parent as the edited commit. This will manufacture
a commit that makes the changes on top of the refactoring:
commit=$(git commit-tree a01b2c3^{tree} -p HEAD)
git merge $commit
git commit --amend -C a01b2c3
Finally, rebase the rest of the topic back onto that.
The tip of the resulting topic should look identical to
what is on the stage now.
Thanks,
-Brad
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] Alternate if() without implicit variable expansion
On 11.09.2014 15:28, Brad King wrote: First rewrite the branch to squash your updates back into the first commit, leaving all my CMP0054 warning commits later in the topic. Then start a new branch from the squashed commit containing only your part of the changes. Note the sha1 of this commit, say a01b2c3. Then edit it to *remove* the changes besides the refactoring Thanks for the walk through. I am a bit stuck on removing the CMP0054 changes from cmConditionEvaluator.cxx part given that file is new and didn't exist without the changes. I'll redo the refactoring part manually from scratch if I can't figure out something better. Might take me a bit; I haven't had much experience with those git aspects yet. Nils -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] Alternate if() without implicit variable expansion
On 09/11/2014 11:35 AM, Nils Gladitz wrote: Thanks for the walk through. I am a bit stuck on removing the CMP0054 changes from cmConditionEvaluator.cxx part given that file is new and didn't exist without the changes. The file should exist, just remove the CMP0054 parts from it and amend the commit. I'll redo the refactoring part manually from scratch if I can't figure out something better. Might take me a bit; I haven't had much experience with those git aspects yet. If it takes too much time, don't bother doing this part unless you are really interested in using it as a learning opportunity. Let me know either way, please. Thanks, -Brad -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] [PATCH] WINCE, VS: Allow selecting an SDK for Windows CE on Visual Studio
On 09/05/2014 03:53 PM, Brad King wrote:
I think CMAKE_GENERATOR_PLATFORM may be a suitable name. Ideally
this setting should be added as a general-purpose replacement for
putting ARM or Win64 in the generator name. The changes for
that are more sweeping than I'd like to ask of you just for WinCE
support, so I drafted them myself.
This is now in 'master'.
On 09/04/2014 06:42 AM, Bach, Pascal wrote:
At the beginning of this block you should check/reject when
the generator name specified a platform name. Something like:
if(this-PlatformName != Win32)
{
cmOStringStream e;
e CMAKE_SYSTEM_NAME is 'WindowsCE' but CMAKE_GENERATOR
specifies a platform too: ' this-GetName() ';
mf-IssueMessage(cmake::FATAL_ERROR, e.str());
return false;
}
This won't' work as the code gets called multiple times
Along with the above changes I also made SetSystemName not
get called more than once. The PlatformName member is
now DefaultPlatformName. Initially it corresponds to the
default based on the generator name, so you should be able
to check it as shown above.
SetSystemName can modify DefaultPlatformName for specific
systems to have a different default in case
CMAKE_GENERATOR_PLATFORM is not set. The value of that
setting is then processed by SetGeneratorPlatform.
-Brad
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] Alternate if() without implicit variable expansion
On 11.09.2014 17:39, Brad King wrote: On 09/11/2014 11:35 AM, Nils Gladitz wrote: Thanks for the walk through. I am a bit stuck on removing the CMP0054 changes from cmConditionEvaluator.cxx part given that file is new and didn't exist without the changes. The file should exist, just remove the CMP0054 parts from it and amend the commit. I might be missing something obvious. cmConditionEvaluator.cxx doesn't exist without the CMP0054 changes because I created it after I did most of the CMP0054 changes. Since most of the changes are replacements rather than plain additions *removing* those changes would mean having to restore those code parts which however used to be in cmIf.cxx rather than cmConditionEvaluator.cxx. Nils -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
[cmake-developers] [ANNOUNCE] CMake 3.0.2 Released
We are pleased to announce that CMake 3.0.2 is now available for download. Please use the latest release from our download page: http://www.cmake.org/download/ Thanks for your support! - Changes in 3.0.2 since 3.0.1: Alan W. Irwin (1): ExternalProject: Avoid infinite loop on file download hash mismatch Brad King (6): CMP0047: Fix CMAKE_COMPILER_IS_GNU(CC|CXX) in OLD behavior CMP0022: Fix version documented to support LINK_PUBLIC/LINK_PRIVATE cmListFileLexer: Fix lexing of single '[' character (#15092) Xcode: Generate per-target file references (#15111) Fix finding binutils when cross-compiling with Clang CMake 3.0.2 Christian Svensson (2): KWIML: Teach ABI.h about OpenRISC 1000 KWSys CPU: Add support for OpenRISC 1000 Stephen Kelly (2): QtAutogen: Use the basename for resource files. QtAutogen: Fix use of multiple ui files in a single target. Tim Blechmann (1): BundleUtilities: Allow Info.plist files which use CR line endings -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] Alternate if() without implicit variable expansion
On 09/11/2014 11:52 AM, Nils Gladitz wrote:
cmConditionEvaluator.cxx doesn't exist without the CMP0054 changes
because I created it after I did most of the CMP0054 changes.
Since most of the changes are replacements rather than plain additions
*removing* those changes would mean having to restore those code parts
which however used to be in cmIf.cxx rather than cmConditionEvaluator.cxx.
I think you missed the part about squashing your changes together
into the first commit of the topic. I just rewrote the topic
to do that. Now you can start working from commit 5922fc2c:
git checkout -b tmp 5922fc2c
git rm Help/policy/CMP0054.rst Help/release/dev/if-sanity.rst
git checkout HEAD~1 -- Help
git rm -rf Tests/RunCMake/CMP0054
git checkout HEAD~1 -- Tests/RunCMake/CMakeLists.txt
git commit --amend
Then keep editing the files and amending the commit to leave
behind only the refactoring pieces. Amend the commit message
accordingly too. Then do:
commit=$(git commit-tree 5922fc2c^{tree} -p HEAD)
git merge $commit
git commit --amend -C 5922fc2c
to restore the rest of the commit's changes. Then rebase
the rest of the topic to get the warning cleanups.
-Brad
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] Alternate if() without implicit variable expansion
On 11.09.2014 18:53, Brad King wrote: On 09/11/2014 11:52 AM, Nils Gladitz wrote: cmConditionEvaluator.cxx doesn't exist without the CMP0054 changes because I created it after I did most of the CMP0054 changes. Since most of the changes are replacements rather than plain additions *removing* those changes would mean having to restore those code parts which however used to be in cmIf.cxx rather than cmConditionEvaluator.cxx. I think you missed the part about squashing your changes together into the first commit of the topic. I just rewrote the topic to do that. Now you can start working from commit 5922fc2c: No I did that as well. git checkout -b tmp 5922fc2c git rm Help/policy/CMP0054.rst Help/release/dev/if-sanity.rst git checkout HEAD~1 -- Help git rm -rf Tests/RunCMake/CMP0054 git checkout HEAD~1 -- Tests/RunCMake/CMakeLists.txt git commit --amend I think I did all that too. Then keep editing the files and amending the commit to leave behind only the refactoring pieces. That is the part I was stuck at. Nils -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] Alternate if() without implicit variable expansion
On 09/11/2014 12:57 PM, Nils Gladitz wrote: Then keep editing the files and amending the commit to leave behind only the refactoring pieces. That is the part I was stuck at. At this point cmConditionEvaluator.cxx exists in the source tree. What is the problem? -Brad -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] Alternate if() without implicit variable expansion
On 11.09.2014 18:59, Brad King wrote: At this point cmConditionEvaluator.cxx exists in the source tree. What is the problem? I can not create a CMP0054 free version of cmConditionEvaluator.cxx by simply removing content from the file (or the patch). I would have to add back lines to cmConditionEvaluator.cxx which where removed while they were still in cmIfCommand.cxx. The problem is that I am not sure how to do that properly. Nils -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] Alternate if() without implicit variable expansion
On 09/11/2014 01:07 PM, Nils Gladitz wrote: I would have to add back lines to cmConditionEvaluator.cxx which where removed while they were still in cmIfCommand.cxx. Look at the diff in commit 5922fc2c and you will see all those lines as removed from cmIfCommand. You can put them all in cmConditionEvaluator. Some of the work is manual. Effectively you are re-doing the refactoring from scratch without the CMP0054 pieces. The use of Git up to this point is just to help get close. The reason I'm asking for this is that the refactoring done to create cmConditionEvaluator is more intrusive than the original CMP0054 change. It will be much easier to convince myself that the whole thing is correct if I can see the refactoring done first and independently. Thanks, -Brad -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] Alternate if() without implicit variable expansion
I think I've got it rewritten properly but I didn't know what half the git commands I ran did most of the time so I am not entirely secure with the result. Would have probably not figured this out without your help. Thanks again! Nils -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [CMake] Incorrect object file name on cmake compilation
Hi Ravi. In what sense is the name incorrect? There is no correct/incorrect way to name object files in relation to the source file name; it can be arbitrary, as long as it's correctly passed on to the linker. I believe CMake chooses to append .obj to the whole file name if there is more than one file with the same base name. But why should this be a problem? Petr On Thu, Sep 11, 2014 at 7:59 AM, Ravi Raman ravi.ra...@xoriant.com wrote: Hi, We are working on a cmake project. The issue is that the cmake build is successful but after the execution of cmake build step, the name of the object file is incorrect. On compilation of the source file main.cpp, the name of the object file is coming incorrectly as main.cpp.obj instead of main.obj To simulate the problem, please find attached herewith a zip file that contains CMakeLists.txt main.cpp main.rc The source list contains “main.cpp” and the resource file “main.rc” Please note the following: 1. This problem occurs only when the resource file main.rc is present in the list. 2. This problem does not occur when the resource file main.rc is excluded from the list OR if the resource file has a name other than main.rc Thanks Regards *Ravi Raman * *Xoriant Solutions Pvt. Ltd* 4th Floor, Winchester, Hiranandani Business Park, Powai, Mumbai 400076, INDIA. Tel: +91 22 30511000,9930100026 Extn: 2144 Voip No. 4088344495/96/97/98 Voip Extn:1178| Fax: +91 22 3051 ravi.ra...@xoriant.com ram.si...@xoriant.com| http://www.xoriant.com -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
Re: [CMake] Incorrect object file name on cmake compilation
Hi, Thanks Petr for your reply. By incorrect I meant instead of the conventional main.obj, we get main.cpp.obj. I understood what you are saying. We have found a solution for this in our cmake code. We have explicitly set the /Fo compiler flag for main.cpp. With that it creates main.obj for main.cpp and also main.res for main.rc Thanks Regards Ravi Raman Xoriant Solutions Pvt. Ltd 4th Floor, Winchester, Hiranandani Business Park, Powai, Mumbai 400076, INDIA. Tel: +91 22 30511000,9930100026 Extn: 2144 Voip No. 4088344495/96/97/98 Voip Extn:1178| Fax: +91 22 3051 ravi.ra...@xoriant.commailto:ram.si...@xoriant.com| http://www.xoriant.comhttp://www.xoriant.com/ From: Petr Kmoch [mailto:petr.km...@gmail.com] Sent: Thursday, September 11, 2014 12:11 PM To: Ravi Raman Cc: cmake@cmake.org Subject: Re: [CMake] Incorrect object file name on cmake compilation Hi Ravi. In what sense is the name incorrect? There is no correct/incorrect way to name object files in relation to the source file name; it can be arbitrary, as long as it's correctly passed on to the linker. I believe CMake chooses to append .obj to the whole file name if there is more than one file with the same base name. But why should this be a problem? Petr On Thu, Sep 11, 2014 at 7:59 AM, Ravi Raman ravi.ra...@xoriant.commailto:ravi.ra...@xoriant.com wrote: Hi, We are working on a cmake project. The issue is that the cmake build is successful but after the execution of cmake build step, the name of the object file is incorrect. On compilation of the source file main.cpp, the name of the object file is coming incorrectly as main.cpp.obj instead of main.obj To simulate the problem, please find attached herewith a zip file that contains CMakeLists.txt main.cpp main.rc The source list contains “main.cpp” and the resource file “main.rc” Please note the following: 1. This problem occurs only when the resource file main.rc is present in the list. 2. This problem does not occur when the resource file main.rc is excluded from the list OR if the resource file has a name other than main.rc Thanks Regards Ravi Raman Xoriant Solutions Pvt. Ltd 4th Floor, Winchester, Hiranandani Business Park, Powai, Mumbai 400076, INDIA. Tel: +91 22 30511000tel:%2B91%2022%2030511000,9930100026 Extn: 2144 Voip No. 4088344495tel:4088344495/96/97/98 Voip Extn:1178| Fax: +91 22 3051tel:%2B91%2022%203051 ravi.ra...@xoriant.commailto:ram.si...@xoriant.com| http://www.xoriant.comhttp://www.xoriant.com/ -- Powered by www.kitware.comhttp://www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
Re: [CMake] Incorrect object file name on cmake compilation
Hi, Date: Thu, 11 Sep 2014 07:49:23 + From: Ravi Raman ravi.ra...@xoriant.com Hi, Thanks Petr for your reply. By incorrect I meant instead of the conventional main.obj, we get main.cpp.obj. I understood what you are saying. We have found a solution for this in our cmake code. Good, so you've found a solution - to which, umm, I dare ask... problem exactly? :) We have explicitly set the /Fo compiler flag for main.cpp. With that it creates main.obj for main.cpp and also main.res for main.rc Why does this need some manual effort (and of manually adding a very specific compiler flag syntax, in fact!) when it ideally/normally/usually shouldn't, one would want to ask. Perhaps this issue is indicative of an asymmetric/incomplete mechanism or configuration in CMake or this specific CMake environment, which one might want to discover and fix, in order to have the need for any manual tweaking (in all sufficiently standard cases) avoided in all future deployments... Thanks, Andreas Mohr -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
Re: [CMake] Incorrect object file name on cmake compilation
I was wondering about this as well. Ravi, what is your motivation for having object file names of a particular format? I don't think I've ever had to care what object files in our builds are called. Petr On Thu, Sep 11, 2014 at 10:01 AM, Andreas Mohr a...@lisas.de wrote: Hi, Date: Thu, 11 Sep 2014 07:49:23 + From: Ravi Raman ravi.ra...@xoriant.com Hi, Thanks Petr for your reply. By incorrect I meant instead of the conventional main.obj, we get main.cpp.obj. I understood what you are saying. We have found a solution for this in our cmake code. Good, so you've found a solution - to which, umm, I dare ask... problem exactly? :) We have explicitly set the /Fo compiler flag for main.cpp. With that it creates main.obj for main.cpp and also main.res for main.rc Why does this need some manual effort (and of manually adding a very specific compiler flag syntax, in fact!) when it ideally/normally/usually shouldn't, one would want to ask. Perhaps this issue is indicative of an asymmetric/incomplete mechanism or configuration in CMake or this specific CMake environment, which one might want to discover and fix, in order to have the need for any manual tweaking (in all sufficiently standard cases) avoided in all future deployments... Thanks, Andreas Mohr -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
Re: [CMake] Incorrect object file name on cmake compilation
Actually, in our project, the names of the object files matter because these object files go as an input to a object file comparison tool that compares object file names. So, there are 2 sets of object files, one coming from cmake build and one from Visual Studio build. The set coming from cmake build was having this object file naming with extension .cpp.obj. That was the reason for looking into this issue. Thanks Regards Ravi Raman Xoriant Solutions Pvt. Ltd 4th Floor, Winchester, Hiranandani Business Park, Powai, Mumbai 400076, INDIA. Tel: +91 22 30511000,9930100026 Extn: 2144 Voip No. 4088344495/96/97/98 Voip Extn:1178| Fax: +91 22 3051 ravi.ra...@xoriant.commailto:ram.si...@xoriant.com| http://www.xoriant.comhttp://www.xoriant.com/ From: Petr Kmoch [mailto:petr.km...@gmail.com] Sent: Thursday, September 11, 2014 1:49 PM To: Andreas Mohr Cc: cmake@cmake.org; Ravi Raman Subject: Re: [CMake] Incorrect object file name on cmake compilation I was wondering about this as well. Ravi, what is your motivation for having object file names of a particular format? I don't think I've ever had to care what object files in our builds are called. Petr On Thu, Sep 11, 2014 at 10:01 AM, Andreas Mohr a...@lisas.demailto:a...@lisas.de wrote: Hi, Date: Thu, 11 Sep 2014 07:49:23 + From: Ravi Raman ravi.ra...@xoriant.com Hi, Thanks Petr for your reply. By incorrect I meant instead of the conventional main.obj, we get main.cpp.obj. I understood what you are saying. We have found a solution for this in our cmake code. Good, so you've found a solution - to which, umm, I dare ask... problem exactly? :) We have explicitly set the /Fo compiler flag for main.cpp. With that it creates main.obj for main.cpp and also main.res for main.rc Why does this need some manual effort (and of manually adding a very specific compiler flag syntax, in fact!) when it ideally/normally/usually shouldn't, one would want to ask. Perhaps this issue is indicative of an asymmetric/incomplete mechanism or configuration in CMake or this specific CMake environment, which one might want to discover and fix, in order to have the need for any manual tweaking (in all sufficiently standard cases) avoided in all future deployments... Thanks, Andreas Mohr -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
Re: [CMake] Incorrect object file name on cmake compilation
On Thu, Sep 11, 2014 at 08:25:27AM +, Ravi Raman wrote: Actually, in our project, the names of the object files matter because these object files go as an input to a object file comparison tool that compares object file names. So, there are 2 sets of object files, one coming from cmake build and one from Visual Studio build. The set coming from cmake build was having this object file naming with extension .cpp.obj. That was the reason for looking into this issue. Ah, so that means we're talking about this issue having come up due to expectations about object naming being somewhat usual (as opposed to CMake-configured naming), of an *external tool*, rather than due to uneasiness/issues detected within the CMake workflow itself. So, that means: - CMake handling likely *is* consistent (at least in regard to this aspect) - the external tool does not like it :) - a manual specific compiler flag setting was configured to fall back to previously usual object naming So, my thoughts on this are that it would be best to have the external tool offer an option to support custom object file naming patterns, since naming of internally generated object files may easily differ in various build systems. Manually adding a very specific /Fo option *can* be done, but: - this manual tweak might then cause incompatibilities with internal CMake assumptions (quite possibly there are CMake configuration variables/mechanisms to generically switch this naming pattern though) - it's extremely compiler-specific (read: not environment-generic) So, I would recommend going the improve external tool support route instead (or resort to figuring out CMake config mechanisms to generically switch object naming). Andreas Mohr -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
Re: [CMake] Incorrect object file name on cmake compilation
I think (Ravi, correct me if I'm wrong) that they're transitioning to CMake from a previously purely Visual Studio build system, and they're writing some tools to validate that the builds are ending up the same. So it's not really a problem for anybody -- I think he was just looking for an explanation of why CMake would change the obj file name. D -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
Re: [CMake] Incorrect object file name on cmake compilation
Yes. That's correct David. I was actually looking for an explanation why the object file name is coming with the suffix .cpp.obj instead of the conventional .obj. It was kind of a problem for me because the object file comparison tool uses the object file name as the reference for object file comparison. Thanks Regards Ravi Raman Xoriant Solutions Pvt. Ltd 4th Floor, Winchester, Hiranandani Business Park, Powai, Mumbai 400076, INDIA. Tel: +91 22 30511000,9930100026 Extn: 2144 Voip No. 4088344495/96/97/98 Voip Extn:1178| Fax: +91 22 3051 ravi.ra...@xoriant.com| http://www.xoriant.com -Original Message- From: David Cole [mailto:dlrd...@aol.com] Sent: Thursday, September 11, 2014 3:25 PM To: a...@lisas.de; Ravi Raman Cc: cmake@cmake.org Subject: Re: [CMake] Incorrect object file name on cmake compilation I think (Ravi, correct me if I'm wrong) that they're transitioning to CMake from a previously purely Visual Studio build system, and they're writing some tools to validate that the builds are ending up the same. So it's not really a problem for anybody -- I think he was just looking for an explanation of why CMake would change the obj file name. D -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
[CMake] Ninja generator does not clean up non-empty directories
Hi all,
Ninja does not clean out non-empty directories.
Given this CMakeLists.txt:
==
cmake_minimum_required(VERSION 2.8)
add_custom_command(
OUTPUT dir
COMMAND ${CMAKE_COMMAND} -E make_directory dir
COMMAND ${CMAKE_COMMAND} -E touch dir/file
)
add_custom_target(
dir-target DEPENDS dir
)
==
the follow commands work fine:
$ cmake -GUnix Makefiles srcdir
...
$ make
Scanning dependencies of target dir-target
[100%] Generating dir
[100%] Built target dir-target
$ make clean
$
But with Ninja, this fails:
$ cmake -GNina srcdir
..
$ ninja
[1/1] Generating dir
$ ninja clean
[1/1] Cleaning all built files...
FAILED: /home/oever/.nix-profile/bin/ninja -t clean
ninja: error: remove(dir): Directory not empty
Cleaning... 0 files.
ninja: build stopped: subcommand failed.
I assume this is a bug. I tried creating a bug db account, but could not get
past the captcha, so I'm writing here.
Cheers,
Jos
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake
[CMake] Should CPack command-line options -P and -R do more?
For a project that uses include(CPack) and produces CPack_Example-0.1.1-Linux.sh when cpack is run and produces CPack_Example-0.1.1-Linux.exe when cpack -G NSIS is run, am I remiss for thinking that cpack -G NSIS -P NEW_NAME -R 3.1.4 should produce NEW_NAME-3.1.4-Linux.exe? As always, thanks. -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
[CMake] Link step more than once
Hi, How can I create two linker steps with different flags for the same target at the same build? Example: target: X link: linker.exe libs_for_a linker_flags_for_a -o A/X.bin link: linker.exe libs_for_b linker_flags_for_b -o B/X.bin Thanks -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
[CMake] dependencies
Hi, I am working at team developing RPM pacage generator. Now I am solving a problem how can i get dependencies using cmake. Basically we need to get paths to libs like they are cached in CmakeCache.txt, is it somehow possible before calling cmake and then parsing the file ? -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
Re: [CMake] dependencies
On Thu, Sep 11, 2014 at 9:51 AM, Vojtech Mašek shooter...@gmail.com wrote: Hi, I am working at team developing RPM pacage generator. Now I am solving a problem how can i get dependencies using cmake. Basically we need to get paths to libs like they are cached in CmakeCache.txt, is it somehow possible before calling cmake and then parsing the file ? I'm a Fedora packager so I'm curious how you're going to do this. Are you planning on running something like rpm -q --whatprovides library to do this? rpmbuild will generate requirements automatically as long as there is a soname dependency, so for the most part that would be redundant except for non-library dependencies (python, perl, php, etc. or binary dependencies). Thanks, Richard -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
Re: [CMake] Link step more than once
Are you trying to generate two different libraries from the same target? On Thu, Sep 11, 2014 at 10:45 AM, fungos fun...@gmail.com wrote: Hi, How can I create two linker steps with different flags for the same target at the same build? Example: target: X link: linker.exe libs_for_a linker_flags_for_a -o A/X.bin link: linker.exe libs_for_b linker_flags_for_b -o B/X.bin Thanks -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
Re: [CMake] Incorrect object file name on cmake compilation
On 9/11/2014 7:04 AM, Ravi Raman wrote: Yes. That's correct David. I was actually looking for an explanation why the object file name is coming with the suffix .cpp.obj instead of the conventional .obj. It was kind of a problem for me because the object file comparison tool uses the object file name as the reference for object file comparison. The reason is to assure that we have unique names for the object files. Imagine a project that had main.c main.cxx and main.F90. They could not all go to main.o. Instead of having to search for duplicates like that and special case them, CMake uses a consistent and unique name for the object files. Really old CMake used to create main.o and issues like this showed up. -Bill -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
Re: [CMake] Get Visual Studio target Arch
Hi Greg, You might want to check out our current fork of CMake on http://cmakems.codeplex.com. I've just added support for multiplatform support for Windows Phone and Windows Store app in a similar way that it is done for iOS. You can try the build on http://cmakems.codeplex.com/releases/view/132284 or use the MSMultiPlatform branch. This will generate one solution that can target Win32/ARM/x64 placing each architecture in a folder based on the platform name (using the $(Platform) variable in VS. To enable this, add the following define: CMAKE_VS_EFFECTIVE_PLATFORMS=Win32;ARM;x64 and code for all three platforms will be generated. We'd love to understand the type of issues you might run into with this and how we can make it better. Thanks ~Gilles -Original Message- From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of Gregor Jasny Sent: Monday, September 8, 2014 12:06 To: cmake@cmake.org; Alexey Petruchik Subject: Re: [CMake] Get Visual Studio target Arch On 06/09/14 16:02, Alexey Petruchik wrote: I want to use different library folders for x64/x86/arm architectures. Cmake has different generators for each arch: Visual Studio 12 2013, Visual Studio 12 2013 ARM, Visual Studio 12 2013 Win64. Is there any cmake var to get visual studio target arch? CMAKE_SYSTEM_PROCESSOR is always AMD64 for me no matter what generator I'm using. All the already available stuff in cmake is not sufficient. Especially if you start to cross compile. I use the pre-defined C/C++ preprocessor symbols for that: include(CheckSymbolExists) if(WIN32) check_symbol_exists(_M_AMD64 RTC_ARCH_X64) if(NOT RTC_ARCH_X64) check_symbol_exists(_M_IX86 RTC_ARCH_X86) endif(NOT RTC_ARCH_X64) # add check for arm here # see http://msdn.microsoft.com/en-us/library/b0084kay.aspx else(WIN32) check_symbol_exists(__i386__ RTC_ARCH_X86) check_symbol_exists(__x86_64__ RTC_ARCH_X64) check_symbol_exists(__arm__ RTC_ARCH_ARM) endif(WIN32) Now you could write: if(RTC_ARCH_X64) set(MY_LIB_DIR x64) elseif(RTC_ARCH_X86) set(MY_LIB_DIR x86) elseif(RTC_ARCH_ARM) set(MY_LIB_DIR x86) else() message(FATAL_ERROR Unknown architecture) endif() I hope this helps. Thanks, Gregor -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
[CMake] [ANNOUNCE] CMake 3.0.2 Released
We are pleased to announce that CMake 3.0.2 is now available for download. Please use the latest release from our download page: http://www.cmake.org/download/ Thanks for your support! - Changes in 3.0.2 since 3.0.1: Alan W. Irwin (1): ExternalProject: Avoid infinite loop on file download hash mismatch Brad King (6): CMP0047: Fix CMAKE_COMPILER_IS_GNU(CC|CXX) in OLD behavior CMP0022: Fix version documented to support LINK_PUBLIC/LINK_PRIVATE cmListFileLexer: Fix lexing of single '[' character (#15092) Xcode: Generate per-target file references (#15111) Fix finding binutils when cross-compiling with Clang CMake 3.0.2 Christian Svensson (2): KWIML: Teach ABI.h about OpenRISC 1000 KWSys CPU: Add support for OpenRISC 1000 Stephen Kelly (2): QtAutogen: Use the basename for resource files. QtAutogen: Fix use of multiple ui files in a single target. Tim Blechmann (1): BundleUtilities: Allow Info.plist files which use CR line endings -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
Re: [CMake] Link step more than once
Yes, we can say that.. in reality I need two outputs for a single target, but these outputs are generated almost exactly with just 2 different linker flags removed. On Thu, Sep 11, 2014 at 11:31 AM, Robert Maynard robert.mayn...@kitware.com wrote: Are you trying to generate two different libraries from the same target? On Thu, Sep 11, 2014 at 10:45 AM, fungos fun...@gmail.com wrote: Hi, How can I create two linker steps with different flags for the same target at the same build? Example: target: X link: linker.exe libs_for_a linker_flags_for_a -o A/X.bin link: linker.exe libs_for_b linker_flags_for_b -o B/X.bin Thanks -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake -- Animal Liberation Front http://www.animal-liberation.com/ -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
Re: [CMake] Link step more than once
Generally the easiest way is to have two targets that share the same source files but have different linker flags. On Thu, Sep 11, 2014 at 12:53 PM, fungos fun...@gmail.com wrote: Yes, we can say that.. in reality I need two outputs for a single target, but these outputs are generated almost exactly with just 2 different linker flags removed. On Thu, Sep 11, 2014 at 11:31 AM, Robert Maynard robert.mayn...@kitware.com wrote: Are you trying to generate two different libraries from the same target? On Thu, Sep 11, 2014 at 10:45 AM, fungos fun...@gmail.com wrote: Hi, How can I create two linker steps with different flags for the same target at the same build? Example: target: X link: linker.exe libs_for_a linker_flags_for_a -o A/X.bin link: linker.exe libs_for_b linker_flags_for_b -o B/X.bin Thanks -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake -- Animal Liberation Front http://www.animal-liberation.com/ -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
Re: [CMake] Link step more than once
Ok, but will this _recompile_ the sources for each target? We must use the same generated object files for the two outputs, the only difference must be the linker flags. On Thu, Sep 11, 2014 at 1:20 PM, Robert Maynard robert.mayn...@kitware.com wrote: Generally the easiest way is to have two targets that share the same source files but have different linker flags. On Thu, Sep 11, 2014 at 12:53 PM, fungos fun...@gmail.com wrote: Yes, we can say that.. in reality I need two outputs for a single target, but these outputs are generated almost exactly with just 2 different linker flags removed. On Thu, Sep 11, 2014 at 11:31 AM, Robert Maynard robert.mayn...@kitware.com wrote: Are you trying to generate two different libraries from the same target? On Thu, Sep 11, 2014 at 10:45 AM, fungos fun...@gmail.com wrote: Hi, How can I create two linker steps with different flags for the same target at the same build? Example: target: X link: linker.exe libs_for_a linker_flags_for_a -o A/X.bin link: linker.exe libs_for_b linker_flags_for_b -o B/X.bin Thanks -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake -- Animal Liberation Front http://www.animal-liberation.com/ -- Animal Liberation Front http://www.animal-liberation.com/ -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
Re: [CMake] Link step more than once
Sounds like what you want is an object library,
http://www.cmake.org/Wiki/CMake/Tutorials/Object_Library:
set(FOO_SOURCES
Foo1.cxx
Bar2.cxx
FooBar3.cxx
)
add_library(FooObjLib OBJECT ${FOO_SOURCES})
add_executable(A $TARGET_OBJECTS:FooObjLib)
set_target_properties(A PROPERTIES LINK_FLAGS /Special /Flags /For /A)
add_executable(B $TARGET_OBJECTS:FooObjLib)
set_target_properties(B PROPERTIES LINK_FLAGS /Special /Flags /For /B)
- Chuck
On Thu, Sep 11, 2014 at 2:09 PM, fungos fun...@gmail.com wrote:
Ok, but will this _recompile_ the sources for each target? We must use the
same generated object files for the two outputs, the only difference must
be the linker flags.
On Thu, Sep 11, 2014 at 1:20 PM, Robert Maynard
robert.mayn...@kitware.com wrote:
Generally the easiest way is to have two targets that share the same
source files but have different linker flags.
On Thu, Sep 11, 2014 at 12:53 PM, fungos fun...@gmail.com wrote:
Yes, we can say that.. in reality I need two outputs for a single
target,
but these outputs are generated almost exactly with just 2 different
linker
flags removed.
On Thu, Sep 11, 2014 at 11:31 AM, Robert Maynard
robert.mayn...@kitware.com wrote:
Are you trying to generate two different libraries from the same
target?
On Thu, Sep 11, 2014 at 10:45 AM, fungos fun...@gmail.com wrote:
Hi,
How can I create two linker steps with different flags for the same
target
at the same build?
Example:
target: X
link: linker.exe libs_for_a linker_flags_for_a -o A/X.bin
link: linker.exe libs_for_b linker_flags_for_b -o B/X.bin
Thanks
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For
more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake
--
Animal Liberation Front
http://www.animal-liberation.com/
--
Animal Liberation Front
http://www.animal-liberation.com/
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake
[CMake] FW: Parallel GNU make issue
I have a strange, and very frustrating, problem. I have a pretty large piece of software that I build nightly as part of regression testing of my own software. All of the software uses CMake and I use a ctest script, via ctest -S [script file], for my nightly regression testing . As I stated, this is a pretty large collection of software but during development it's not a huge issue because the build is quite parallelizable via GNU make's -j N option. On my nightly test platform, a 64-core machine, I can build the whole thing in about an hour. A nice manageable amount of time for a nightly regression test. Unfortunately when I run the build process via ctest something is causing the parallel make to fail and I'm lucky if the build takes under 15 hours. Barely practical for a nightly test. I'm not sure how to find out what's going on. After the ctest build I can go into the build directory, do a make clean and then a make -j 12, for example, and the build flies. Of course I can build the software entirely outside of ctest and it too flies. Only when the build happens as part of ctest does it seem to revert to, essentially, a make -j 1 and slow to a crawl. I can look at the process tree, via ps -ef, during the ctest build and I see the root invocation of gmake and it's fine. For example, it typically looks something like: PID PPID C STIME TTY TIME CMD 6141 6283 96 11:41 pts/000:24:40 ctest -VV -S ctest_nightly.cmake -DPROCESSORCOUNT=12 8032 6141 0 11:42 pts/000:00:00 /usr/bin/gmake -i -j 12 8035 8032 0 11:42 pts/000:00:00 /usr/bin/gmake -f CMakeFiles/Makefile2 all 851 8035 0 11:52 pts/000:00:00 /usr/bin/gmake -f packages/ml/src/CMakeFiles/ml.dir/build.make 27797 8035 0 11:46 pts/000:00:00 /usr/bin/gmake -f packages/moocho/src/CMakeFiles/moocho.dir/build.make You can see that the parent make, PID 8032 which is started via ctest (PID 6141), has the appropriate flag, -j 12, but at this point in the build it's compiling one file at a time. Another odd thing is that I think the build starts out fine, invoking multiple file compilations simultaneously, but after a couple of minutes it reverts to essentially the make -j 1 behavior. It's like the GNU make jobserver is failing, but I'm not getting any error messages from GNU make to that affect. If anyone has any suggestions on how I can figure this out I'd appreciate it. Apologies for the lengthy explanation. I've been pulling my hair out trying to figure out how to solve this issue. Thanks in advance, Gary -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
Re: [CMake] FW: Parallel GNU make issue
Hi Gary, Do you see either of these two warning messages show up: warning: -jN forced in submake: disabling jobserver mode. or warning: jobserver unavailable: using -j1. Add `+' to parent make rule. These warnings often accompany the forced serialization of a parallel make build, although usually they show up regardless of the launch method, i.e. ctests vs manual make. These warnings are often indicative of a particular problem in super-build scenarios.. - Chuck On Thu, Sep 11, 2014 at 2:29 PM, Hennigan, Gary L glhe...@sandia.gov wrote: I have a strange, and very frustrating, problem. I have a pretty large piece of software that I build nightly as part of regression testing of my own software. All of the software uses CMake and I use a ctest script, via “ctest –S [script file]”, for my nightly regression testing . As I stated, this is a pretty large collection of software but during development it’s not a huge issue because the build is quite parallelizable via GNU make’s “-j N” option. On my nightly test platform, a 64-core machine, I can build the whole thing in about an hour. A nice manageable amount of time for a nightly regression test. Unfortunately when I run the build process via ctest something is causing the parallel make to fail and I’m lucky if the build takes under 15 hours. Barely practical for a nightly test. I’m not sure how to find out what’s going on. After the ctest build I can go into the build directory, do a “make clean” and then a “make –j 12”, for example, and the build flies. Of course I can build the software entirely outside of ctest and it too flies. Only when the build happens as part of ctest does it seem to revert to, essentially, a “make –j 1” and slow to a crawl. I can look at the process tree, via “ps –ef”, during the ctest build and I see the root invocation of gmake and it’s fine. For example, it typically looks something like: PID PPID C STIME TTY TIME CMD 6141 6283 96 11:41 pts/000:24:40 ctest -VV -S ctest_nightly.cmake -DPROCESSORCOUNT=12 8032 6141 0 11:42 pts/000:00:00 /usr/bin/gmake -i *-j 12* 8035 8032 0 11:42 pts/000:00:00 /usr/bin/gmake -f CMakeFiles/Makefile2 all 851 8035 0 11:52 pts/000:00:00 /usr/bin/gmake -f packages/ml/src/CMakeFiles/ml.dir/build.make 27797 8035 0 11:46 pts/000:00:00 /usr/bin/gmake -f packages/moocho/src/CMakeFiles/moocho.dir/build.make You can see that the parent make, PID 8032 which is started via ctest (PID 6141), has the appropriate flag, “-j 12”, but at this point in the build it’s compiling one file at a time. Another odd thing is that I think the build starts out fine, invoking multiple file compilations simultaneously, but after a couple of minutes it reverts to essentially the “make –j 1” behavior. It’s like the GNU make jobserver is failing, but I’m not getting any error messages from GNU make to that affect. If anyone has any suggestions on how I can figure this out I’d appreciate it. Apologies for the lengthy explanation. I’ve been pulling my hair out trying to figure out how to solve this issue. Thanks in advance, Gary -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
Re: [CMake] missing INTERFACE_LINK_LIBRARIES in target export files
Excuses; I found the target property setting in the respective
`myLibTargets-none.cmake` file:
```
set_target_properties(myLib PROPERTIES
IMPORTED_LINK_INTERFACE_LIBRARIES_NONE /usr/lib/liblapack.so
IMPORTED_LOCATION_NONE
${_IMPORT_PREFIX}/lib/x86_64-linux-gnu/libmylib.so.1.0
IMPORTED_SONAME_NONE libmylib.so.1
)
```
Cheers,
Nico
On Thu, Sep 11, 2014 at 2:07 AM, Nico Schlömer nico.schloe...@gmail.com wrote:
Hi all,
in a CMake project of mine, I build shared libraries and link against
third-party shared libraries. In the export target files, I find
```
add_library(mylib SHARED IMPORTED)
```
as expected, but I'm *missing* anything along the lines of
```
set_target_properties(mylib PROPERTIES
INTERFACE_INCLUDE_DIRECTORIES ${_IMPORT_PREFIX}/include
INTERFACE_LINK_LIBRARIES /usr/lib/lapack.so
)
```
Any idea why this isn't present? Note that I'm *not* using the
`PRIVATE` keyword in `TARGET_LINK_LIBRARIES()`.
Cheers,
Nico
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake
Re: [CMake] FW: Parallel GNU make issue
Thanks for the reply Chuck. Unfortunately there is no such message. I’m not even sure the GNU make jobserver is the problem. It’s just that the symptom is the same as if that were happening. Am I comparing apples to apples when I go into the build directory created via ctest and invoking gmake manually, and comparing that to the way ctest is invoking gmake? Manually, after I notice the ctest build has regressed to a single compile at a time, I kill ctest then I go to the build directory it created and do gmake clean find . –name ‘*.o’ –print|xargs rm touch CMakeCache.txt gmake –j 10 As I said, there’s a dramatic difference between the two. The manual build proceeds as I would expect and is done within an hour. The ctest build takes many times longer. I should’ve mentioned that I’m using the 2.8.12.2 version of the tools. Gary From: Chuck Atkins [mailto:chuck.atk...@kitware.com] Sent: Thursday, September 11, 2014 1:03 PM To: Hennigan, Gary L Cc: cmake@cmake.org Subject: [EXTERNAL] Re: [CMake] FW: Parallel GNU make issue Hi Gary, Do you see either of these two warning messages show up: warning: -jN forced in submake: disabling jobserver mode. or warning: jobserver unavailable: using -j1. Add `+' to parent make rule. These warnings often accompany the forced serialization of a parallel make build, although usually they show up regardless of the launch method, i.e. ctests vs manual make. These warnings are often indicative of a particular problem in super-build scenarios.. - Chuck On Thu, Sep 11, 2014 at 2:29 PM, Hennigan, Gary L glhe...@sandia.govmailto:glhe...@sandia.gov wrote: I have a strange, and very frustrating, problem. I have a pretty large piece of software that I build nightly as part of regression testing of my own software. All of the software uses CMake and I use a ctest script, via “ctest –S [script file]”, for my nightly regression testing . As I stated, this is a pretty large collection of software but during development it’s not a huge issue because the build is quite parallelizable via GNU make’s “-j N” option. On my nightly test platform, a 64-core machine, I can build the whole thing in about an hour. A nice manageable amount of time for a nightly regression test. Unfortunately when I run the build process via ctest something is causing the parallel make to fail and I’m lucky if the build takes under 15 hours. Barely practical for a nightly test. I’m not sure how to find out what’s going on. After the ctest build I can go into the build directory, do a “make clean” and then a “make –j 12”, for example, and the build flies. Of course I can build the software entirely outside of ctest and it too flies. Only when the build happens as part of ctest does it seem to revert to, essentially, a “make –j 1” and slow to a crawl. I can look at the process tree, via “ps –ef”, during the ctest build and I see the root invocation of gmake and it’s fine. For example, it typically looks something like: PID PPID C STIME TTY TIME CMD 6141 6283 96 11:41 pts/000:24:40 ctest -VV -S ctest_nightly.cmake -DPROCESSORCOUNT=12 8032 6141 0 11:42 pts/000:00:00 /usr/bin/gmake -i -j 12 8035 8032 0 11:42 pts/000:00:00 /usr/bin/gmake -f CMakeFiles/Makefile2 all 851 8035 0 11:52 pts/000:00:00 /usr/bin/gmake -f packages/ml/src/CMakeFiles/ml.dir/build.make 27797 8035 0 11:46 pts/000:00:00 /usr/bin/gmake -f packages/moocho/src/CMakeFiles/moocho.dir/build.make You can see that the parent make, PID 8032 which is started via ctest (PID 6141), has the appropriate flag, “-j 12”, but at this point in the build it’s compiling one file at a time. Another odd thing is that I think the build starts out fine, invoking multiple file compilations simultaneously, but after a couple of minutes it reverts to essentially the “make –j 1” behavior. It’s like the GNU make jobserver is failing, but I’m not getting any error messages from GNU make to that affect. If anyone has any suggestions on how I can figure this out I’d appreciate it. Apologies for the lengthy explanation. I’ve been pulling my hair out trying to figure out how to solve this issue. Thanks in advance, Gary -- Powered by www.kitware.comhttp://www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware
Re: [CMake] Link step more than once
Cool, this did the trick. It was needed a post-build step to rename the
target but it works.
Thank you
On Thu, Sep 11, 2014 at 2:19 PM, Chuck Atkins chuck.atk...@kitware.com
wrote:
Sounds like what you want is an object library,
http://www.cmake.org/Wiki/CMake/Tutorials/Object_Library:
set(FOO_SOURCES
Foo1.cxx
Bar2.cxx
FooBar3.cxx
)
add_library(FooObjLib OBJECT ${FOO_SOURCES})
add_executable(A $TARGET_OBJECTS:FooObjLib)
set_target_properties(A PROPERTIES LINK_FLAGS /Special /Flags /For /A)
add_executable(B $TARGET_OBJECTS:FooObjLib)
set_target_properties(B PROPERTIES LINK_FLAGS /Special /Flags /For /B)
- Chuck
On Thu, Sep 11, 2014 at 2:09 PM, fungos fun...@gmail.com wrote:
Ok, but will this _recompile_ the sources for each target? We must use
the same generated object files for the two outputs, the only difference
must be the linker flags.
On Thu, Sep 11, 2014 at 1:20 PM, Robert Maynard
robert.mayn...@kitware.com wrote:
Generally the easiest way is to have two targets that share the same
source files but have different linker flags.
On Thu, Sep 11, 2014 at 12:53 PM, fungos fun...@gmail.com wrote:
Yes, we can say that.. in reality I need two outputs for a single
target,
but these outputs are generated almost exactly with just 2 different
linker
flags removed.
On Thu, Sep 11, 2014 at 11:31 AM, Robert Maynard
robert.mayn...@kitware.com wrote:
Are you trying to generate two different libraries from the same
target?
On Thu, Sep 11, 2014 at 10:45 AM, fungos fun...@gmail.com wrote:
Hi,
How can I create two linker steps with different flags for the same
target
at the same build?
Example:
target: X
link: linker.exe libs_for_a linker_flags_for_a -o A/X.bin
link: linker.exe libs_for_b linker_flags_for_b -o B/X.bin
Thanks
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For
more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake
--
Animal Liberation Front
http://www.animal-liberation.com/
--
Animal Liberation Front
http://www.animal-liberation.com/
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake
--
Animal Liberation Front
http://www.animal-liberation.com/
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake
[CMake] install(EXPORT ...) includes target B which requires target A that is not in the export set
Hi all,
One of my projects contains two libraries libA and libB, where libB
depends on libA, and both are exporting their configuration through
the usual `INSTALL(EXPORT ...)` mechanisms.
I'm getting errors of the type
```
CMake Error: install(EXPORT SEACASNemesis-exports ...) includes
target nemesis which requires target exodus that is not in the
export set.
```
now, and I'm not quite sure what they mean. Do all of my export files
have to be self-contained?
In other projects of mine, CMake was happy to produce target files with
```
set_target_properties(teuchosnumerics PROPERTIES
IMPORTED_LINK_INTERFACE_LIBRARIES_NONE
B;A;/usr/lib/liblapack.so;/usr/lib/libblas.so
IMPORTED_LOCATION_NONE ${_IMPORT_PREFIX}/lib/x86_64-linux-gnu/libB.so.11.11
IMPORTED_SONAME_NONE libB.so.11
)
```
without A appearing in the same target file.
Cheers,
Nico
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake
Re: [CMake] Link step more than once
Set the OUTPUT_NAME or OUTPUT_NAME_CONFIG property on the target to
change what the name of the generated library will be. This will
eliminate the need for a post-build step.
On Thu, Sep 11, 2014 at 4:16 PM, fungos fun...@gmail.com wrote:
Cool, this did the trick. It was needed a post-build step to rename the
target but it works.
Thank you
On Thu, Sep 11, 2014 at 2:19 PM, Chuck Atkins chuck.atk...@kitware.com
wrote:
Sounds like what you want is an object library,
http://www.cmake.org/Wiki/CMake/Tutorials/Object_Library:
set(FOO_SOURCES
Foo1.cxx
Bar2.cxx
FooBar3.cxx
)
add_library(FooObjLib OBJECT ${FOO_SOURCES})
add_executable(A $TARGET_OBJECTS:FooObjLib)
set_target_properties(A PROPERTIES LINK_FLAGS /Special /Flags /For /A)
add_executable(B $TARGET_OBJECTS:FooObjLib)
set_target_properties(B PROPERTIES LINK_FLAGS /Special /Flags /For /B)
- Chuck
On Thu, Sep 11, 2014 at 2:09 PM, fungos fun...@gmail.com wrote:
Ok, but will this _recompile_ the sources for each target? We must use
the same generated object files for the two outputs, the only difference
must be the linker flags.
On Thu, Sep 11, 2014 at 1:20 PM, Robert Maynard
robert.mayn...@kitware.com wrote:
Generally the easiest way is to have two targets that share the same
source files but have different linker flags.
On Thu, Sep 11, 2014 at 12:53 PM, fungos fun...@gmail.com wrote:
Yes, we can say that.. in reality I need two outputs for a single
target,
but these outputs are generated almost exactly with just 2 different
linker
flags removed.
On Thu, Sep 11, 2014 at 11:31 AM, Robert Maynard
robert.mayn...@kitware.com wrote:
Are you trying to generate two different libraries from the same
target?
On Thu, Sep 11, 2014 at 10:45 AM, fungos fun...@gmail.com wrote:
Hi,
How can I create two linker steps with different flags for the same
target
at the same build?
Example:
target: X
link: linker.exe libs_for_a linker_flags_for_a -o A/X.bin
link: linker.exe libs_for_b linker_flags_for_b -o B/X.bin
Thanks
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For
more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake
--
Animal Liberation Front
http://www.animal-liberation.com/
--
Animal Liberation Front
http://www.animal-liberation.com/
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake
--
Animal Liberation Front
http://www.animal-liberation.com/
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake
Re: [CMake] install(EXPORT ...) includes target B which requires target A that is not in the export set
On Thursday, September 11, 2014 23:51:21 Nico Schlömer wrote: Hi all, One of my projects contains two libraries libA and libB, where libB depends on libA, and both are exporting their configuration through the usual `INSTALL(EXPORT ...)` mechanisms. I'm getting errors of the type ``` CMake Error: install(EXPORT SEACASNemesis-exports ...) includes target nemesis which requires target exodus that is not in the export set. ``` now, and I'm not quite sure what they mean. Do all of my export files have to be self-contained? IIRC, it should complain if it detects that a target is needed which is not exported at all. Alex -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
Re: [CMake] FW: Parallel GNU make issue
On 9/11/2014 4:09 PM, Hennigan, Gary L wrote: Thanks for the reply Chuck. Do you have an external projects in this build? -Bill -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
Re: [CMake] FW: Parallel GNU make issue
Is there a significant amount of output from make? What does make do if it's running low on RAM? ctest may be holding onto too much memory trying to process the output if it's very large... Just a thought -- worth a look, though. D -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
Re: [CMake] Should CPack command-line options -P and -R do more?
Or are these customizing CPack command line options mostly meant to be used with a CPACK_PROJECT_CONFIG_FILE? On Thu, Sep 11, 2014 at 9:07 AM, Iosif Neitzke iosif.neitzke+cm...@gmail.com wrote: For a project that uses include(CPack) and produces CPack_Example-0.1.1-Linux.sh when cpack is run and produces CPack_Example-0.1.1-Linux.exe when cpack -G NSIS is run, am I remiss for thinking that cpack -G NSIS -P NEW_NAME -R 3.1.4 should produce NEW_NAME-3.1.4-Linux.exe? As always, thanks. -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
[Cmake-commits] CMake branch, hooks, updated. 6f2466c503b192c2065bcdc2135137ec5c74ceef
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, hooks has been updated
via 6f2466c503b192c2065bcdc2135137ec5c74ceef (commit)
from b9b952190a736e30ef33f2a75cf4aab45bcb3b5a (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=6f2466c503b192c2065bcdc2135137ec5c74ceef
commit 6f2466c503b192c2065bcdc2135137ec5c74ceef
Author: Brad King brad.k...@kitware.com
AuthorDate: Wed Sep 10 16:31:32 2014 -0400
Commit: Brad King brad.k...@kitware.com
CommitDate: Wed Sep 10 16:31:32 2014 -0400
Add a 'pre-push' hook
For now do nothing but chain to a project-specific hook.
diff --git a/hooks-config.bash b/hooks-config.bash
index afdbf9d..3cb29af 100644
--- a/hooks-config.bash
+++ b/hooks-config.bash
@@ -59,7 +59,7 @@ hooks_child() {
*) prefix=./ ;;
esac
if test -x $prefix$child ; then
- $prefix$child $@
+ echo $stdin | $prefix$child $@
fi
}
diff --git a/pre-push b/pre-push
new file mode 100755
index 000..4e7c9fd
--- /dev/null
+++ b/pre-push
@@ -0,0 +1,24 @@
+#!/usr/bin/env bash
+#=
+# Copyright 2010-2014 Kitware, Inc.
+#
+# Licensed under the Apache License, Version 2.0 (the License);
+# you may not use this file except in compliance with the License.
+# You may obtain a copy of the License at
+#
+# http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an AS IS BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+#=
+
+. ${BASH_SOURCE%/*}/hooks-config.bash
+
+# Read all input up front so we can use it and hand it to the chained hook.
+stdin=$(cat)
+
+# Chain to project-specific hook.
+hooks_chain pre-push $@
---
Summary of changes:
hooks-config.bash |2 +-
prepare-commit-msg = pre-push | 17 -
2 files changed, 5 insertions(+), 14 deletions(-)
copy prepare-commit-msg = pre-push (62%)
hooks/post-receive
--
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits
[Cmake-commits] CMake branch, next, updated. v3.0.1-5283-ga3fa292
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 a3fa29228138e26839fcbf8948db5d714fa483b9 (commit)
via 4b4555de3e2fc1782298003cbd7efdd10bfbd685 (commit)
from 9c6cff6c5dd76653a24a96a3462e34e8341dbaee (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=a3fa29228138e26839fcbf8948db5d714fa483b9
commit a3fa29228138e26839fcbf8948db5d714fa483b9
Merge: 9c6cff6 4b4555d
Author: Brad King brad.k...@kitware.com
AuthorDate: Thu Sep 11 08:48:28 2014 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Thu Sep 11 08:48:28 2014 -0400
Merge topic 'doc-WINCE-var' into next
4b4555de Help: Document the WINCE variable
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=4b4555de3e2fc1782298003cbd7efdd10bfbd685
commit 4b4555de3e2fc1782298003cbd7efdd10bfbd685
Author: Pascal Bach pascal.b...@siemens.com
AuthorDate: Thu Sep 11 11:07:35 2014 +0200
Commit: Brad King brad.k...@kitware.com
CommitDate: Thu Sep 11 08:44:20 2014 -0400
Help: Document the WINCE variable
diff --git a/Help/manual/cmake-variables.7.rst
b/Help/manual/cmake-variables.7.rst
index 149e4ac..b00c16e 100644
--- a/Help/manual/cmake-variables.7.rst
+++ b/Help/manual/cmake-variables.7.rst
@@ -192,6 +192,7 @@ Variables that Describe the System
/variable/MSVC_VERSION
/variable/UNIX
/variable/WIN32
+ /variable/WINCE
/variable/WINDOWS_PHONE
/variable/WINDOWS_STORE
/variable/XCODE_VERSION
diff --git a/Help/variable/WINCE.rst b/Help/variable/WINCE.rst
new file mode 100644
index 000..54ff7de
--- /dev/null
+++ b/Help/variable/WINCE.rst
@@ -0,0 +1,5 @@
+WINCE
+-
+
+True when the :variable:`CMAKE_SYSTEM_NAME` variable is set
+to ``WindowsCE``.
---
Summary of changes:
Help/manual/cmake-variables.7.rst |1 +
Help/variable/{WINDOWS_PHONE.rst = WINCE.rst} |6 +++---
2 files changed, 4 insertions(+), 3 deletions(-)
copy Help/variable/{WINDOWS_PHONE.rst = WINCE.rst} (55%)
hooks/post-receive
--
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits
[Cmake-commits] CMake branch, next, updated. v3.0.1-5285-gde3cfe7
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 de3cfe7da8659b0e5689bdc5b653f8425d1e2bf0 (commit) via 908c74399a737d878e18823e00730964896d1184 (commit) from a3fa29228138e26839fcbf8948db5d714fa483b9 (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=de3cfe7da8659b0e5689bdc5b653f8425d1e2bf0 commit de3cfe7da8659b0e5689bdc5b653f8425d1e2bf0 Merge: a3fa292 908c743 Author: Brad King brad.k...@kitware.com AuthorDate: Thu Sep 11 08:55:54 2014 -0400 Commit: CMake Topic Stage kwro...@kitware.com CommitDate: Thu Sep 11 08:55:54 2014 -0400 Merge topic 'doc-check-results-cached' into next 908c7439 Help: Document that the CHECK_* macros create cache variables http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=908c74399a737d878e18823e00730964896d1184 commit 908c74399a737d878e18823e00730964896d1184 Author: Sebastian Leske sebastian.le...@sleske.name AuthorDate: Wed Sep 10 08:35:49 2014 +0200 Commit: Brad King brad.k...@kitware.com CommitDate: Thu Sep 11 08:55:26 2014 -0400 Help: Document that the CHECK_* macros create cache variables Otherwise callers may expect to be able to re-use result variables. diff --git a/Modules/CheckCCompilerFlag.cmake b/Modules/CheckCCompilerFlag.cmake index efdac20..53f3454 100644 --- a/Modules/CheckCCompilerFlag.cmake +++ b/Modules/CheckCCompilerFlag.cmake @@ -10,6 +10,7 @@ # # flag - the compiler flag # var - variable to store the result +#Will be created as an internal cache variable. # # This internally calls the check_c_source_compiles macro and sets # CMAKE_REQUIRED_DEFINITIONS to flag. See help for diff --git a/Modules/CheckCSourceCompiles.cmake b/Modules/CheckCSourceCompiles.cmake index 7523446..6e80fb5 100644 --- a/Modules/CheckCSourceCompiles.cmake +++ b/Modules/CheckCSourceCompiles.cmake @@ -10,6 +10,7 @@ # # code - source code to try to compile, must define 'main' # var- variable to store whether the source code compiled +# Will be created as an internal cache variable. # fail-regex - fail if test output matches this regex # # The following variables may be set before calling this macro to modify diff --git a/Modules/CheckCSourceRuns.cmake b/Modules/CheckCSourceRuns.cmake index 0fb0f23..0ce423c 100644 --- a/Modules/CheckCSourceRuns.cmake +++ b/Modules/CheckCSourceRuns.cmake @@ -11,6 +11,7 @@ # code - source code to try to compile # var- variable to store the result # (1 for success, empty for failure) +# Will be created as an internal cache variable. # # The following variables may be set before calling this macro to modify # the way the check is run: diff --git a/Modules/CheckCXXSourceCompiles.cmake b/Modules/CheckCXXSourceCompiles.cmake index edd62a6..6d52ec6 100644 --- a/Modules/CheckCXXSourceCompiles.cmake +++ b/Modules/CheckCXXSourceCompiles.cmake @@ -10,6 +10,7 @@ # # code - source code to try to compile, must define 'main' # var- variable to store whether the source code compiled +# Will be created as an internal cache variable. # fail-regex - fail if test output matches this regex # # The following variables may be set before calling this macro to modify diff --git a/Modules/CheckCXXSourceRuns.cmake b/Modules/CheckCXXSourceRuns.cmake index 02731f8..3c06d75 100644 --- a/Modules/CheckCXXSourceRuns.cmake +++ b/Modules/CheckCXXSourceRuns.cmake @@ -11,6 +11,7 @@ # code - source code to try to compile # var- variable to store the result # (1 for success, empty for failure) +# Will be created as an internal cache variable. # # The following variables may be set before calling this macro to modify # the way the check is run: diff --git a/Modules/CheckFortranFunctionExists.cmake b/Modules/CheckFortranFunctionExists.cmake index 0b12289..bd52f61 100644 --- a/Modules/CheckFortranFunctionExists.cmake +++ b/Modules/CheckFortranFunctionExists.cmake @@ -10,6 +10,7 @@ # # FUNCTION - the name of the Fortran function # VARIABLE - variable to store the result +# Will be created as an internal cache variable. # # # diff --git a/Modules/CheckFortranSourceCompiles.cmake b/Modules/CheckFortranSourceCompiles.cmake index 63e4539..f90d05b 100644 --- a/Modules/CheckFortranSourceCompiles.cmake +++ b/Modules/CheckFortranSourceCompiles.cmake @@ -12,6 +12,7 @@ # Source code to try to compile. It must define a PROGRAM entry point. # ``var`` # Variable to store whether the source code compiled. +# Will be created as an
[Cmake-commits] CMake branch, next, updated. v3.0.2-5268-g0f63c7d
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 0f63c7d223d5d134bb13953af261857b7288e91f (commit) via aa2b64b28b4b74601f2ecd67a400d6d472d1ab9e (commit) via 527dfe2a4fb026107a803997b1e8a4a7dab57a75 (commit) via 28012f3eef5067a6a4b2de3fc4f421949ef8ada9 (commit) from de3cfe7da8659b0e5689bdc5b653f8425d1e2bf0 (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=0f63c7d223d5d134bb13953af261857b7288e91f commit 0f63c7d223d5d134bb13953af261857b7288e91f Merge: aa2b64b 527dfe2 Author: Brad King brad.k...@kitware.com AuthorDate: Thu Sep 11 09:11:49 2014 -0400 Commit: Brad King brad.k...@kitware.com CommitDate: Thu Sep 11 09:11:49 2014 -0400 Merge branch 'master' into next http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=aa2b64b28b4b74601f2ecd67a400d6d472d1ab9e commit aa2b64b28b4b74601f2ecd67a400d6d472d1ab9e Merge: de3cfe7 28012f3 Author: Brad King brad.k...@kitware.com AuthorDate: Thu Sep 11 09:11:41 2014 -0400 Commit: Brad King brad.k...@kitware.com CommitDate: Thu Sep 11 09:11:41 2014 -0400 Merge branch 'master' into next --- Summary of changes: Source/CMakeVersion.cmake |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- CMake ___ Cmake-commits mailing list Cmake-commits@cmake.org http://public.kitware.com/mailman/listinfo/cmake-commits
[Cmake-commits] CMake branch, master, updated. v3.0.2-1849-g453f20d
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, master has been updated via 453f20d89381d8d5c2e7afb91559c754dc03910e (commit) from b36a795163a5835abc3bb507fcb53bc4bf06146c (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=453f20d89381d8d5c2e7afb91559c754dc03910e commit 453f20d89381d8d5c2e7afb91559c754dc03910e Author: Kitware Robot kwro...@kitware.com AuthorDate: Fri Sep 12 00:01:14 2014 -0400 Commit: Kitware Robot kwro...@kitware.com CommitDate: Fri Sep 12 00:01:14 2014 -0400 CMake Nightly Date Stamp diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake index 14909d8..21057d3 100644 --- a/Source/CMakeVersion.cmake +++ b/Source/CMakeVersion.cmake @@ -1,5 +1,5 @@ # CMake version number components. set(CMake_VERSION_MAJOR 3) set(CMake_VERSION_MINOR 0) -set(CMake_VERSION_PATCH 20140911) +set(CMake_VERSION_PATCH 20140912) #set(CMake_VERSION_RC 1) --- Summary of changes: Source/CMakeVersion.cmake |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- CMake ___ Cmake-commits mailing list Cmake-commits@cmake.org http://public.kitware.com/mailman/listinfo/cmake-commits
