Environment variables in Linker command files

Gerard Belanger1

Greetings,

I am using a custom linker command file before the CCS generated file to force _c_int00 to the beginning of my load module.

The method is from http://processors.wiki.ti.com/index.php/Accessing_c_int00#Using_SYS.2FBIOS

My specific code is:

SECTIONS
{
   boot : > 0x80000000
   {
      -l"C:\ti\xdctools_3_24_07_73\packages\ti\targets\arm\rtsarm\lib\boot.aea8fnv" <boot.oea8fnv> (.text)
    }
}

This does work, but I dislike having to hard code the path.

Is there a way to use a CCS variable, or an environment variable such as XDC_GG_ROOT or XDCROOT for the product specific part of the path?

Tools:

CCS 5.3.0.00090

Arm compiler tools 5.0.4

Gerry Belanger

over 12 years ago

0 Archaeologist over 12 years ago

TI__Guru* 84285 points

Try using a wildcard:

SECTIONS
{
    boot : > 0x80000000
    {
      *<boot.oea8fnv>(.text) 
    } 
}

0 Gerard Belanger1 over 12 years ago in reply to Archaeologist

Intellectual 955 points

Archaeologist said:

Try using a wildcard:

SECTIONS
{
    boot : > 0x80000000
    {
      *<boot.oea8fnv>(.text) 
    } 
}

That works ! One less complication.

Thanks!

GerryB

Code Composer Studio™︎

Code Composer Studio forum

Environment variables in Linker command files