#303 MSVC Import: GCC needs different ENV var strings

[Oliver Stöneberg]

In MSVC you can use ENV var for e.g. defines. In MSVC
they have to be $(ENV_VAR). Those aren't working in
GCC. GCC needs $ENV_VAR. When importing a MSVC project,
this should be converted.

[Oliver Stöneberg]

Logged In: YES
user_id=591019

Hm...I thought I had it working with $ENV_VAR. But for some
reason it doesn't work. I will look into it later and put a
comment with the right solution for GCC here.

[Colin Laplace]

Logged In: YES
user_id=25510

Ok, when reporting MSVC import bugs, please also attach a
sample MSVC project files - I don't have any on my
computers ;)

Colin

[Marek Januszewski]

Logged In: YES
user_id=609236

try ${ENV_VAR} ?

[Oliver Stöneberg]

Logged In: YES
user_id=591019

yes, it seems to work! :)

[Marek Januszewski]

Logged In: YES
user_id=609236

so I'm going to close this one.

[Nobody/Anonymous]

Logged In: NO

Err...well...it should be added to the MSVC importer, as you
can use $(xxx) vars in there and they won't work with GCC.
That's the reason why I added this bug report.

[Marek Januszewski]

Logged In: YES
user_id=609236

998873 is similar to this bug

[aditsu]

Logged In: YES
user_id=682737

I'd like to use environment variables for the exe and object
output dirs (in build options); I tried a few things but it
didn't work.
I'm not sure if this fits here, should I submit a new bug
report (or rfe)?

Adrian

[Marek Januszewski]

Logged In: YES
user_id=609236

Adrian, probably a new rfe