Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

Per compiler custom variables not expanded?

<< < (2/4) > >>

yop:
AFAIR when I added the Intel compiler support, that global variable was set by the compiler installation, but maybe I 'm wrong as the support for that compiler was added somewhere around November (?) and the global variables expansion was still there. My demo license for icc in windows has expired so I can't take a look at it. Also I haven't yet installed it in my (brand new) gentoo box but until a month ago it worked on a regular basis on my suse installation without any problems.

MortenMacFly:

--- Quote from: yop on May 08, 2006, 04:31:52 pm ---AFAIR when I added the Intel compiler support, that global variable was set by the compiler installation, [...]

--- End quote ---
No, you are right. It is set during installation. So there is nothing wrong with the Intel compiler plugin. But I'm working on a terminal server that resets all user-settings made after log-out for security reasons. So this environment variable is lost everytime I log off. I've also "installed" the Intel compiler by simply copying it and not using the installer (I don't have the right to run a setup on that machine). So I see basically 3 requirements for the implementation of an "environment - variables - setting - thingy":
1.) You want to set environment variables by hand (e.g. you want to force overwriting an existing one, e.g. LIBS or INCLUDES.)
2.) You have conflicting environment variables for compilers and/or tools, e.g. "LICENSE_FILE" is used by quite some tools - so this would result in 1.) basically.
3.) You want to run tests with your application that uses (expands) environment variables.

On my way home I thought about that problem any further. I think it shouldn't be a per-compiler option. Maybe it's best to implement this feature one-time only under "settings" and maybe as an addition to the "runner" options. This means e.g. the console runner would be in charge for setting environment variables provided via a command line option (e.g. console_runner -Emy_env=my_value or similar...). Setting up such variables would then be a per-project setting... just line the command line passed to the application.

Any comments on that?

With regards, Morten.

thomas:
Actually, why don't we just make a environment variables plugin?  8)

When the plugin loads, it sets whatever variables you have specified, so they are always defined as long as Code::Blocks runs.

MortenMacFly:

--- Quote from: thomas on May 08, 2006, 06:04:21 pm ---Actually, why don't we just make a environment variables plugin?  8)

--- End quote ---
Well... sounds quite simple and is (indeed) a good idea. Are you going to implement this within 5 minutes again (like the autosave plugin)? Otherwise I would volunteer and give it a try... but it might take significantly longer... ;-)
With regards, Morten.

thomas:
Dinner first :)  But if you like, go ahead :)

Navigation

[0] Message Index

[#] Next page

[*] Previous page