• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 53 subscribers
  • Views 732 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CCS/TMS320C6748: CCS9 Linker: Cannot find rts6740.lib

Nathan Blilie
Prodigy 20 points
Part Number: TMS320C6748

Tool/software: Code Composer Studio

I have a project that I've been using for several CCS versions with no issues. I installed CCS9 and imported the project. I have this in my .cmd file:

SECTIONS
{
.boot > SHRAM
{
-l rts6740.lib<boot.obj>(.text)
}

etc.

The linker command and output are

Invoking: C6000 Linker
"C:/ti/ccs901/ccs/tools/compiler/c6000_7.4.24/bin/cl6x" -mv6740 --abi=coffabi -O2 --define=c6748 -z --stack_size=0x800 --heap_size=0x800 --reread_libs --warn_sections --rom_model -o "Dtmb2Dsp.out" bunch of obj files here "../C6748.cmd" "../c674xfastMath.lib" "../dsp67x.lib" "../dsplib.lib" -l"C:/ti/ccs901/ccs/tools/compiler/c6000_7.4.24/lib/rts6740.lib"
<Linking>
"../C6748.cmd", line 68: error: cannot find file "rts6740.lib"
error: errors encountered during linking; "Dtmb2Dsp.out" not built

 

Even though I have explicitly specified the location of the rts6740.lib file, I still get this error.

Help? Thanks

  • 0
    TI__Guru**** 464751 points

    Hello Nathan,

    Seems like you are referencing (-l) the library by its full path in the linker properties:

    Nathan Blilie said:
    -l"C:/ti/ccs901/ccs/tools/compiler/c6000_7.4.24/lib/rts6740.lib"

    Since you did not specify the library search path to that library, the linker command file is unable to find it with just the name alone:

    Nathan Blilie said:
    "../C6748.cmd", line 68: error: cannot find file "rts6740.lib"

    You either need to:

    A) add the full path to the library in the cmd file

    OR

    B) add the path to the library in the library search path (-i) list for the linker properties.

    Option B is likely the best solution as you can set the path once then just reference the library by just the name.

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 20 points
    Thank you. You're probably right, but I don't know how the paths became so messed up. To fix the problem, I deleted the Workspace and reimported the project and then I was successful building it.