The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=15579
==
Reported By:yak32
Assigned To:
Hi Cedric.
When doing things like that, remember that CMake's named arguments are
arguments just like any other. So you can easily obtain them from variable
expansion; something like this:
if(${LIBRARY}_CONFIGURE_COMMAND)
set(the_configure_command CONFIGURE_COMMAND
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 f3e4e3ecde21e790c6428f553f81e4d544f4e73b (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 3e3a09d1d3c91a6522260734b4542b420152e21c (commit)
via
Thank you very much for your help, Petr!
I will try it!
Cheers,
Cédric
- Mail original -
De: Petr Kmoch petr.km...@gmail.com
À: Cedric Doucet cedric.dou...@inria.fr
Cc: cmake@cmake.org
Envoyé: Jeudi 21 Mai 2015 14:21:48
Objet: Re: [CMake] How to skip steps and use default values
On 05/21/2015 08:43 AM, Taylor Braun-Jones wrote:
Why is CMake stripping MAKEFLAGS from its environment?
This has been done since our very early days in this commit:
BUG: Need to remove the MAKEFLAGS when cmake starts. If cmake is run from
inside make, we don't want the try-compiles to
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 dc7377cb0c319462ec1830e3ea43d6bb2b38f99c (commit)
via
No idea on this one. The trick I showed is vanilla CMake, a direct
consequence of the CMake parsing string processing algorithm. What you're
asking is about the internals of ExternalProject_Add, of which I know
nothing.
Petr
On Thu, May 21, 2015 at 1:43 PM, Cedric Doucet cedric.dou...@inria.fr
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 8070c4f252293e7dfe44fd2c53d5d7498b307c67 (commit)
via
This is what I'm seeing:
$ echo 'message(MAKEFLAGS: $ENV{MAKEFLAGS}\nFOO: $ENV{FOO})'
CMakeLists.txt
$ MAKEFLAGS=test FOO=bar cmake .
-- The C compiler identification is GNU 4.8.3
-- The CXX compiler identification is GNU 4.8.3
-- Check for working C compiler: /usr/lib64/ccache/cc
-- Check for
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 831e03dd36b80a02cd47bbb0aa9a17b46306f799 (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 41d833e1e9decb422c019f16626fe61e38c03eec (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 db90e7c6bcd40c2cdc27232f5305800ae215ce14 (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 26a04a684403b9d0d8a478a1ff8ec6f0fc404cb2 (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 2c54622ff57b2ccb44d4e99e2fefb0501dbccb92 (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 482438b97ac5d5be76cbb457c6187478a5fa50dd (commit)
via
Hello,
I would like to loop on a list of libraries to download and install, by calling
the ExternalProject_Add command for each of these libraries.
To do that, I need to define some commands for each library, like
CONFIGURE_COMMAND, BUILD_COMMAND and INSTALL_COMMAND.
These commands may
On Thu, May 21, 2015 at 10:19 AM, Brad King brad.k...@kitware.com wrote:
We typically run coverage as part of nightly testing with a 'ctest -S'
dashboard client script. The script surrounds the actual build
invocation and can take responsibility for adding things like COVFILE
to the
Does the CMake Ninja generator support a way to skip dependencies when
building a target? Something like the target_name/fast feature for the
Makefile generator? [1]
Thanks,
Taylor
[1]
http://www.cmake.org/Wiki/CMake_FAQ#Is_there_a_way_to_skip_checking_of_dependent_libraries_when_compiling.3F
--
On Thu, May 21, 2015 at 9:44 AM, Ben Boeckel ben.boec...@kitware.com
wrote:
The problem with MAKEFLAGS is that `-i` also gets inherited and that is
not acceptable to use when running things like try_compile since it
causes false positives (e.g., detecting NEON extensions on x86). CMake
clears
On Thu, May 21, 2015 at 8:56 AM, Brad King brad.k...@kitware.com wrote:
What are you trying to do?
I'm trying to implement a workaround solution for setting environment
variables in my Makefiles at build time. So what I started with was this:
set(bullseye_environment
On 05/21/2015 09:31 AM, Taylor Braun-Jones wrote:
gmake[1]: warning: jobserver unavailable: using -j1. Add `+' to parent make
rule.
I don't think that is caused by the MAKEFLAGS removal I linked.
The code I linked does not run during 'cmake --build'. It only
runs while configuring a project
On 05/21/2015 09:31 AM, Taylor Braun-Jones wrote:
I'm trying to implement a workaround solution for setting environment
variables
in my Makefiles at build time. So what I started with was this:
set(bullseye_environment COVFILE=${PROJECT_BINARY_DIR}/bullseye/test.cov)
On Thu, May 21, 2015 at 09:31:41 -0400, Taylor Braun-Jones wrote:
So I added another workound for that:
if(${CMAKE_GENERATOR} MATCHES .* Makefiles$)
set(environment_build_flags $ENV{MAKEFLAGS})
endif()
add_custom_target(coverage_data
COMMAND env --unset=MAKEFLAGS
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 75e071117161e8e01a5fd3144279f276dcf8f1a1 (commit)
via
Hi Folks,
Last year FindOpenGL gained imported targets:
FindOpenGL: Provide imported targets for GL and GLU
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=b7804cb6
only to be reverted prior to release:
FindOpenGL: Revert support for imported targets
Taylor Braun-Jones wrote:
Does the CMake Ninja generator support a way to skip dependencies when
building a target? Something like the target_name/fast feature for the
Makefile generator? [1]
I believe the last time that was raised was
Hello,
I am trying to compile a code written in C, but using an external library that
contains C++ functions. I am on a Cray system and everything works if I
manually link with the cray CC wrapper. When I change the linker language with
this command:
set_property(TARGET adh PROPERTY
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 d2a981afa7e038dfb44e2643e263f089bfd12541 (commit)
via
20150521)
+set(CMake_VERSION_PATCH 20150522)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/post-receive
--
CMake
On Thu, May 21, 2015 at 10:14 AM, Brad King brad.k...@kitware.com wrote:
You could try using +env as your COMMAND instead, though I wouldn't
consider this an officially supported approach.
Thanks - that works and is a much better workaround.
--
Powered by www.kitware.com
Please keep
31 matches
Mail list logo
