CMP0053 warns/fails on $ENV{ProgramFiles(x86)}.
Could () be added to the legal set of characters when within an $ENV{}
expansion?
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
On 10/06/2014 06:39 AM, Nils Gladitz wrote:
CMP0053 warns/fails on $ENV{ProgramFiles(x86)}.
Could () be added to the legal set of characters when within an $ENV{}
expansion?
We considered that case and decided to ask users to use a
nested variable reference for that case. There is a
On 10/06/2014 02:48 PM, Brad King wrote:
On 10/06/2014 06:39 AM, Nils Gladitz wrote:
CMP0053 warns/fails on $ENV{ProgramFiles(x86)}.
Could () be added to the legal set of characters when within an $ENV{}
expansion?
We considered that case and decided to ask users to use a
nested variable
On 10/05/2014 04:59 PM, Ruslan Baratov via cmake-developers wrote:
So it can't be resolved without some low-level management. I'm thinking
about `file` command sub-option like LOCK_DIRECTORY:
`file(LOCK_DIRECTORY /path/to/shared-dir)`. Does it sounds doable?
I think it is a reasonable
On 10/05/2014 05:18 AM, Konstantin Podsvirov wrote:
Straight to the point: Brad please apply my changes!
I've merged the topic to 'next' for testing:
CPackIFW: Search algorithm update
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=f9f74874
CPackIFW: Added support for multiple
On 10/04/2014 11:37 AM, Adam Strzelecki wrote:
I've applied your suggestions about quoting and used portable
(POSIX compliant) find call that should work now on any system.
Thanks.
On 10/05/2014 03:35 PM, Adam Strzelecki wrote:
Correct me if I am wrong but it seems CDash reports no
further
On 10/06/2014 09:15 AM, Konstantin Podsvirov wrote:
Can I expect that CPack IFW generator will be in the tag v3.1.0-rc1?
Anything that is in 'master' now will be in 3.1. This update should
be merged in time barring catastrophic problems with it.
Thanks,
-Brad
--
Powered by www.kitware.com
06.10.2014, 17:01, Brad King brad.k...@kitware.com:
On 10/05/2014 05:18 AM, Konstantin Podsvirov wrote:
Straight to the point: Brad please apply my changes!
I've merged the topic to 'next' for testing...
Thank you :-)
Can I expect that CPack IFW generator will be in the tag v3.1.0-rc1?
This
- Original Message -
On 10/04/2014 11:37 AM, Adam Strzelecki wrote:
I've applied your suggestions about quoting and used portable
(POSIX compliant) find call that should work now on any system.
Thanks.
On 10/05/2014 03:35 PM, Adam Strzelecki wrote:
Correct me if I am wrong
Sure, I think it would be good to require 10.6.
We also have uses of the -delete_rpath/-add_rpath parameters in
cmInstallTargetGenerator.cxx, and the test of that already requires 10.6 or
greater.
Moreover I believe nobody nowadays builds for 10.5 on 10.5. Since 10.6 with
Xcode 3 supports
On 10/06/2014 10:36 AM, Adam Strzelecki wrote:
Sure, I think it would be good to require 10.6.
Moreover I believe nobody nowadays builds for 10.5 on 10.5.
Perhaps no one has to build that way for deployment but there could
still be people just building for their own host as the only computer
On Fri, Oct 03, 2014 at 13:51:54 -0400, Ben Boeckel wrote:
Feel free to cherry-pick the documentation fixes (or I can spin out a
branch) if the other changes are too late (I hope to add tests Monday,
but can do it today if that's too late).
A test has been added. Brad, there are some bugfixes
On 10/06/2014 02:24 PM, Ben Boeckel wrote:
On Fri, Oct 03, 2014 at 13:51:54 -0400, Ben Boeckel wrote:
Feel free to cherry-pick the documentation fixes (or I can spin out a
branch) if the other changes are too late (I hope to add tests Monday,
but can do it today if that's too late).
A test
On Mon, Oct 06, 2014 at 14:31:58 -0400, Brad King wrote:
Please re-order the topic to have all the fixes first, and then the
changes to add ubsan support. That way I can revert the latter if
it is problematic. Then merge the whole topic for testing.
Done.
--Ben
--
Powered by
Brad King wrote:
On 10/03/2014 12:47 PM, Rolf Eike Beer wrote:
+ # give an exact match if the first ${NAME}_FIND_VERSION_COUNT
components of the version string match + # this constructs the
equivalent of (([^.]\\.){${${_NAME}_FIND_VERSION_COUNT}}) +
- Original Message -
On 10/06/2014 10:36 AM, Adam Strzelecki wrote:
Sure, I think it would be good to require 10.6.
Moreover I believe nobody nowadays builds for 10.5 on 10.5.
Perhaps no one has to build that way for deployment but there could
still be people just building for
Hello,
Variables like CPACK_DEBIAN_PACKAGE_DEPENDS and CPACK_RPM_PACKAGE_REQUIRES
can be set.
Do you know any other package formats where similar settings are supported by
corresponding generators?
http://www.cmake.org/Wiki/CMake:CPackPackageGenerators
Regards,
Markus
--
Powered by
As is also written in the stackoverflow answer, this information can be found
in the cmake documentation for find_package[1]:
prefix/ (W)
prefix/(cmake|CMake)/ (W)
prefix/name*/
Hi,
After generating Eclipse projects and importing them, Eclipse is not
indexing all source files. I have detailed the issue (so sorry for the long
email) and the experiments I have performed to resolve the issue. I would
be really glad if someone could point out, what is going wrong or is there
Hi there,
For some mysterious reason the invocation in subject does not print out the
all-important message CMAKE_C_COMPILER=path_to_cl.exe after the
compilation of CompilerIdC.c
The invocation in question is in CMakeDetermnineCompilerId.cmake like 188.
The CMAKE_C_COMPILER message is the one
Thanks very much for taking a careful look at this, Bill.
The source files in my test were more or less the same as yours but I
changed them to be identical.
Most of my previous tests were with the 2013 Express version of VS but
I had also done a couple of tests with 2010 Express. Previously, I
On 10/6/2014 2:10 PM, Bill Greene wrote:
After I change MySub.cpp, either with touch or by editing the file in the
GUI, and rebuild either with the F7 key or by selecting the Build Solution
menu item, I see something like this:
What if you right click on ALL_BUILD and build that project? It
Hi,
thanks for your detailled findings.
Can you please create a ticket in the bug tracker with this, so it doesn't get
lost ?
http://public.kitware.com/Bug
Thanks
Alex
On Monday, October 06, 2014 14:30:06 Tushar Soni wrote:
Hi,
After generating Eclipse projects and importing them, Eclipse
What if you right click on ALL_BUILD and build that project?
For some reason, the ALL_BUILD project was *not* selected/checked to build.
However if I build it explicitly or
change the VS configuration so it does build, the main program is still not
being re-linked.
Another thing to try is to
Hi,
For Xcode generator, is it possible to specify CFLAGS for each architecture,
e.g. i386 and x86_64? Thanks!
Best regards,
Bin Chen
Notice:
This message and any included attachments are intended only for the use of the
addressee, and may contain
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 131df017bf969f67d62804e376589589c4577d4d (commit)
via
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 08f9eff69c5ae8ff4e086be590b4434d84729da9 (commit)
via
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 b6b7bd3ea7a5524f86370d0a65a58cba55df299a (commit)
via
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 e0fef85c7a493b655cb6a7d0c4b6e7bb11e8a6b6 (commit)
via
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 3f9191932262f2279a7d25bf0dbb2fc224bd27cb (commit)
via
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 b1531431dd4914ffd8cd48e7d5b23fe77360dc19 (commit)
via
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 c74d2ddfa47792326c6d8b74df8816e27ad87e4c (commit)
via
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 a1859811ec00a1b0c3755c023e32cce83c0ffe0d (commit)
via
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 d33aceb1e1351f51f793376b0bb4be13b23cce2e (commit)
via
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 b838deb2e9627bf2d607de300f4a9ca287baec38 (commit)
via
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 279b884a14f424c64ec7d72b68cc8e6e613eb854 (commit)
via
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 05d793389215d5f80e7b4e444ecb1452250e6cbb (commit)
via
20141006)
+set(CMake_VERSION_PATCH 20141007)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/post-receive
--
CMake
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 ff01a61060dedea83dfba83bf636dabd85d89c61 (commit)
via
39 matches
Mail list logo
