compiler options file

E2E_display_name_Mike

To compile my project, I want to use the options file (-@ option) so that I have a default set of options archived. I find I can't use environment variables in this file (e.g. $(Proj_dir)). So adding a search path of

-i"$(Proj_dir)\..\..\c6747_drivers"

does NOT work but

-i".\..\..\c6747_drivers"

does work.  But using relative directory references is relative to each file compiled so it is applied differently when the source file is in a different folder location.

Is there a way to get environment variables to work in the options file?  OR can you suggest a good work around?  Using relative path names is not a good work around for projects where 
source files are located in different folder levels.

Mike

over 16 years ago

0 Mariana over 16 years ago

TI__Mastermind 24340 points

Hi Mike,

Try:

-i"%(Proj_dir)%\..\..\c6747_drivers" instead of -i"$(Proj_dir)\..\..\c6747_drivers"

0 E2E_display_name_Mike over 16 years ago in reply to Mariana

Expert 1700 points

This didn't work - does it work for you? I can't even debug it because the compiler output doesn't display how it resolves the environment variable --> or if it even resolves it or not. I suspect it's ignoring it and the -i command within which it is located.

Mike

0 Mariana over 16 years ago in reply to E2E_display_name_Mike

TI__Mastermind 24340 points

Sorry Mike,

I will not work, please see:

Can I use CCS macros, such as $(Install_dir), inside my *.opt (and *.cmd) files?

For CCS env variables you would use $ indeed. For windows env variables, you would use %%. But again, these will not work for the file...

Processors

Processors forum

compiler options file