On 11-Aug-15 07:49, James Johnston wrote:
I have found it annoyingly difficult to set up an environment for a build
when using ExternalProject_Add.
I can confirm that there is an additional mess with the environment
sometimes and not just about setting it (like vcvarsall.bat for Visual
Studio
On 08/12/2015 08:06 PM, James Johnston wrote:
>> http://www.cmake.org/Bug/view.php?id=15653
> I'll explore that option some more, after the feature you linked to is
> addressed.
Currently no one is looking at addressing it. If you want to work on
it, take a look at the PERMISSIONS option of the
> -Original Message-
> From: cmake-developers [mailto:cmake-developers-boun...@cmake.org]
> On Behalf Of Brad King
> Sent: Wednesday, August 12, 2015 14:10
> To: cmake-developers@cmake.org
> Subject: Re: [cmake-developers] Setting up environment using
> ExternalProj
> -Original Message-
> From: cmake-developers [mailto:cmake-developers-boun...@cmake.org]
> On Behalf Of David Cole via cmake-developers
> Sent: Wednesday, August 12, 2015 15:53
> To: Brad King
> Cc: cmake-developers@cmake.org
> Subject: Re: [cmake-developers] Setting
One thing to consider before embarking on modifying CMake for
"required environment" purposes is that it might be just as simple to
"force" (or at least strongly encourage) your project developers to
use the proper environment for running the whole build.
You could, for example, have an initial "e
On 08/11/2015 10:41 AM, James Johnston wrote:
> 1. CMake creates a temporary shell script / batch file (the shell chosen
> based on the platform CMake compiled for - cmd.exe on Windows, sh on POSIX).
I don't think CMake needs to be the one to generate this. The complexity
of the file-based or co
> -Original Message-
> From: Brad King [mailto:brad.k...@kitware.com]
> Sent: Tuesday, August 11, 2015 13:35
> To: James Johnston
> Cc: cmake-developers@cmake.org
> Subject: Re: [cmake-developers] Setting up environment using
> ExternalProject_Add
>
> On
On 08/11/2015 12:49 AM, James Johnston wrote:
> CONFIGURE_ENVIRONMENT_COMMAND
[snip]
> add_custom_command( ENVIRONMENT_COMMAND
> COMMAND ${CMAKE_PROGRAM} -GNinja )
A problem with both of these approaches is that on UNIX and in Make
the environment does not persist after the c
Hi,
(Pardon the length; skip to end to see what I am proposing to change. Below
is justification why.)
I have found it annoyingly difficult to set up an environment for a build
when using ExternalProject_Add. This seems to be needed when creating a
superbuild that uses several different compile
