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/AM4379: example on how to create a linker command file

Part Number: AM4379

Tool/software: Code Composer Studio

hello everybody , 

Can you give a detail example how to configure the CCS to generate a linker command file instead of the default command line ?

my issue is  I m coding in C  and  have many many file  and having a  linker command file  could help me a lot 

thank you 

bye

Carlo

 

  • Carlo,

    Colombo Carlo said:
    Can you give a detail example how to configure the CCS to generate a linker command file instead of the default command line ?

    I am not entirely sure what you mean by "default command line", but if you create a new project (menu File --> New --> CCS Project) and select the AM4379 device, it will create an empty project with the linker script or command file (depending on the core and toolchain used)

    This linker script typically contains a minimal set of settings to allow you to create a "Hello world" type of project. Obviously more intricate projects will require modifications to it. 

    Hope this helps,

    Rafael

  • Hi Rafael ,
    let me give you more details . My issue is I got a very long script command ( over 8K characters ) causing to have issue in windows system . I already created libs , but still have a long script . It would be great to have a command file instead of a script .
    how can I make it ?
    thank you
    bye
    Carlo
  • Carlo,

    So, it seems you are creating a project from the command line using eclipsec.exe, right? If so, there is no unique way to solve this issue.

    I would try to reduce path names by either moving the build tree closer to the root directory (C:\) or create project path variables to remove long paths. Another thing to do is consolidate paths to libraries and include files that can suppress -I entries.

    Apart from this I don't think it is easy to do something for this case. I tried Windows' built in PowerShell but it seems to have an even smaller command line size.

    I will think of any additional details and post it here if I find anything that could help.

    Hope this helps,
    Rafael
  • Colombo Carlo said:
    My issue is I got a very long script command ( over 8K characters ) causing to have issue in windows system .

    I last time I investigated with CCS 6.1.3 I found that when run under Windows 7 CCS automatically created and used a ccsOjbs.opt linker options file when the command line for linker would exceed the maximum allowed Windows command line - see ccsObjs.opt File?

    What is the full version of CCS you are using, and which version of Windows?