Re: [cmake-developers] Modules/GetPrequisites.cmake issues
On Monday, August 03, 2015 10:22:18 AM Brad King wrote: On 07/30/2015 10:56 AM, Brad King wrote: Thanks! Applied: Those patches exposed a bug in FindMPI, so I fixed that and rebased the other changes on it: FindMPI: Drop unnecessary and incorrect use of GetPrerequisites http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=1c46b6ae GetPrerequisites: Add error checks for execute_process() calls http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=afb674ab GetPrerequisites: Optionally filter objdump output for speed http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=5d0a8b1a -Brad Thanks. I believe that also fixes http://www.cmake.org/Bug/view.php?id=13351 Clint -- 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] CDash problems
OK, I finally have a build of boost I can rely on which enables me to try this out for you again. Using the following source tree, I am able to get a successful build test of Safe Numerics, other than a couple of warnings, and it actually submits to the CDash dashboard, no problem. Source tree: davidcole@TRIVET /c/dev/repos/safe_numerics (master) $ git log -1 commit 569dc083c96845f06c5bf7a9d9d6756fd45d43bd Author: Robert Ramey ra...@rrsd.com Date: Sun Feb 1 21:14:12 2015 -0800 updated html documentation Script used to build and submit dashboard (w/ CMake 3.3.0, ninja, MS compiler from Visual Studio 2013, and a boost install with system layout): @rem Windows cmd script build-SafeNumerics.cmd setlocal set build_dir=%~n0 rmdir /q /s %build_dir% mkdir %build_dir% pushd %build_dir% cmake ^ -DBOOST_ROOT=C:\dev\NSB\x86\Release\boost ^ -DCMAKE_BUILD_TYPE=Release ^ -G Ninja C:\dev\repos\safe_numerics\CMake ninja Experimental popd endlocal Results: http://my.cdash.org/buildSummary.php?buildid=803237 When I update to most recent master (source at commit 78111d12), it still submits, but there are build errors in it: http://my.cdash.org/buildSummary.php?buildid=803238 The CMake/CDash stuff looks reasonable from my perspective. I haven't dug into all the details or anything, but it basically works, provided you have a boost install to point it to. I have no problems at all submitting dashboards for this project. If you want, I actually have a machine at work that is already submitting some open source dashboards -- if you'd like, I can add a Nightly run for Safe Numerics in this Windows/VS2013 environment since it is small and quick to run. HTH, David C. On Thu, Jun 25, 2015 at 12:16 PM, David Cole dlrd...@aol.com wrote: I cloned your project [Safe Numerics](https://github.com/robertramey/safe_numerics) to try to help you out by attempting to reproduce this problem. I see the most recent activity is in the policies branch, but I don't see anything in the whole repo, in either 'master' or 'policies' branches that refer to how to build it via CMake, or how to attempt to submit a CDash build... I browsed through the html docs and did a 'git grep -i experimental' to no avail. Do you have build instructions? Should I just configure using the CMake/CMakeLists.txt file and then try to build the Experimental target? Will it build ok on Windows with VS 2013, or Ninja plus that compiler? Thx, David C. On Thu, Jun 25, 2015 at 10:44 AM, Robert Ramey ra...@rrsd.com wrote: I set up a project on the cdash.org website. When I invoke the experimental target it runs the tests and uploads the results to cdash.org. So far so good. In my github project and documentation I've encouraged uses of this project to use CMake to build it and test it and run the experimental target so that their test results will also appear on the cdash dashboard. But when someone other than myself tries to do this, I get an emal from ad...@cdhash.org which says: Object: Cannot create handler based on XML content An XML submission from 42.156.137.83 to the project Safe Numerics cannot be parsed. The content of the file is as follow: -CDash on my.cdash.org What do I have to do to find out the problem and fix this? The project is Safe Numerics http://my.cdash.org/index.php?project=Safe+Numerics Robert Ramey -- 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-commits] CMake branch, next, updated. v3.3.0-1799-g940f14e
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 940f14edf440b4a58ed4f22468ae9bf474b46629 (commit)
via d951f5429a116e6174f9cdb983945cb01cf37553 (commit)
from 8b0fd7f79a86971233d8561ed9fc8cc2d6df9372 (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=940f14edf440b4a58ed4f22468ae9bf474b46629
commit 940f14edf440b4a58ed4f22468ae9bf474b46629
Merge: 8b0fd7f d951f54
Author: Brad King brad.k...@kitware.com
AuthorDate: Mon Aug 3 10:26:08 2015 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Mon Aug 3 10:26:08 2015 -0400
Merge topic 'doc-ninja-rule-launchers' into next
d951f542 Help: Refine RULE_LAUNCH_{COMPILE,CUSTOM,LINK} global property docs
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=d951f5429a116e6174f9cdb983945cb01cf37553
commit d951f5429a116e6174f9cdb983945cb01cf37553
Author: Brad King brad.k...@kitware.com
AuthorDate: Mon Aug 3 10:19:49 2015 -0400
Commit: Brad King brad.k...@kitware.com
CommitDate: Mon Aug 3 10:25:53 2015 -0400
Help: Refine RULE_LAUNCH_{COMPILE,CUSTOM,LINK} global property docs
Link to the generators that implement these properties. Explain in
more detail why other generators ignore them.
diff --git a/Help/prop_gbl/RULE_LAUNCH_COMPILE.rst
b/Help/prop_gbl/RULE_LAUNCH_COMPILE.rst
index 980843b..e0df878 100644
--- a/Help/prop_gbl/RULE_LAUNCH_COMPILE.rst
+++ b/Help/prop_gbl/RULE_LAUNCH_COMPILE.rst
@@ -3,7 +3,9 @@ RULE_LAUNCH_COMPILE
Specify a launcher for compile rules.
-Makefile generators prefix compiler commands with the given launcher
-command line. This is intended to allow launchers to intercept build
-problems with high granularity. Non-Makefile generators currently
-ignore this property.
+:ref:`Makefile Generators` and the :generator:`Ninja` generator prefix
+compiler commands with the given launcher command line.
+This is intended to allow launchers to intercept build problems
+with high granularity. Other generators ignore this property
+because their underlying build systems provide no hook to wrap
+individual commands with a launcher.
diff --git a/Help/prop_gbl/RULE_LAUNCH_CUSTOM.rst
b/Help/prop_gbl/RULE_LAUNCH_CUSTOM.rst
index 9d4a25c..b20c59b 100644
--- a/Help/prop_gbl/RULE_LAUNCH_CUSTOM.rst
+++ b/Help/prop_gbl/RULE_LAUNCH_CUSTOM.rst
@@ -3,7 +3,9 @@ RULE_LAUNCH_CUSTOM
Specify a launcher for custom rules.
-Makefile generators prefix custom commands with the given launcher
-command line. This is intended to allow launchers to intercept build
-problems with high granularity. Non-Makefile generators currently
-ignore this property.
+:ref:`Makefile Generators` and the :generator:`Ninja` generator prefix
+custom commands with the given launcher command line.
+This is intended to allow launchers to intercept build problems
+with high granularity. Other generators ignore this property
+because their underlying build systems provide no hook to wrap
+individual commands with a launcher.
diff --git a/Help/prop_gbl/RULE_LAUNCH_LINK.rst
b/Help/prop_gbl/RULE_LAUNCH_LINK.rst
index 191f1d5..567bb68 100644
--- a/Help/prop_gbl/RULE_LAUNCH_LINK.rst
+++ b/Help/prop_gbl/RULE_LAUNCH_LINK.rst
@@ -3,7 +3,9 @@ RULE_LAUNCH_LINK
Specify a launcher for link rules.
-Makefile generators prefix link and archive commands with the given
-launcher command line. This is intended to allow launchers to
-intercept build problems with high granularity. Non-Makefile
-generators currently ignore this property.
+:ref:`Makefile Generators` and the :generator:`Ninja` generator prefix
+link and archive commands with the given launcher command line.
+This is intended to allow launchers to intercept build problems
+with high granularity. Other generators ignore this property
+because their underlying build systems provide no hook to wrap
+individual commands with a launcher.
---
Summary of changes:
Help/prop_gbl/RULE_LAUNCH_COMPILE.rst | 10 ++
Help/prop_gbl/RULE_LAUNCH_CUSTOM.rst | 10 ++
Help/prop_gbl/RULE_LAUNCH_LINK.rst| 10 ++
3 files changed, 18 insertions(+), 12 deletions(-)
hooks/post-receive
--
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits
Re: [cmake-developers] Modules/GetPrequisites.cmake issues
On 07/30/2015 10:56 AM, Brad King wrote: Thanks! Applied: Those patches exposed a bug in FindMPI, so I fixed that and rebased the other changes on it: FindMPI: Drop unnecessary and incorrect use of GetPrerequisites http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=1c46b6ae GetPrerequisites: Add error checks for execute_process() calls http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=afb674ab GetPrerequisites: Optionally filter objdump output for speed http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=5d0a8b1a -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] Add command line options for deprecation message control
On 08/03/2015 09:43 AM, Domen Vrankar wrote: Since CPack only gets CPACK_* variables from CMake we can't use CMAKE_SUPPRESS_DEVELOPER_ERRORS to revert back to warnings. The mistake is that message() now treats warnings as errors unless explicitly suppressed. While normal CMake runs suppress it by default, script mode and CPack have no such initialization. I've inverted the logic to require the mode to be explicitly enabled: cmake: Do not treat developer warnings as errors by default in scripts http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=975426ce That should fix the test failures. On 08/01/2015 04:03 AM, Stephen Kelly wrote: I still think it's a bit odd that policies and message(DEPRECATED) use a different semantic though (ie, message(DEPRECATED) should issue a warning by default unless -Wno-dev is used). ...or -Wno-deprecated That semantic change may be reasonable but is independent of the command line options change under discussion here. It may require a policy too. -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
[Cmake-commits] CMake branch, next, updated. v3.3.0-1797-g8b0fd7f
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 8b0fd7f79a86971233d8561ed9fc8cc2d6df9372 (commit)
via 975426ceb339cf7a17f57ffba2757bb368669f93 (commit)
from 1e7713c82c352d6f69a4add9614611d4e3b6f0de (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=8b0fd7f79a86971233d8561ed9fc8cc2d6df9372
commit 8b0fd7f79a86971233d8561ed9fc8cc2d6df9372
Merge: 1e7713c 975426c
Author: Brad King brad.k...@kitware.com
AuthorDate: Mon Aug 3 10:21:06 2015 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Mon Aug 3 10:21:06 2015 -0400
Merge topic 'cmake-W-options' into next
975426ce cmake: Do not treat developer warnings as errors by default in
scripts
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=975426ceb339cf7a17f57ffba2757bb368669f93
commit 975426ceb339cf7a17f57ffba2757bb368669f93
Author: Brad King brad.k...@kitware.com
AuthorDate: Mon Aug 3 10:00:42 2015 -0400
Commit: Brad King brad.k...@kitware.com
CommitDate: Mon Aug 3 10:03:27 2015 -0400
cmake: Do not treat developer warnings as errors by default in scripts
The logic in commit c96fe0b4 (cmake: Add -W options to control
deprecation warnings and errors, 2015-07-28) accidentally enables
errors on warnings by default in scripts because there is no
initialization of CMAKE_SUPPRESS_DEVELOPER_ERRORS to TRUE.
Rename internal CMAKE_SUPPRESS_DEVELOPER_ERRORS cache entry to
CMAKE_ERROR_DEVELOPER_WARNINGS. Fix the logic in the message() command
to treat AUTHOR_WARNING as an error only if the option is explicitly
enabled.
diff --git a/Source/cmMessageCommand.cxx b/Source/cmMessageCommand.cxx
index e09ba75..467555f 100644
--- a/Source/cmMessageCommand.cxx
+++ b/Source/cmMessageCommand.cxx
@@ -43,7 +43,7 @@ bool cmMessageCommand
}
else if (*i == AUTHOR_WARNING)
{
-if (!this-Makefile-IsOn(CMAKE_SUPPRESS_DEVELOPER_ERRORS))
+if (this-Makefile-IsOn(CMAKE_ERROR_DEVELOPER_WARNINGS))
{
fatal = true;
type = cmake::AUTHOR_ERROR;
diff --git a/Source/cmake.cxx b/Source/cmake.cxx
index 6832141..e28f385 100644
--- a/Source/cmake.cxx
+++ b/Source/cmake.cxx
@@ -1289,7 +1289,7 @@ int cmake::Configure()
the author of the CMakeLists.txt files.,
cmState::INTERNAL);
this-CacheManager-
-AddCacheEntry(CMAKE_SUPPRESS_DEVELOPER_ERRORS, TRUE,
+AddCacheEntry(CMAKE_ERROR_DEVELOPER_WARNINGS, FALSE,
Suppress errors that are meant for
the author of the CMakeLists.txt files.,
cmState::INTERNAL);
@@ -1328,7 +1328,7 @@ int cmake::Configure()
else if (warningLevel == ERROR_LEVEL)
{
this-CacheManager-
-AddCacheEntry(CMAKE_SUPPRESS_DEVELOPER_ERRORS, FALSE,
+AddCacheEntry(CMAKE_ERROR_DEVELOPER_WARNINGS, TRUE,
Suppress errors that are meant for
the author of the CMakeLists.txt files.,
cmState::INTERNAL);
@@ -1676,11 +1676,11 @@ int cmake::Run(const std::vectorstd::string args,
bool noconfigure)
}
// don't turn dev warnings into errors by default, if no value has been
- // specified for the flag, enable it
- if (!this-State-GetCacheEntryValue(CMAKE_SUPPRESS_DEVELOPER_ERRORS))
+ // specified for the flag, disable it
+ if (!this-State-GetCacheEntryValue(CMAKE_ERROR_DEVELOPER_WARNINGS))
{
this-CacheManager-
-AddCacheEntry(CMAKE_SUPPRESS_DEVELOPER_ERRORS, TRUE,
+AddCacheEntry(CMAKE_ERROR_DEVELOPER_WARNINGS, FALSE,
Suppress errors that are meant for
the author of the CMakeLists.txt files.,
cmState::INTERNAL);
---
Summary of changes:
Source/cmMessageCommand.cxx |2 +-
Source/cmake.cxx| 10 +-
2 files changed, 6 insertions(+), 6 deletions(-)
hooks/post-receive
--
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits
Re: [CMake] ARGVx inherited by sub-functions?
You could argue bug or feature depending on your point of view. (I'd lean
toward bug, as it is rather unexpected...) However, it has been that way
for quite some time, (ever since function was added?), so it may require a
new policy to fix, since some function calls from inside functions may be
accidentally depending on the current behavior.
D
On Monday, August 3, 2015, Paul Smith p...@mad-scientist.net wrote:
Is this a known thing, or a bug (I'm using cmake 3.1.0):
I create this CMakeLists.txt:
cmake_minimum_required(VERSION 3.1.0)
project(ArgTest)
function(FOO one two)
message(STATUS extra args are ${ARGN})
message(STATUS third arg is ${ARGV2})
endfunction()
function(BAR one)
FOO(${one} TWO)
message(STATUS do something with ${ARGN})
endfunction()
BAR(ONE N1 N2 N3 N4)
Note how I invoke BAR() with 5 arguments, but BAR invokes FOO with only
two arguments. I would expect that the third argument ${ARGV3} would be
empty in function FOO.
However, when I run cmake on this file it shows:
-- extra args are
-- third arg is N2
-- do something with N1;N2;N3;N4
So the ARGN for function FOO is correct (nothing there) but FOO has
inherited the extra ARGVx arguments beyond the first two, that I
passed to function BAR!
That's rather unexpected. Bug or feature?
--
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-developers] cmake-3.3.0-Linux-x86_64.tar.gz on download page is not gzipped
thank you for the good catch and for fixing this! now the download behaves as expected on my Chrome version. thank you again and keep it up! radovan On Mon, Aug 3, 2015 at 8:05 PM Brad King brad.k...@kitware.com wrote: On 07/31/2015 09:54 AM, Nils Gladitz wrote: The HTTP response for cmake-3.3.0.tar.gz does contain: Content-Encoding: x-gzip Thanks for pointing this out. Which I think does tell clients that they should decompress to get the actual content which is declared to be of Content-Type:application/x-gzip; this is I think incorrect unless the HTTP server compresses the .tar.gz once more with gzip before delivery. Our admins have fixed the configuration on the server so that there is no Content-Encoding header for .Z and .gz files anymore. I think that configuration was there by mistake. -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] ninja under windows
I suspect that ninja thinks its on a posix system because you compiled it in cygwin. Try building it in a windows terminal. I routinely use cmake and ninja on windows with the msvc toolchain and it works great but I use msys instead of cygwin. Hopefully that helps you. Frank On 8/3/2015 12:22 PM, Gonzalo Garramuño wrote: I compiled Ninja on cygwin from git. That now works fine it seems. I am trying to compile for msvc. However, when cmake runs, I get: [1/123] Building CXX object 'libACESclip\CMakeFiles\ACESclip.dir\src\ACESclipWriter.cpp.obj'ninja: fatal: unknown deps type 'msvc' $ ninja --version 1.6.0.git Is compiling under the microsoft compiler not an option for ninja files ( I can compile with NMake Makefiles just fine in the same project ). -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
[CMake] ARGVx inherited by sub-functions?
Is this a known thing, or a bug (I'm using cmake 3.1.0):
I create this CMakeLists.txt:
cmake_minimum_required(VERSION 3.1.0)
project(ArgTest)
function(FOO one two)
message(STATUS extra args are ${ARGN})
message(STATUS third arg is ${ARGV2})
endfunction()
function(BAR one)
FOO(${one} TWO)
message(STATUS do something with ${ARGN})
endfunction()
BAR(ONE N1 N2 N3 N4)
Note how I invoke BAR() with 5 arguments, but BAR invokes FOO with only
two arguments. I would expect that the third argument ${ARGV3} would be
empty in function FOO.
However, when I run cmake on this file it shows:
-- extra args are
-- third arg is N2
-- do something with N1;N2;N3;N4
So the ARGN for function FOO is correct (nothing there) but FOO has
inherited the extra ARGVx arguments beyond the first two, that I
passed to function BAR!
That's rather unexpected. Bug or feature?
--
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-developers] [PATCH] Macro generation for relaxed constexpr
Qt 5 provides a macro for this context which expands to either 'const' or
'constexpr' depending on whether cxx_constexpr is available, and another
macro which expands to either 'const' or 'constexpr' depending on whether
cxx_relaxed_constexpr is available.
Thinking of it, since C++14 constexpr does not imply const anymore, so
isn't this macro ambiguous wrt standard c++ ?
On Wed, Jul 8, 2015 at 10:42 PM, Stephen Kelly steve...@gmail.com wrote:
Jean-Michaël Celerier wrote:
I think there should be a test for the different allowed contexts of the
${prefix_arg}_RELAXED_CONSTEXPR and ${prefix_arg}_CONSTEXPR macros. Could
you extend Tests/Module/WriteCompilerDetectionHeader with a test for
that?
For sure, I'll do this asap.
Great, thanks!
Steve.
--
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
--
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-commits] CMake branch, next, updated. v3.3.0-1764-gfde8e00
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 fde8e00e2c7ab16e09b2716b4c661b2c299bac6b (commit) via 9b59c178718b7cf1c007d758f59d603ad2856627 (commit) from 6648c4d2f8a390350e5361f4f7c5d1ee12911fae (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=fde8e00e2c7ab16e09b2716b4c661b2c299bac6b commit fde8e00e2c7ab16e09b2716b4c661b2c299bac6b Merge: 6648c4d 9b59c17 Author: Stephen Kelly steve...@gmail.com AuthorDate: Mon Aug 3 03:13:48 2015 -0400 Commit: CMake Topic Stage kwro...@kitware.com CommitDate: Mon Aug 3 03:13:48 2015 -0400 Merge topic 'use-generator-target' into next 9b59c178 Fix width. http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=9b59c178718b7cf1c007d758f59d603ad2856627 commit 9b59c178718b7cf1c007d758f59d603ad2856627 Author: Stephen Kelly steve...@gmail.com AuthorDate: Mon Aug 3 09:13:16 2015 +0200 Commit: Stephen Kelly steve...@gmail.com CommitDate: Mon Aug 3 09:13:16 2015 +0200 Fix width. diff --git a/Source/cmGeneratorTarget.h b/Source/cmGeneratorTarget.h index 1d7a411..68e7a8a 100644 --- a/Source/cmGeneratorTarget.h +++ b/Source/cmGeneratorTarget.h @@ -332,7 +332,8 @@ private: mutable std::mapstd::string, bool DebugCompatiblePropertiesDone; - std::string GetFullNameInternal(const std::string config, bool implib) const; + std::string GetFullNameInternal(const std::string config, + bool implib) const; void GetFullNameInternal(const std::string config, bool implib, std::string outPrefix, std::string outBase, std::string outSuffix) const; --- Summary of changes: Source/cmGeneratorTarget.h |3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) hooks/post-receive -- CMake ___ Cmake-commits mailing list Cmake-commits@cmake.org http://public.kitware.com/mailman/listinfo/cmake-commits
[cmake-developers] [CMake 0015676]: The red message INSTALL TARGETS - target Xxx has RESOURCE files but no RESOURCE DESTINATION. is misleading on Apple platforms.
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=15676
==
Reported By:Adn
Assigned To:
==
Project:CMake
Issue ID: 15676
Category: CMake
Reproducibility:always
Severity: minor
Priority: normal
Status: new
==
Date Submitted: 2015-08-03 05:33 EDT
Last Modified: 2015-08-03 05:33 EDT
==
Summary:The red message INSTALL TARGETS - target Xxx has
RESOURCE files but no RESOURCE DESTINATION. is misleading on Apple platforms.
Description:
When building an OS X application, the resource files are listed in the RESOURCE
target property. Following INSTALL(...) documentation
(http://www.cmake.org/cmake/help/v3.3/command/install.html?highlight=install#installing-targets):
The PRIVATE_HEADER, PUBLIC_HEADER, and RESOURCE arguments cause subsequent
properties to be applied to installing a FRAMEWORK shared library target’s
associated files on non-Apple platforms.
Rules defined by these arguments are ignored on Apple platforms because the
associated files are installed into the appropriate locations inside the
framework folder.
From the documentation, one would understand that there is no point in giving a
RESOURCE argument to INSTALL command when targeting Apple platforms: the
argument is ignored, and the resource are copied inside the bundle (the second
statement here being actually true). Yet, if this argument is omitted, a red
message is emitted in the GUI, which seems confusing with regard to the
documentation statement.
Also, if one decides to provide this argument with a dummy location to turn off
the message, the install target will actually copy the RESOURCE files to the
dummy location (So the argument is not ignored: the resources are still copied
in the bundle, but they are also copied in the provided location).
Steps to Reproduce:
##
## This is the skeleton of a CMakeLists.txt that would trigger the red message
when generated on Apple
##
# populate ${${PROJECT_NAME}_RESOURCES} variable with a .xib file and images
add_executable(${PROJECT_NAME} MACOSX_BUNDLE
${${PROJECT_NAME}_HEADERS}
${${PROJECT_NAME}_SOURCES}
${${PROJECT_NAME}_RESOURCES}
main.mm
)
set_target_properties(${PROJECT_NAME} PROPERTIES
VERSION ${VERSION}
SOVERSION ${SOVERSION}
RESOURCE ${${PROJECT_NAME}_RESOURCES}
)
install(TARGETS ${PROJECT_NAME}
BUNDLE DESTINATION ${RUNTIME_OUTPUT_DIRECTORY}
)
Additional Information:
There is a stack overflow question on this topic:
http://stackoverflow.com/q/31723271/1027706
==
Issue History
Date ModifiedUsername FieldChange
==
2015-08-03 05:33 AdnNew 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
[CMake] ZERO_CHECK hangs for a MS Visual Studio 2010 project on Windows7
Hello, I have a piece of C++ and Fortran software that I'm porting to the CMake build system. On my TeamCity continuous integration server I observe a weird behaviour: whenever I modify a CMakeLists.txt in a way that might mean ZERO_CHECK has something to update, building the ZERO_CHECK hangs until it gets killed off by the CI server job scheduler some 6 hours later. The project in question is definitely not big enough to make 6h of ZERO_CHECK sound reasonable. Besides, when I restart the build job after it gets killed, the second build works ok: it completes ZERO_CHECK promptly, and carries on with its regular job of compiling, linking etc.etc. Log sample: [13:23:52][Step 4/4] [13:23:52][Step 4/4] Microsoft (R) Visual Studio Version 10.0.40219.1. [13:23:52][Step 4/4] Copyright (C) Microsoft Corp. All rights reserved. [13:23:52][Step 4/4] 1-- Build started: Project: ZERO_CHECK, Configuration: RelWithDebInfo x64 -- [13:23:56][Step 4/4] 1Build started 31.07.2015 13:23:54. (it looks the same way even when I enable detailed logging in MSBuild) This behavior seems to be 100% reproducible, and doing any trivial `echo #FOO! CMakeLists.txt` dummy commit is enough to trigger it. The same behavior seems to happen both when I run the build directly from devenv.com and via IncrediBuild distributed build thingy. Has any of you seen a ZERO_CHECK build that hangs in VisualStudio 2010? Any ideas about how and why it might happen? Is there any way to see some verbose logs of what was it that the ZERO_CHECK build wanted to accomplish when it hanged? I tried looking around with procmon, but I'm not very proficient with this tool, and didn't see anything obvious. Hoping to hear from you soon, -- Tadeusz Andrzej Kadłubowski -- 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, next, updated. v3.3.0-1779-g1f652e5
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 1f652e5949b2309bfc1bd102d21092117ff069b0 (commit)
via 77abc4d7ff48dfae64a698c3627d43d08c8dccdd (commit)
via 3513808281430af404f390d881b6a9b5447d960f (commit)
via e341befa19cbd538ea804dc519caa10930ef7dad (commit)
via da967933e0e81bc065ccb53a7a4ab69302f42371 (commit)
via 4fbbae36ecfc5f281256da93e02539b88fe92d15 (commit)
via a324ef1b3f9041eea32fa45991896c8dec0c8541 (commit)
via 2c76fc32078d21454c0cb4d4ddf0c771adad9e0a (commit)
via 5c5ab106dd68ebd3105a877c325b94892504a0a2 (commit)
via b952bb3f9be968de54032135237c67bbc0dd0a70 (commit)
via 6daea501377f8347c5b081f03fdd22cfdb76f538 (commit)
via 798a5ac620ee63abc5d61b6db6f65db1b34a3605 (commit)
via 05a79e3349482f58ccd70f87ac7b852d451b1abd (commit)
via 8fcae6727a7355bf01a77250f2c5fe0df8fda82a (commit)
via a12e80dd27edd9499f1a252549254866b2dcb827 (commit)
from fde8e00e2c7ab16e09b2716b4c661b2c299bac6b (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=1f652e5949b2309bfc1bd102d21092117ff069b0
commit 1f652e5949b2309bfc1bd102d21092117ff069b0
Merge: fde8e00 77abc4d
Author: Stephen Kelly steve...@gmail.com
AuthorDate: Mon Aug 3 03:17:53 2015 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Mon Aug 3 03:17:53 2015 -0400
Merge topic 'use-generator-target' into next
77abc4d7 cmOrderDirectories: Port to cmGeneratorTarget.
35138082 cmMakefile: Remove unused method.
e341befa cmGlobalGenerator: Base exclusion computation on cmGeneratorTarget.
da967933 cmGeneratorTarget: Move CompileInfoMap from cmTarget.
4fbbae36 cmGeneratorTarget: Move GetCompilePDBDirectory from cmTarget.
a324ef1b cmGeneratorTarget: Move GetOutputName from cmTarget.
2c76fc32 cmComputeLinkDepends: Port to cmGeneratorTarget.
5c5ab106 cmComputeLinkInformation: Port to cmGeneratorTarget.
b952bb3f cmGeneratorTarget: Move IsBundleOnApple from cmTarget.
6daea501 cmMakefileTargetGenerator: Add accessor for GeneratorTarget.
798a5ac6 cmGeneratorTarget: Move GetLinkClosure from cmTarget.
05a79e33 cmGeneratorTarget: Move GetLinkerLanguage from cmTarget.
8fcae672 cmGeneratorTarget: Move GetFrameworkDirectory from cmTarget.
a12e80dd cmGeneratorTarget: Move GetFullNameInternal from cmTarget.
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=77abc4d7ff48dfae64a698c3627d43d08c8dccdd
commit 77abc4d7ff48dfae64a698c3627d43d08c8dccdd
Author: Stephen Kelly steve...@gmail.com
AuthorDate: Sat Aug 1 09:48:04 2015 +0200
Commit: Stephen Kelly steve...@gmail.com
CommitDate: Mon Aug 3 09:14:17 2015 +0200
cmOrderDirectories: Port to cmGeneratorTarget.
diff --git a/Source/cmComputeLinkInformation.cxx
b/Source/cmComputeLinkInformation.cxx
index 5cd0d54..e0c6e86 100644
--- a/Source/cmComputeLinkInformation.cxx
+++ b/Source/cmComputeLinkInformation.cxx
@@ -260,10 +260,10 @@ cmComputeLinkInformation
// Allocate internals.
this-OrderLinkerSearchPath =
-new cmOrderDirectories(this-GlobalGenerator, target-Target,
+new cmOrderDirectories(this-GlobalGenerator, target,
linker search path);
this-OrderRuntimeSearchPath =
-new cmOrderDirectories(this-GlobalGenerator, target-Target,
+new cmOrderDirectories(this-GlobalGenerator, target,
runtime search path);
this-OrderDependentRPath = 0;
@@ -370,7 +370,7 @@ cmComputeLinkInformation
{
this-SharedDependencyMode = SharedDepModeDir;
this-OrderDependentRPath =
- new cmOrderDirectories(this-GlobalGenerator, target-Target,
+ new cmOrderDirectories(this-GlobalGenerator, target,
dependent library path);
}
diff --git a/Source/cmOrderDirectories.cxx b/Source/cmOrderDirectories.cxx
index a612437..35ee127 100644
--- a/Source/cmOrderDirectories.cxx
+++ b/Source/cmOrderDirectories.cxx
@@ -280,7 +280,7 @@ bool
cmOrderDirectoriesConstraintLibrary::FindConflict(std::string const dir)
//
cmOrderDirectories::cmOrderDirectories(cmGlobalGenerator* gg,
- cmTarget const* target,
+ const cmGeneratorTarget* target,
const char* purpose)
{
this-GlobalGenerator = gg;
@@ -554,7 +554,8 @@ void cmOrderDirectories::FindImplicitConflicts()
text
Some of these libraries may not be found correctly.;
Re: [cmake-developers] Modules/GetPrequisites.cmake issues
On 03/08/2015 15:22, Brad King wrote: Hi Brad, On 07/30/2015 10:56 AM, Brad King wrote: Thanks! Applied: Those patches exposed a bug in FindMPI, so I fixed that and rebased the other changes on it: Glad my patch flushed out an unrelated defect. OTOH there are many other uses of execute_process() in the Modules that look like they might be suspect through not checking if the process returned a success status. It's not a blanket change as some do seem to be failsafe by checking for error output. Even a very simple command might fail unexpectedly due to access rights or similar. FindMPI: Drop unnecessary and incorrect use of GetPrerequisites http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=1c46b6ae GetPrerequisites: Add error checks for execute_process() calls http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=afb674ab GetPrerequisites: Optionally filter objdump output for speed http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=5d0a8b1a -Brad Regards Bill Somerville. -- 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] Add command line options for deprecation message control
Brad King wrote: On 08/01/2015 04:03 AM, Stephen Kelly wrote: I still think it's a bit odd that policies and message(DEPRECATED) use a different semantic though (ie, message(DEPRECATED) should issue a warning by default unless -Wno-dev is used). ...or -Wno-deprecated That semantic change may be reasonable but is independent of the command line options change under discussion here. It may require a policy too. I filed a bug to track this: http://www.cmake.org/Bug/view.php?id=15677 Thanks, Steve. -- 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-commits] CMake branch, next, updated. v3.3.0-1806-g1341adc
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 1341adc5d45a5273c1e36904a2957e151fdaa1c9 (commit)
via 8f8d824d2b7c8ed4ff911e223141a45eebb5569e (commit)
via 244e93644116719d208a7e55606ba267225e362f (commit)
via 7e49926499c76e427441eed29277c176eb779194 (commit)
from e540a5464bda433d5850908065e73261b9c4fea1 (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=1341adc5d45a5273c1e36904a2957e151fdaa1c9
commit 1341adc5d45a5273c1e36904a2957e151fdaa1c9
Merge: e540a54 8f8d824
Author: Brad King brad.k...@kitware.com
AuthorDate: Mon Aug 3 15:10:48 2015 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Mon Aug 3 15:10:48 2015 -0400
Merge topic 'java-updates' into next
8f8d824d UseJava: Teach install_jar new DESTINATION and COMPONENT options
244e9364 UseJava: Teach add_jar to support file syntax for sources
7e499264 FindJava: Add support for idlj and jarsigner tools
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=8f8d824d2b7c8ed4ff911e223141a45eebb5569e
commit 8f8d824d2b7c8ed4ff911e223141a45eebb5569e
Author: Marc Chevrier marc.chevr...@sap.com
AuthorDate: Thu Jul 30 11:19:24 2015 +0200
Commit: Brad King brad.k...@kitware.com
CommitDate: Mon Aug 3 14:59:44 2015 -0400
UseJava: Teach install_jar new DESTINATION and COMPONENT options
diff --git a/Help/release/dev/java-updates.rst
b/Help/release/dev/java-updates.rst
index 2e5e184..b777807 100644
--- a/Help/release/dev/java-updates.rst
+++ b/Help/release/dev/java-updates.rst
@@ -7,3 +7,7 @@ java-updates
* The :module:`UseJava` module ``add_jar`` function learned
to support response files (e.g. ``@srcs.txt``) for source
specification.
+
+* The :module:`UseJava` module ``install_jar`` function learned
+ new ``DESTINATION`` and ``COMPONENT`` options to specify
+ the corresponding :command:`install` command options.
diff --git a/Modules/UseJava.cmake b/Modules/UseJava.cmake
index 0add8d2..c61591d 100644
--- a/Modules/UseJava.cmake
+++ b/Modules/UseJava.cmake
@@ -211,14 +211,16 @@
#
# ::
#
-# install_jar(TARGET_NAME DESTINATION)
+# install_jar(target_name destination)
+# install_jar(target_name DESTINATION destination [COMPONENT component])
#
# This command installs the TARGET_NAME files to the given DESTINATION.
# It should be called in the same scope as add_jar() or it will fail.
#
# ::
#
-# install_jni_symlink(TARGET_NAME DESTINATION)
+# install_jni_symlink(target_name destination)
+# install_jni_symlink(target_name DESTINATION destination [COMPONENT
component])
#
# This command installs the TARGET_NAME JNI symlinks to the given
# DESTINATION. It should be called in the same scope as add_jar() or it
@@ -629,7 +631,26 @@ function(add_jar _TARGET_NAME)
endfunction()
-function(INSTALL_JAR _TARGET_NAME _DESTINATION)
+function(INSTALL_JAR _TARGET_NAME)
+if (ARGC EQUAL 2)
+ set (_DESTINATION ${ARGV1})
+else()
+ cmake_parse_arguments(_install_jar
+
+DESTINATION;COMPONENT
+
+${ARGN})
+ if (_install_jar_DESTINATION)
+set (_DESTINATION ${_install_jar_DESTINATION})
+ else()
+message(SEND_ERROR install_jar: ${_TARGET_NAME}: DESTINATION must be
specified.)
+ endif()
+
+ if (_install_jar_COMPONENT)
+set (_COMPONENT COMPONENT ${_install_jar_COMPONENT})
+ endif()
+endif()
+
get_property(__FILES
TARGET
${_TARGET_NAME}
@@ -643,13 +664,33 @@ function(INSTALL_JAR _TARGET_NAME _DESTINATION)
${__FILES}
DESTINATION
${_DESTINATION}
+${_COMPONENT}
)
else ()
-message(SEND_ERROR The target ${_TARGET_NAME} is not known in this
scope.)
+message(SEND_ERROR install_jar: The target ${_TARGET_NAME} is not
known in this scope.)
endif ()
endfunction()
-function(INSTALL_JNI_SYMLINK _TARGET_NAME _DESTINATION)
+function(INSTALL_JNI_SYMLINK _TARGET_NAME)
+if (ARGC EQUAL 2)
+ set (_DESTINATION ${ARGV1})
+else()
+ cmake_parse_arguments(_install_jni_symlink
+
+DESTINATION;COMPONENT
+
+${ARGN})
+ if (_install_jni_symlink_DESTINATION)
+set (_DESTINATION ${_install_jni_symlink_DESTINATION})
+ else()
+message(SEND_ERROR install_jni_symlink: ${_TARGET_NAME}: DESTINATION
must be specified.)
+ endif()
+
+ if (_install_jni_symlink_COMPONENT)
+set (_COMPONENT COMPONENT ${_install_jni_symlink_COMPONENT})
+ endif()
+endif()
+
get_property(__SYMLINK
TARGET
Re: [cmake-developers] [PATCH] Macro generation for relaxed constexpr
Jean-Michaël Celerier wrote: Qt 5 provides a macro for this context which expands to either 'const' or 'constexpr' depending on whether cxx_constexpr is available, and another macro which expands to either 'const' or 'constexpr' depending on whether cxx_relaxed_constexpr is available. Thinking of it, since C++14 constexpr does not imply const anymore, so isn't this macro ambiguous wrt standard c++ ? The 'const' keyword can be used in multiple contexts. Can you clarify which you mean with a reference to some document? Thanks, Steve. -- 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] cmake-3.3.0-Linux-x86_64.tar.gz on download page is not gzipped
On 07/31/2015 09:54 AM, Nils Gladitz wrote: The HTTP response for cmake-3.3.0.tar.gz does contain: Content-Encoding: x-gzip Thanks for pointing this out. Which I think does tell clients that they should decompress to get the actual content which is declared to be of Content-Type:application/x-gzip; this is I think incorrect unless the HTTP server compresses the .tar.gz once more with gzip before delivery. Our admins have fixed the configuration on the server so that there is no Content-Encoding header for .Z and .gz files anymore. I think that configuration was there by mistake. -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
[cmake-developers] [CMake 0015677]: Issue deprecation warnings by default.
The following issue has been SUBMITTED. == http://www.cmake.org/Bug/view.php?id=15677 == Reported By:Stephen Kelly Assigned To: == Project:CMake Issue ID: 15677 Category: CMake Reproducibility:have not tried Severity: minor Priority: normal Status: new == Date Submitted: 2015-08-03 19:19 CEST Last Modified: 2015-08-03 19:19 CEST == Summary:Issue deprecation warnings by default. Description: message(DEPRECATED) does not issue any warning unless the user adds additional command line flags. Policy warnings are issued by default until the user uses command line flags. message(DEPRECATED) should likely be changed to issue the message by default. http://thread.gmane.org/gmane.comp.programming.tools.cmake.devel/13798/focus=13878 == Issue History Date ModifiedUsername FieldChange == 2015-08-03 19:19 Stephen Kelly New 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
[CMake] ninja under windows
I compiled Ninja on cygwin from git. That now works fine it seems. I am trying to compile for msvc. However, when cmake runs, I get: [1/123] Building CXX object 'libACESclip\CMakeFiles\ACESclip.dir\src\ACESclipWriter.cpp.obj'ninja: fatal: unknown deps type 'msvc' $ ninja --version 1.6.0.git Is compiling under the microsoft compiler not an option for ninja files ( I can compile with NMake Makefiles just fine in the same project ). -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
[Cmake-commits] CMake branch, master, updated. v3.3.0-671-g25ec835
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 25ec835571741d5339fb653e06e79896d72f8e8a (commit) via d4736d53cd61f2cbbb36bec682663b74b01dddce (commit) from db519cae57122dc6584226aac951674b49301efc (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=25ec835571741d5339fb653e06e79896d72f8e8a commit 25ec835571741d5339fb653e06e79896d72f8e8a Merge: db519ca d4736d5 Author: Brad King brad.k...@kitware.com AuthorDate: Mon Aug 3 09:11:30 2015 -0400 Commit: CMake Topic Stage kwro...@kitware.com CommitDate: Mon Aug 3 09:11:30 2015 -0400 Merge topic 'fix-windows-version-detection' d4736d53 Windows: Fix CMAKE_HOST_SYSTEM_VERSION on Windows = 8.1 (#15674) --- Summary of changes: Source/cmGlobalGenerator.cxx | 56 ++ 1 file changed, 46 insertions(+), 10 deletions(-) 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.3.0-676-g94d53d1
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 94d53d1664b1e792e800cfd206e8e81ff625 (commit) via 5d0a8b1abc3f8a6d8d23772251b4ef2758d2def6 (commit) via afb674ab46a7d6ff3d1801315f3d852bdba79d0c (commit) from 6508cc5355d74a148e9a8d7feca99d60b9748168 (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=94d53d1664b1e792e800cfd206e8e81ff625 commit 94d53d1664b1e792e800cfd206e8e81ff625 Merge: 6508cc5 5d0a8b1 Author: Brad King brad.k...@kitware.com AuthorDate: Mon Aug 3 09:11:34 2015 -0400 Commit: CMake Topic Stage kwro...@kitware.com CommitDate: Mon Aug 3 09:11:34 2015 -0400 Merge topic 'GetPrerequisites-updates' 5d0a8b1a GetPrerequisites: Optionally filter objdump output for speed afb674ab GetPrerequisites: Add error checks for execute_process() calls --- Summary of changes: Modules/GetPrerequisites.cmake | 38 ++ 1 file changed, 38 insertions(+) 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.3.0-669-gdb519ca
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 db519cae57122dc6584226aac951674b49301efc (commit) via f7a9ed7e90cd2661b279d0bcd44d43620b8eeda1 (commit) from 5c02ae4ac9dec3a275d3965ccdcfdb564686dc79 (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=db519cae57122dc6584226aac951674b49301efc commit db519cae57122dc6584226aac951674b49301efc Merge: 5c02ae4 f7a9ed7 Author: Brad King brad.k...@kitware.com AuthorDate: Mon Aug 3 09:11:28 2015 -0400 Commit: CMake Topic Stage kwro...@kitware.com CommitDate: Mon Aug 3 09:11:28 2015 -0400 Merge topic 'fix-xcode-quoting' f7a9ed7e Xcode: Quote strings containing a tilde (#15672) --- Summary of changes: Source/cmXCodeObject.cxx |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.3.0-673-g6508cc5
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 6508cc5355d74a148e9a8d7feca99d60b9748168 (commit) via 1c46b6aed0db88c97189713f291164f98df780a9 (commit) from 25ec835571741d5339fb653e06e79896d72f8e8a (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=6508cc5355d74a148e9a8d7feca99d60b9748168 commit 6508cc5355d74a148e9a8d7feca99d60b9748168 Merge: 25ec835 1c46b6a Author: Brad King brad.k...@kitware.com AuthorDate: Mon Aug 3 09:11:32 2015 -0400 Commit: CMake Topic Stage kwro...@kitware.com CommitDate: Mon Aug 3 09:11:32 2015 -0400 Merge topic 'FindMPI-drop-GetPrerequisites' 1c46b6ae FindMPI: Drop unnecessary and incorrect use of GetPrerequisites --- Summary of changes: Modules/FindMPI.cmake |8 +++- 1 file changed, 3 insertions(+), 5 deletions(-) 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.3.0-667-g5c02ae4
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 5c02ae4ac9dec3a275d3965ccdcfdb564686dc79 (commit) via da98b89612d59906bd938d58a9072b3ce68864de (commit) via 129640f279259e51fbb0e81a5bec2ec2dfac543e (commit) via d0915bc86f294707411ae525e70fa20965f1aeec (commit) via 1feafc643b1c50fd0fa8171a4170065ca39d4d4c (commit) from ebacce3f0b0cef6116e91d408d591ff67285c420 (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=5c02ae4ac9dec3a275d3965ccdcfdb564686dc79 commit 5c02ae4ac9dec3a275d3965ccdcfdb564686dc79 Merge: ebacce3 da98b89 Author: Brad King brad.k...@kitware.com AuthorDate: Mon Aug 3 09:11:25 2015 -0400 Commit: CMake Topic Stage kwro...@kitware.com CommitDate: Mon Aug 3 09:11:25 2015 -0400 Merge topic 'update-kwsys' da98b896 Tests: In CTestTest2 skip the kwsys.testProcess-10 test that leaks 129640f2 CTestCustom: Ignore kwsys.testProcess-10 for MemCheck as KWSys does d0915bc8 Merge branch 'upstream-kwsys' into update-kwsys 1feafc64 KWSys 2015-07-30 (f63febb7) --- Summary of changes: CTestCustom.cmake.in |4 + Source/kwsys/CMakeLists.txt |6 +- Source/kwsys/CTestCustom.cmake.in | 15 ++ Source/kwsys/Process.h.in | 131 ++- Source/kwsys/ProcessUNIX.c| 357 Source/kwsys/ProcessWin32.c | 462 - Source/kwsys/testProcess.c| 267 + Tests/CTestTest2/test.cmake.in| 13 +- 8 files changed, 1051 insertions(+), 204 deletions(-) create mode 100644 Source/kwsys/CTestCustom.cmake.in 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.3.0-1781-gbbfd6cb
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 bbfd6cbd9f339015c1cefa27773953f69b6d3c68 (commit) via 632cb7761c2b69224dda45151ff7ff9bf3ebbce8 (commit) from 1f652e5949b2309bfc1bd102d21092117ff069b0 (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=bbfd6cbd9f339015c1cefa27773953f69b6d3c68 commit bbfd6cbd9f339015c1cefa27773953f69b6d3c68 Merge: 1f652e5 632cb77 Author: Brad King brad.k...@kitware.com AuthorDate: Mon Aug 3 09:13:16 2015 -0400 Commit: CMake Topic Stage kwro...@kitware.com CommitDate: Mon Aug 3 09:13:16 2015 -0400 Merge topic 'cpack-rpm-documentation-fixes' into next 632cb776 Revert topic 'cpack-rpm-documentation-fixes' http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=632cb7761c2b69224dda45151ff7ff9bf3ebbce8 commit 632cb7761c2b69224dda45151ff7ff9bf3ebbce8 Author: Brad King brad.k...@kitware.com AuthorDate: Mon Aug 3 09:12:57 2015 -0400 Commit: Brad King brad.k...@kitware.com CommitDate: Mon Aug 3 09:12:57 2015 -0400 Revert topic 'cpack-rpm-documentation-fixes' It will be restored once unrelated errors in its tests are fixed. diff --git a/Modules/CPackRPM.cmake b/Modules/CPackRPM.cmake index 7c1db14..cb77fb8 100644 --- a/Modules/CPackRPM.cmake +++ b/Modules/CPackRPM.cmake @@ -95,7 +95,6 @@ # * Default : CPACK_PACKAGE_VENDOR if set or unknown # # .. variable:: CPACK_RPM_PACKAGE_URL -# CPACK_RPM_component_PACKAGE_URL # # The projects URL. # @@ -124,55 +123,7 @@ # compression whereas older cannot use such RPM. Using this one can enforce # compression type to be used. Possible value are: lzma, xz, bzip2 and gzip. # -# .. variable:: CPACK_RPM_PACKAGE_AUTOREQ -# CPACK_RPM_component_PACKAGE_AUTOREQ -# -# RPM spec autoreq field. -# -# * Mandatory : NO -# * Default : - -# -# May be used to enable (1, yes) or disable (0, no) automatic shared libraries -# dependency detection. Dependencies are added to requires list. -# -# .. note:: -# -#By defalut automatic dependency detection is enabled by rpm generator. -# -# .. variable:: CPACK_RPM_PACKAGE_AUTOPROV -# CPACK_RPM_component_PACKAGE_AUTOPROV -# -# RPM spec autoprov field. -# -# * Mandatory : NO -# * Default : - -# -# May be used to enable (1, yes) or disable (0, no) automatic listing of shared -# libraries that are provided by the package. Shared libraries are added to -# provides list. -# -# .. note:: -# -#By defalut automatic provides detection is enabled by rpm generator. -# -# .. variable:: CPACK_RPM_PACKAGE_AUTOREQPROV -# CPACK_RPM_component_PACKAGE_AUTOREQPROV -# -# RPM spec autoreqprov field. -# -# * Mandatory : NO -# * Default : - -# -# Variable enables/disables autoreq and autoprov at the same time. -# See :variable:`CPACK_RPM_PACKAGE_AUTOREQ` and :variable:`CPACK_RPM_PACKAGE_AUTOPROV` -# for more details. -# -# .. note:: -# -#By defalut automatic detection feature is enabled by rpm. -# # .. variable:: CPACK_RPM_PACKAGE_REQUIRES -# CPACK_RPM_component_PACKAGE_REQUIRES # # RPM spec requires field. # @@ -188,25 +139,7 @@ # # rpm -qp --requires file.rpm # -# .. variable:: CPACK_RPM_PACKAGE_CONFLICTS -# CPACK_RPM_component_PACKAGE_CONFLICTS -# -# RPM spec conflicts field. -# -# * Mandatory : NO -# * Default : - -# -# May be used to set negative RPM dependencies (conflicts). Note that you must enclose -# the complete requires string between quotes, for example:: -# -# set(CPACK_RPM_PACKAGE_CONFLICTS libxml2) -# -# The conflicting package list of an RPM file could be printed with:: -# -# rpm -qp --conflicts file.rpm -# # .. variable:: CPACK_RPM_PACKAGE_REQUIRES_PRE -# CPACK_RPM_component_PACKAGE_REQUIRES_PRE # # RPM spec requires(pre) field. # @@ -219,7 +152,6 @@ # set(CPACK_RPM_PACKAGE_REQUIRES_PRE shadow-utils, initscripts) # # .. variable:: CPACK_RPM_PACKAGE_REQUIRES_POST -# CPACK_RPM_component_PACKAGE_REQUIRES_POST # # RPM spec requires(post) field. # @@ -233,7 +165,6 @@ # # # .. variable:: CPACK_RPM_PACKAGE_REQUIRES_POSTUN -# CPACK_RPM_component_PACKAGE_REQUIRES_POSTUN # # RPM spec requires(postun) field. # @@ -247,7 +178,6 @@ # # # .. variable:: CPACK_RPM_PACKAGE_REQUIRES_PREUN -# CPACK_RPM_component_PACKAGE_REQUIRES_PREUN # # RPM spec requires(preun) field. # @@ -260,7 +190,6 @@ # set(CPACK_RPM_PACKAGE_REQUIRES_PREUN shadow-utils, initscripts) # # .. variable:: CPACK_RPM_PACKAGE_SUGGESTS -# CPACK_RPM_component_PACKAGE_SUGGESTS
[Cmake-commits] CMake branch, next, updated. v3.3.0-1790-gcb7e276
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 cb7e276d6a39ebf79ddb060532f7c11066784a5b (commit) via 302edf850e34b008b921e40e756b81d9fde5d1ad (commit) via 94d53d1664b1e792e800cfd206e8e81ff625 (commit) via 6508cc5355d74a148e9a8d7feca99d60b9748168 (commit) via 25ec835571741d5339fb653e06e79896d72f8e8a (commit) via db519cae57122dc6584226aac951674b49301efc (commit) via 5c02ae4ac9dec3a275d3965ccdcfdb564686dc79 (commit) via ebacce3f0b0cef6116e91d408d591ff67285c420 (commit) via 614786cc5c8cf6f504112a722aabf8dddc154d2c (commit) from bbfd6cbd9f339015c1cefa27773953f69b6d3c68 (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=cb7e276d6a39ebf79ddb060532f7c11066784a5b commit cb7e276d6a39ebf79ddb060532f7c11066784a5b Merge: 302edf8 94d53d1 Author: Brad King brad.k...@kitware.com AuthorDate: Mon Aug 3 09:16:41 2015 -0400 Commit: Brad King brad.k...@kitware.com CommitDate: Mon Aug 3 09:16:41 2015 -0400 Merge branch 'master' into next http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=302edf850e34b008b921e40e756b81d9fde5d1ad commit 302edf850e34b008b921e40e756b81d9fde5d1ad Merge: bbfd6cb ebacce3 Author: Brad King brad.k...@kitware.com AuthorDate: Mon Aug 3 09:16:35 2015 -0400 Commit: Brad King brad.k...@kitware.com CommitDate: Mon Aug 3 09:16:35 2015 -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, next, updated. v3.3.0-1795-g1e7713c
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 1e7713c82c352d6f69a4add9614611d4e3b6f0de (commit) via 7ac2b1256b09044b86c6bd926cc239133beab088 (commit) from 2b5ca8ec591cb9e7c3f7415c022662293773ebda (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=1e7713c82c352d6f69a4add9614611d4e3b6f0de commit 1e7713c82c352d6f69a4add9614611d4e3b6f0de Merge: 2b5ca8e 7ac2b12 Author: Brad King brad.k...@kitware.com AuthorDate: Mon Aug 3 09:25:21 2015 -0400 Commit: Brad King brad.k...@kitware.com CommitDate: Mon Aug 3 09:25:21 2015 -0400 Merge branch 'master' into next --- Summary of changes: 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.3.0-679-g7ac2b12
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 7ac2b1256b09044b86c6bd926cc239133beab088 (commit)
via 14e49ed15615e7f2bcb58aa4540683250006f5c7 (commit)
via 623dcc85a447b9ce0f09cffa8cd296cd8a51ad9d (commit)
from 94d53d1664b1e792e800cfd206e8e81ff625 (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=7ac2b1256b09044b86c6bd926cc239133beab088
commit 7ac2b1256b09044b86c6bd926cc239133beab088
Merge: 94d53d1 14e49ed
Author: Brad King brad.k...@kitware.com
AuthorDate: Mon Aug 3 09:25:10 2015 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Mon Aug 3 09:25:10 2015 -0400
Merge topic 'if-test'
14e49ed1 if: Add TEST test condition
623dcc85 ExternalProject: Avoid if() auto-dereference of a TEST variable
---
Summary of changes:
Help/command/if.rst|4 +++
Help/manual/cmake-policies.7.rst |1 +
Help/policy/CMP0064.rst| 17 +
Help/release/dev/if-TEST.rst |5
Modules/ExternalProject.cmake |6 ++---
Source/cmConditionEvaluator.cxx| 26 +++-
Source/cmConditionEvaluator.h |1 +
Source/cmPolicies.h|3 +++
Tests/RunCMake/CMP0064/CMP0064-NEW.cmake |5
Tests/RunCMake/CMP0064/CMP0064-OLD.cmake |7 ++
Tests/RunCMake/CMP0064/CMP0064-WARN.cmake |7 ++
.../{CompileDefinitions = CMP0064}/CMakeLists.txt |0
Tests/RunCMake/CMP0064/RunCMakeTest.cmake |5
Tests/RunCMake/CMakeLists.txt |1 +
Tests/RunCMake/if/RunCMakeTest.cmake |3 +++
.../if/TestNameThatDoesNotExist-stdout.txt |1 +
Tests/RunCMake/if/TestNameThatDoesNotExist.cmake |6 +
Tests/RunCMake/if/TestNameThatExists-stdout.txt|1 +
Tests/RunCMake/if/TestNameThatExists.cmake |7 ++
19 files changed, 102 insertions(+), 4 deletions(-)
create mode 100644 Help/policy/CMP0064.rst
create mode 100644 Help/release/dev/if-TEST.rst
create mode 100644 Tests/RunCMake/CMP0064/CMP0064-NEW.cmake
create mode 100644 Tests/RunCMake/CMP0064/CMP0064-OLD.cmake
create mode 100644 Tests/RunCMake/CMP0064/CMP0064-WARN.cmake
copy Tests/RunCMake/{CompileDefinitions = CMP0064}/CMakeLists.txt (100%)
create mode 100644 Tests/RunCMake/CMP0064/RunCMakeTest.cmake
create mode 100644 Tests/RunCMake/if/TestNameThatDoesNotExist-stdout.txt
create mode 100644 Tests/RunCMake/if/TestNameThatDoesNotExist.cmake
create mode 100644 Tests/RunCMake/if/TestNameThatExists-stdout.txt
create mode 100644 Tests/RunCMake/if/TestNameThatExists.cmake
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.3.0-1793-g2b5ca8e
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 2b5ca8ec591cb9e7c3f7415c022662293773ebda (commit)
via 14e49ed15615e7f2bcb58aa4540683250006f5c7 (commit)
via 623dcc85a447b9ce0f09cffa8cd296cd8a51ad9d (commit)
from cb7e276d6a39ebf79ddb060532f7c11066784a5b (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=2b5ca8ec591cb9e7c3f7415c022662293773ebda
commit 2b5ca8ec591cb9e7c3f7415c022662293773ebda
Merge: cb7e276 14e49ed
Author: Brad King brad.k...@kitware.com
AuthorDate: Mon Aug 3 09:25:01 2015 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Mon Aug 3 09:25:01 2015 -0400
Merge topic 'if-test' into next
14e49ed1 if: Add TEST test condition
623dcc85 ExternalProject: Avoid if() auto-dereference of a TEST variable
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=14e49ed15615e7f2bcb58aa4540683250006f5c7
commit 14e49ed15615e7f2bcb58aa4540683250006f5c7
Author: Matt McCormick matt.mccorm...@kitware.com
AuthorDate: Mon Dec 29 20:47:48 2014 -0500
Commit: Brad King brad.k...@kitware.com
CommitDate: Mon Aug 3 09:22:25 2015 -0400
if: Add TEST test condition
if(TEST TestNameThatExists) will return true if a test with the name
TestNameThatExists has been added with add_test. The syntax is similar
to if(TARGET TargetName). Since use of TEST as an argument to if()
could previously be interpreted as a non-keyword argument, add policy
CMP0064 to treat it as a keyword as NEW behavior.
diff --git a/Help/command/if.rst b/Help/command/if.rst
index 396becf..2465bde 100644
--- a/Help/command/if.rst
+++ b/Help/command/if.rst
@@ -71,6 +71,10 @@ Possible expressions are:
created by the :command:`add_executable`, :command:`add_library`, or
:command:`add_custom_target` commands.
+``if(TEST test-name)``
+ True if the given name is an existing test name created by the
+ :command:`add_test` command.
+
``if(EXISTS path-to-file-or-directory)``
True if the named file or directory exists. Behavior is well-defined
only for full paths.
diff --git a/Help/manual/cmake-policies.7.rst b/Help/manual/cmake-policies.7.rst
index 0a313cd..590f10d 100644
--- a/Help/manual/cmake-policies.7.rst
+++ b/Help/manual/cmake-policies.7.rst
@@ -121,3 +121,4 @@ All Policies
/policy/CMP0061
/policy/CMP0062
/policy/CMP0063
+ /policy/CMP0064
diff --git a/Help/policy/CMP0064.rst b/Help/policy/CMP0064.rst
new file mode 100644
index 000..e9a061b
--- /dev/null
+++ b/Help/policy/CMP0064.rst
@@ -0,0 +1,17 @@
+CMP0064
+---
+
+Recognize ``TEST`` as a operator for the :command:`if` command.
+
+The ``TEST`` operator was added to the :command:`if` command to determine if a
+given test name was created by the :command:`add_test` command.
+
+The ``OLD`` behavior for this policy is to ignore the ``TEST`` operator.
+The ``NEW`` behavior is to interpret the ``TEST`` operator.
+
+This policy was introduced in CMake version 3.4. CMake version
+|release| warns when the policy is not set and uses ``OLD`` behavior. Use
+the :command:`cmake_policy()` command to set it to ``OLD`` or ``NEW``
+explicitly.
+
+.. include:: DEPRECATED.txt
diff --git a/Help/release/dev/if-TEST.rst b/Help/release/dev/if-TEST.rst
new file mode 100644
index 000..05bf71c
--- /dev/null
+++ b/Help/release/dev/if-TEST.rst
@@ -0,0 +1,5 @@
+if-TEST
+---
+
+* Add a new TEST operator to if() that evaluates to true
+ if a given test name has been defined.
diff --git a/Source/cmConditionEvaluator.cxx b/Source/cmConditionEvaluator.cxx
index 420bfdf..7874803 100644
--- a/Source/cmConditionEvaluator.cxx
+++ b/Source/cmConditionEvaluator.cxx
@@ -16,7 +16,8 @@ cmConditionEvaluator::cmConditionEvaluator(cmMakefile
makefile):
Makefile(makefile),
Policy12Status(makefile.GetPolicyStatus(cmPolicies::CMP0012)),
Policy54Status(makefile.GetPolicyStatus(cmPolicies::CMP0054)),
- Policy57Status(makefile.GetPolicyStatus(cmPolicies::CMP0057))
+ Policy57Status(makefile.GetPolicyStatus(cmPolicies::CMP0057)),
+ Policy64Status(makefile.GetPolicyStatus(cmPolicies::CMP0064))
{
}
@@ -493,6 +494,29 @@ bool cmConditionEvaluator::HandleLevel1(cmArgumentList
newArgs,
this-Makefile.FindTargetToUse(argP1-GetValue())?true:false,
reducible, arg, newArgs, argP1, argP2);
}
+ // does a test exist
+ if(this-Policy64Status != cmPolicies::OLD
+this-Policy64Status != cmPolicies::WARN)
+{
+if (this-IsKeyword(TEST, *arg) argP1 != newArgs.end())
+ {
+ const cmTest* haveTest = this-Makefile.GetTest(argP1-c_str());
+
Re: [cmake-developers] Add command line options for deprecation message control
The branch seems to make the RunCMake.CPack_RPM test fail on my machine. I have not investigated. Missed this thread... I was talking to Brad about this. Failing test is written exactly for testing author warning message (CPackRPM.cmake:560). RPM packages may be relocatable but if relocation paths don't match with any file paths in package an author warning is output but package is still created. Since CPack only gets CPACK_* variables from CMake we can't use CMAKE_SUPPRESS_DEVELOPER_ERRORS to revert back to warnings. If this is the only location where CPack uses developer messages we could change it to normal info message but implementing this fallback mechanism for CPack (and CTest?) would probably be a more complete solution. Regards, Domen -- 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 0015678]: CMakeCache.txt can't be passed into cmake's -C flag
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=15678
==
Reported By:Chris
Assigned To:
==
Project:CMake
Issue ID: 15678
Category: CMake
Reproducibility:always
Severity: minor
Priority: normal
Status: new
==
Date Submitted: 2015-08-03 17:08 EDT
Last Modified: 2015-08-03 17:08 EDT
==
Summary:CMakeCache.txt can't be passed into cmake's -C flag
Description:
I'm probably trying to be too clever, but I'm trying to setup a cmake build
target for clang to do a bootstrap build where you build clang, then use the
built clang to rebuild clang. I had this genius idea that I could try and pass
through the CMake options used to configure the first clang using the
CMakeCache.txt and the -C flag. It unfortunately doesn't work. I see the
following errors:
[2/5] Performing configure step for 'bootstrap'
FAILED: cd
/Users/cbieneman/dev/open-source/llvm-build-rel/tools/clang/bootstrap/src/bootstrap-build
/Users/cbieneman/dev/open-source/cmake-bins/bin/cmake -C
/Users/cbieneman/dev/open-source/llvm-build-rel/CMakeCache.txt
-DCMAKE_CXX_COMPILER=/Users/cbieneman/dev/open-source/llvm-build-rel/bin/clang++
-DCMAKE_CXX_COMPILER=/Users/cbieneman/dev/open-source/llvm-build-rel/bin/clang
-GSublime Text 2 - Ninja /Users/cbieneman/dev/open-source/llvm
/Users/cbieneman/dev/open-source/cmake-bins/bin/cmake -E touch
/Users/cbieneman/dev/open-source/llvm-build-rel/tools/clang/bootstrap/src/bootstrap-stamp/bootstrap-configure
loading initial cache file
/Users/cbieneman/dev/open-source/llvm-build-rel/CMakeCache.txt
CMake Error: Error in cmake code at
/Users/cbieneman/dev/open-source/llvm-build-rel/CMakeCache.txt:17:
Parse error. Expected a command name, got unquoted argument with text
//Default.
CMake Error: Error processing file:
/Users/cbieneman/dev/open-source/llvm-build-rel/CMakeCache.txt
Steps to Reproduce:
Apply the diffs below to clang, and configure with CMake setting
-DCLANG_ENABLE_BOOTSTRAP=On, and run buildtool bootstrap.
Additional Information:
diff --git a/CMakeLists.txt b/CMakeLists.txt
index ab70f1d..6974b6e 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -96,6 +96,7 @@ if( CMAKE_SOURCE_DIR STREQUAL CMAKE_CURRENT_SOURCE_DIR )
option(LLVM_FORCE_USE_OLD_HOST_TOOLCHAIN
Set to ON to force using an old, unsupported host toolchain. OFF)
+ option(CLANG_ENABLE_BOOTSTRAP Generate the clang bootstrap target OFF)
include(AddLLVM)
include(TableGen)
@@ -551,3 +552,31 @@ if (CLANG_BUILT_STANDALONE)
${CLANG_BINARY_DIR}/share/clang/cmake/ClangConfig.cmake
COPYONLY)
endif ()
+
+if (CLANG_ENABLE_BOOTSTRAP)
+ include(ExternalProject)
+
+ ExternalProject_Add(bootstrap
+DEPENDS clang
+PREFIX bootstrap
+SOURCE_DIR ${CMAKE_SOURCE_DIR}
+CMAKE_ARGS -C ${CMAKE_BINARY_DIR}/CMakeCache.txt
+${CLANG_BOOTSTRAP_CMAKE_ARGS}
+-DCMAKE_CXX_COMPILER=${CMAKE_BINARY_DIR}/bin/clang++
+-DCMAKE_CXX_COMPILER=${CMAKE_BINARY_DIR}/bin/clang
+STEP_TARGETS configure build
+)
+
+ ExternalProject_Add_Step(bootstrap force-reconfigure
+DEPENDERS configure
+ALWAYS 1
+)
+
+ ExternalProject_Add_Step(bootstrap clobber
+COMMAND ${CMAKE_COMMAND} -E remove_directory BINARY_DIR
+COMMAND ${CMAKE_COMMAND} -E make_directory BINARY_DIR
+COMMENT Clobberring compiler-rt build directory...
+DEPENDERS configure
+DEPENDS ${LLVM_RUNTIME_OUTPUT_INTDIR}/bootstrap
+ )
+endif()
==
Issue History
Date ModifiedUsername FieldChange
==
2015-08-03 17:08 Chris New 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:
Re: [cmake-developers] [PATCH] Macro generation for relaxed constexpr
I'm referring to the const used after methods (struct { int f() const; }).
Here is an example : https://ideone.com/C28SMn
Best regards :)
On Mon, Aug 3, 2015 at 7:20 PM, Stephen Kelly steve...@gmail.com wrote:
Jean-Michaël Celerier wrote:
Qt 5 provides a macro for this context which expands to either 'const'
or
'constexpr' depending on whether cxx_constexpr is available, and another
macro which expands to either 'const' or 'constexpr' depending on whether
cxx_relaxed_constexpr is available.
Thinking of it, since C++14 constexpr does not imply const anymore, so
isn't this macro ambiguous wrt standard c++ ?
The 'const' keyword can be used in multiple contexts. Can you clarify which
you mean with a reference to some document?
Thanks,
Steve.
--
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
--
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] Segfault
On 08/02/2015 01:35 PM, Justin Borodinsky wrote:
I received a segfault during generation with the attached list-file.
Attached is a patch to master which avoids the null pointer access
causing it, but there may be a better fix.
Please try this patch instead.
Thanks,
-Brad
From 33d52a96f7f622f96a3c656babe59795f7cabf8f Mon Sep 17 00:00:00 2001
Message-Id: 33d52a96f7f622f96a3c656babe59795f7cabf8f.1438633052.git.brad.k...@kitware.com
From: Brad King brad.k...@kitware.com
Date: Mon, 3 Aug 2015 15:28:41 -0400
Subject: [PATCH] Reject TARGET_PDB_FILE for imported targets instead of
crashing
Reported-by: Justin Borodinsky justin.borodin...@gmail.com
---
Source/cmGeneratorExpressionNode.cxx | 7 +++
Source/cmTarget.cxx | 1 +
.../GeneratorExpression/ImportedTarget-TARGET_PDB_FILE-result.txt | 1 +
.../GeneratorExpression/ImportedTarget-TARGET_PDB_FILE-stderr.txt | 8
.../GeneratorExpression/ImportedTarget-TARGET_PDB_FILE.cmake | 2 ++
Tests/RunCMake/GeneratorExpression/RunCMakeTest.cmake | 1 +
6 files changed, 20 insertions(+)
create mode 100644 Tests/RunCMake/GeneratorExpression/ImportedTarget-TARGET_PDB_FILE-result.txt
create mode 100644 Tests/RunCMake/GeneratorExpression/ImportedTarget-TARGET_PDB_FILE-stderr.txt
create mode 100644 Tests/RunCMake/GeneratorExpression/ImportedTarget-TARGET_PDB_FILE.cmake
diff --git a/Source/cmGeneratorExpressionNode.cxx b/Source/cmGeneratorExpressionNode.cxx
index f3527ff..140e2e4 100644
--- a/Source/cmGeneratorExpressionNode.cxx
+++ b/Source/cmGeneratorExpressionNode.cxx
@@ -1597,6 +1597,13 @@ struct TargetFilesystemArtifactResultCreatorArtifactPdbTag
cmGeneratorExpressionContext *context,
const GeneratorExpressionContent *content)
{
+if (target-IsImported())
+ {
+ ::reportError(context, content-GetOriginalExpression(),
+TARGET_PDB_FILE not allowed for IMPORTED targets.);
+ return std::string();
+ }
+
std::string language = target-Target-GetLinkerLanguage(context-Config);
std::string pdbSupportVar = CMAKE_ + language + _LINKER_SUPPORTS_PDB;
diff --git a/Source/cmTarget.cxx b/Source/cmTarget.cxx
index cf33791..3b43e6f 100644
--- a/Source/cmTarget.cxx
+++ b/Source/cmTarget.cxx
@@ -3356,6 +3356,7 @@ void cmTarget::ComputeLinkClosure(const std::string config,
// Get languages built in this target.
UNORDERED_SETstd::string languages;
LinkImplementation const* impl = this-GetLinkImplementation(config);
+ assert(impl);
for(std::vectorstd::string::const_iterator li = impl-Languages.begin();
li != impl-Languages.end(); ++li)
{
diff --git a/Tests/RunCMake/GeneratorExpression/ImportedTarget-TARGET_PDB_FILE-result.txt b/Tests/RunCMake/GeneratorExpression/ImportedTarget-TARGET_PDB_FILE-result.txt
new file mode 100644
index 000..d00491f
--- /dev/null
+++ b/Tests/RunCMake/GeneratorExpression/ImportedTarget-TARGET_PDB_FILE-result.txt
@@ -0,0 +1 @@
+1
diff --git a/Tests/RunCMake/GeneratorExpression/ImportedTarget-TARGET_PDB_FILE-stderr.txt b/Tests/RunCMake/GeneratorExpression/ImportedTarget-TARGET_PDB_FILE-stderr.txt
new file mode 100644
index 000..d915ecb
--- /dev/null
+++ b/Tests/RunCMake/GeneratorExpression/ImportedTarget-TARGET_PDB_FILE-stderr.txt
@@ -0,0 +1,8 @@
+CMake Error at ImportedTarget-TARGET_PDB_FILE.cmake:2 \(add_custom_target\):
+ Error evaluating generator expression:
+
+\$TARGET_PDB_FILE:empty
+
+ TARGET_PDB_FILE not allowed for IMPORTED targets.
+Call Stack \(most recent call first\):
+ CMakeLists.txt:3 \(include\)
diff --git a/Tests/RunCMake/GeneratorExpression/ImportedTarget-TARGET_PDB_FILE.cmake b/Tests/RunCMake/GeneratorExpression/ImportedTarget-TARGET_PDB_FILE.cmake
new file mode 100644
index 000..c55c5d5
--- /dev/null
+++ b/Tests/RunCMake/GeneratorExpression/ImportedTarget-TARGET_PDB_FILE.cmake
@@ -0,0 +1,2 @@
+add_library(empty UNKNOWN IMPORTED)
+add_custom_target(custom COMMAND echo $TARGET_PDB_FILE:empty)
diff --git a/Tests/RunCMake/GeneratorExpression/RunCMakeTest.cmake b/Tests/RunCMake/GeneratorExpression/RunCMakeTest.cmake
index 1c8fab5..cba3941 100644
--- a/Tests/RunCMake/GeneratorExpression/RunCMakeTest.cmake
+++ b/Tests/RunCMake/GeneratorExpression/RunCMakeTest.cmake
@@ -26,6 +26,7 @@ run_cmake(COMPILE_LANGUAGE-add_library)
run_cmake(COMPILE_LANGUAGE-add_test)
run_cmake(COMPILE_LANGUAGE-unknown-lang)
+run_cmake(ImportedTarget-TARGET_PDB_FILE)
if(LINKER_SUPPORTS_PDB)
run_cmake(NonValidTarget-TARGET_PDB_FILE)
run_cmake(ValidTarget-TARGET_PDB_FILE)
--
2.4.6
--
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:
[Cmake-commits] CMake branch, next, updated. v3.3.0-1808-g910b102
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 910b10207f43694f66036569b5604b023d39ab03 (commit)
via 354bbd881d3e46aa40e2a566967174682c0521b2 (commit)
from 1341adc5d45a5273c1e36904a2957e151fdaa1c9 (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=910b10207f43694f66036569b5604b023d39ab03
commit 910b10207f43694f66036569b5604b023d39ab03
Merge: 1341adc 354bbd8
Author: Brad King brad.k...@kitware.com
AuthorDate: Mon Aug 3 16:42:10 2015 -0400
Commit: CMake Topic Stage kwro...@kitware.com
CommitDate: Mon Aug 3 16:42:10 2015 -0400
Merge topic 'use-generator-target' into next
354bbd88 fixup! cmGeneratorTarget: Move GetFullName from cmTarget.
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=354bbd881d3e46aa40e2a566967174682c0521b2
commit 354bbd881d3e46aa40e2a566967174682c0521b2
Author: Brad King brad.k...@kitware.com
AuthorDate: Mon Aug 3 16:40:57 2015 -0400
Commit: Brad King brad.k...@kitware.com
CommitDate: Mon Aug 3 16:40:57 2015 -0400
fixup! cmGeneratorTarget: Move GetFullName from cmTarget.
diff --git a/Source/cmLocalVisualStudio6Generator.cxx
b/Source/cmLocalVisualStudio6Generator.cxx
index e1fa7d4..29e1034 100644
--- a/Source/cmLocalVisualStudio6Generator.cxx
+++ b/Source/cmLocalVisualStudio6Generator.cxx
@@ -1112,14 +1112,15 @@ void cmLocalVisualStudio6Generator
// Compute the proper name to use to link this library.
std::string lib;
std::string libDebug;
- cmGeneratorTarget* tgt = this-GlobalGenerator-GetGeneratorTarget(
- this-GlobalGenerator-FindTarget(j-first.c_str()));
+ cmTarget* tgt = this-GlobalGenerator-FindTarget(j-first.c_str());
if(tgt)
{
+cmGeneratorTarget* gt =
+ this-GlobalGenerator-GetGeneratorTarget(tgt);
lib = cmSystemTools::GetFilenameWithoutExtension
- (tgt-GetFullName().c_str());
+ (gt-GetFullName().c_str());
libDebug = cmSystemTools::GetFilenameWithoutExtension
- (tgt-GetFullName(Debug).c_str());
+ (gt-GetFullName(Debug).c_str());
lib += .lib;
libDebug += .lib;
}
---
Summary of changes:
Source/cmLocalVisualStudio6Generator.cxx |9 +
1 file changed, 5 insertions(+), 4 deletions(-)
hooks/post-receive
--
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits
Re: [cmake-developers] Java support
On 07/31/2015 04:08 AM, CHEVRIER, Marc wrote: New version of patches. Thanks. I applied the first three with minor tweaks and merged to 'next' for testing: FindJava: Add support for idlj and jarsigner tools http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=7e499264 UseJava: Teach add_jar to support file syntax for sources http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=244e9364 UseJava: Teach install_jar new DESTINATION and COMPONENT options http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=8f8d824d The 0004 patch (create_javah) fails testing for me on Linux: $ ctest -R Java.Javah -V ... 261: Running test command: /usr/lib/jvm/java-7-openjdk-amd64/bin/java -classpath hello3.jar HelloWorld2 261: Test command failed: /usr/lib/jvm/java-7-openjdk-amd64/bin/java 261: Native code library failed to load. 261: java.lang.UnsatisfiedLinkError: no B in java.library.path ... 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
