Hi,
In Unix shell we can do that:
$ VAR=foo cmd in out
This way the environment variable is only set in the environment of the
process of the command and not the in current shell like when using the
"export" built-in.
I would like to be able to do the same for a custom command in CMake.
Ideally
Sorry wrong ML :(.
On Fri, Jul 19, 2013 at 4:36 PM, Nicolas Desprès
wrote:
> Hi,
>
> In Unix shell we can do that:
> $ VAR=foo cmd in out
>
> This way the environment variable is only set in the environment of the
> process of the command and not the in current shell like when using the
> "expor
On 07/19/2013 10:36 AM, Nicolas Desprès wrote:
> Hi,
>
> In Unix shell we can do that:
> $ VAR=foo cmd in out
>
> This way the environment variable is only set in the environment of the
> process of the command and not the in current shell like when using the
> "export" built-in.
>
> I would l
On 2013-07-19 10:36, Nicolas Desprès wrote:
In Unix shell we can do that:
$ VAR=foo cmd in out
This way the environment variable is only set in the environment of the
process of the command and not the in current shell like when using the
"export" built-in.
I would like to be able to do the sam
On 2013-07-19 12:35-0400 Matthew Woehlke wrote:
On 2013-07-19 10:36, Nicolas Desprès wrote:
In Unix shell we can do that:
$ VAR=foo cmd in out
This way the environment variable is only set in the environment of the
process of the command and not the in current shell like when using the
"export
On Fri, Jul 19, 2013 at 8:29 PM, Alan W. Irwin wrote:
> On 2013-07-19 12:35-0400 Matthew Woehlke wrote:
>
> On 2013-07-19 10:36, Nicolas Desprès wrote:
>>
>>> In Unix shell we can do that:
>>> $ VAR=foo cmd in out
>>>
>>> This way the environment variable is only set in the environment of the
>>>
