CCS: Windows Environment variable for Resource->Linked Resources

Ki,

Thanks.  A little clarification please - even if it appears as a "system variable", that could not be used directly as a build variable, without explicitly adding it to the build variables as well.  The idea was that each user would have their own system variable defining a project path, that CCS would automatically enlist as a build variable.  But I guess, from your reply, that is not possible - it would always require manually adding it to the build variable (so wouldn't matter whether was defined as system variable, or not).

Robert

Robert Wolfe said:

The idea was that each user would have their own system variable defining a project path, that CCS would automatically enlist as a build variable. 

However, you can use an environment variable to specify other project path settings, e.g. compiler search paths.

In the following example added the VERSION_ROOT environment variable to the compiler include path:

Where round brackets are used to reference an environment variable.

With the VERSION_ROOT environment variable set before starting CCS:

C:\Users\mr_halfword>set VERSION_ROOT=%USERPROFILE%\my_version

C:\Users\mr_halfword>c:\ti\ccs920\ccs\eclipse\ccstudio.exe

When a build was performed in CCS the environment variable was used to populate the include path to the compiler:

Invoking: ARM Compiler

"C:/ti/ccs920/ccs/tools/compiler/ti-cgt-arm_18.12.4.LTS/bin/armcl" -mv7M4 --code_state=16 --float_support=FPv4SPD16 -me --include_path="C:/Users/mr_halfword/workspace_v9_2/TM4C1294_hello" --include_path="C:/ti/ccs920/ccs/tools/compiler/ti-cgt-arm_18.12.4.LTS/include" --include_path="C:\Users\mr_halfword\my_version" --define=ccs="ccs" --define=PART_TM4C1294NCPDT -g --gcc --diag_warning=225 --diag_wrap=off --display_error_number --abi=eabi --preproc_with_compile --preproc_dependency="tm4c1294ncpdt_startup_ccs.d_raw" "../tm4c1294ncpdt_startup_ccs.c"

Ok, thanks for the additional clarification.  Just to be clear, a environment variable could not be used in the Resource->Path Variables, per attached picture.

Robert

Ok Chester, thanks for the follow-ups.  We'll write it off for now, then.

Robert

Robert Wolfe said:

it would always require manually adding it to the build variable (so wouldn't matter whether was defined as system variable, or not).

Note that you can also try using a macro.ini to define the variable and add it to the project. On project import, CCS would read the file and add the variable as both build variable and path variable. However, the user would still then need to manually modify the path to match their environment. Not a perfect solution but maybe still useful to a degree

https://software-dl.ti.com/ccs/esd/documents/ccs_portable-projects.html#sharing-variables-file

Thanks

ki

Great Ki, maybe that is an option we can use.

Thanks,

Robert