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.

Linker not finding file but file is present

Other Parts Discussed in Thread: CCSTUDIO

Hi,

 I've got a 2407 project that I copied all the files from one directory to another. In the copied directory when I go to build, I get the following error message from the linker. The file 4002x.cmd is present in the directory, and as far as I can tell the file does not have any file attributes set (read only or hidden). I checked the custom.lkf file and it appears to have the proper path for this file, same as all the other files in the build (that are fine). I've tried deleting the file and copying it again. I've also tried renaming the file, but I get the same error message all the time.

Why am I getting this message and how can I get this to recognize the file?

(CCS 3.3.82.13 Code gen 7.04)

[Linking...] "C:\CCStudio_v3.3\C2400\cgtools\bin\dspcl" -@"Custom.lkf"
<Linking>
TMS320C24xx COFF Linker                 Version 7.04
Copyright (c) 1987-2003  Texas Instruments Incorporated

>> : can't open file C:\Documents and Settings\bob\My Documents\Code\4002-16 DMM\4002-16-2.5.0 2.4.3 with changes for new breakout\4002x.cmd for input

 

Here's the first few lines of the custom.lkf file:

-z -estart -heap0 -m"VLTP100.map" -o"VLTP100.out" -stack32 -x -i"C:/CCStudio_v3.3/c2400/cgtools/lib" -l"rts2xx.lib"
"C:\Documents and Settings\bob\My Documents\Code\4002-16 DMM\4002-16-2.5.0  2.4.3 with changes for new breakout\4002x.cmd"
"C:\Documents and Settings\bob\My Documents\Code\4002-16 DMM\4002-16-2.5.0  2.4.3 with changes for new breakout\ad_proc.obj"
"C:\Documents and Settings\bob\My Documents\Code\4002-16 DMM\4002-16-2.5.0  2.4.3 with changes for new breakout\autobal.obj"
"C:\Documents and Settings\bob\My Documents\\Code\4002-16 DMM\4002-16-2.5.0  2.4.3 with changes for new breakout\burn_chk.ob

  • Hi Bob,

    I suspect that it is struggling with all the spaces in your path (at least it did so with me). Could you try and put it in a simpler path (without spaces) and see if this helps?

    Thanks

    ki

  • Hi,

     I moved the directory to C:\4002 and it did assemble and link correctly!

    I don't understand why the path would be a problem. I have other projects with longer paths and more spaces than this had. I suspect it has something to do with the fact that I copied the directory and changed the name after I copied it.

    Anyway, thanks for your help.

     

    Regards,

    Bob

  • I think the linker does not like double spaces in the path. I removed a space in the folder: "4002-16-2.50  2.4.3 with changes for new breakout" so that it became "4002-16-2.50 2.4.3 with changes for new breakout" (note only one space now between "4002-16-2.50" and "2.4.3") and the issue seems to go away.

    Note that the compiler -fr option doesn't seem to like any spaces at all. You should wrap in quotes or avoid spaces when using the -fr option.

    ki