For now, a wrapper script is definitely the way to do this.
We need the ability to specify environment values generically in the
"add_custom_command" command. Once we have that, adding support to
ExternalProject will be trivial. Until we have that, a wrapper script
work-around is valid now and wil
Thanks Luigi. I feared a workaround was necessary. I will go over your
suggestion and try to apply it.
I'll second your suggestion for providing environment variables for
ExternalProjects.
Miki.
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/op
On 17/10/2011 18.27, Milutin Jovanovic' wrote:
Hi all,
Hi all. First time posting. Before I start I'd like to thank all the
Kitware guys for a very nice and useful tool. I did a fair bit of
searching to try to avoid asking duplicate questions, but did not find
answer to my problem.
I am tr
Hi all,
Hi all. First time posting. Before I start I'd like to thank all the Kitware
guys for a very nice and useful tool. I did a fair bit of searching to try
to avoid asking duplicate questions, but did not find answer to my problem.
I am trying to make a private build of some dependencies, ogg
On Tuesday 20 October 2009, James C. Sutherland wrote:
> How do I set an environment variable so that it is visible globally in
> CMake? Specifically, I want to have it visible when I run something
> like:
>
> #---
> # set the environment variable value
> set( ENV{m
How do I set an environment variable so that it is visible globally in
CMake? Specifically, I want to have it visible when I run something
like:
#---
# set the environment variable value
set( ENV{myVariable} ... )
# run a test through a CMake script that requ
Robert Bielik skrev:
Is there a way to set environment variables (Windoze) permanently with
CMake ? Tried the
SET(ENV{MY_ENV_VAR} Stuff) but since MY_ENV_VAR never showed up after
running CMake I suspect
it is only set locally in the process running CMake...
Ok, so this seems to be the case (
Is there a way to set environment variables (Windoze) permanently with CMake ?
Tried the
SET(ENV{MY_ENV_VAR} Stuff) but since MY_ENV_VAR never showed up after running
CMake I suspect
it is only set locally in the process running CMake...
TIA
/R
___
C
No, I can't. The reason I don't generate them is that they have to be
portable since they are shipped to customers as a part of an SDK, and as
I understand it the project files CMake generates are not
portable/movable (due to absolute paths, etc).
You can generate relative paths with the fo
Bill Hoffman wrote:
> Jesper Eskilson wrote:
>> Is there any way for CMake to set environment variables which can be
>> picked up in Visual Studio's pre/post-build steps?
>>
>> I'm working on a system where I've got a couple of studio project
>> included via the INCLUDE_EXTERNAL_MSPROJECT(), and I
Sylvain Benner wrote:
>
>
>> Is there any way for CMake to set environment variables which can be
>> picked up in Visual Studio's pre/post-build steps?
>>
>> I'm working on a system where I've got a couple of studio project
>> included via the INCLUDE_EXTERNAL_MSPROJECT(), and I would like to be
Is there any way for CMake to set environment variables which can be
picked up in Visual Studio's pre/post-build steps?
I'm working on a system where I've got a couple of studio project
included via the INCLUDE_EXTERNAL_MSPROJECT(), and I would like to be
able to refer to things like CMAKE_BIN
Jesper Eskilson wrote:
Is there any way for CMake to set environment variables which can be
picked up in Visual Studio's pre/post-build steps?
I'm working on a system where I've got a couple of studio project
included via the INCLUDE_EXTERNAL_MSPROJECT(), and I would like to be
able to refer to
Is there any way for CMake to set environment variables which can be
picked up in Visual Studio's pre/post-build steps?
I'm working on a system where I've got a couple of studio project
included via the INCLUDE_EXTERNAL_MSPROJECT(), and I would like to be
able to refer to things like CMAKE_BINARY_
14 matches
Mail list logo
