User forums > Help
Setting enviroment variable for cross compiling
CmKaHo:
Feature req. 003350 established.
--- Quote from: MortenMacFly on April 25, 2007, 08:11:05 am ---Well this would only make sense if the envvars are stored in the project file... is that what you mean?
--- End quote ---
Yes - this is one (good) way.
--- Quote from: mandrav on April 25, 2007, 08:49:43 am ---
--- Quote ---Anyways: IIRC there was a time where the custom variables were *also* exported to envvars if setup. Should this feature return?
--- End quote ---
That's a possibility too :).
--- End quote ---
Good idea. Simple and sufficient.
mandrav:
--- Quote from: MortenMacFly on April 25, 2007, 10:28:37 am ---
--- Quote from: mandrav on April 25, 2007, 08:49:43 am ---That's a possibility too :).
--- End quote ---
Looking into it... it seems to be as simple as to modify compileroptionsbase.cpp "SetVar", "UnsetVar" and "UnsetAllVars" accordingly... Should it really be as simple as that?!
With regards, Morten.
--- End quote ---
No :)
These just set/unset the variables in the respective target/project.
Search in macrosmanager.cpp for calls to GetAllVars(). That's where it accesses the custom variables of a project/target/compiler and it's where we 'd export them to the environment if we needed to (although now it would be an all-or-nothing deal).
dmoore:
--- Quote from: mandrav on April 25, 2007, 12:59:10 pm --- (although now it would be an all-or-nothing deal).
--- End quote ---
too hard to have a checkbox option on each custom variable?
mandrav:
--- Quote from: dmoore on April 25, 2007, 07:03:58 pm ---
--- Quote from: mandrav on April 25, 2007, 12:59:10 pm --- (although now it would be an all-or-nothing deal).
--- End quote ---
too hard to have a checkbox option on each custom variable?
--- End quote ---
Yes because we 'd have to change the base type that stores these custom variables.
And changing the sdk interface at this time is out of the question...
Navigation
[0] Message Index
[*] Previous page
Go to full version