• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 54 subscribers
  • Views 2901 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.

Command line build using CCS 5.1

Robert Coburn
Intellectual 470 points

Other Parts Discussed in Thread: CCSTUDIO

I am attempting to perform a command line build using CCS 5.1 but not having much luck, the output does not give me enough information to determine what is happening. It appears that absolutly nothing is happening.

 

I have read http://processors.wiki.ti.com/index.php/Projects_-_Command_Line_Build/Create#Working_with_CCSv5 as a starting place

 

Version information:

Code composer: 5.1.0.09000

OS Windows XP Service Pack 3

The problem may be due to the way I have my workspace set up. My project files are not stored in the workspace, rather the project is imported into the workspace. I have 4 projets in the workspace and have no problems building within the GUI, but when I attemp a command line build on a single project the output states the project is not in the workspace. It appears that I can not find any projects in the workspace whatsover. I get the same results  ( no indication of any action ) when I specify -ccs.workspace with no prioject specified, other than not getting the eror message about the project not being found.

C:\rtn\ti\coe-test>c:\rtn\ti\ccsv5\eclipse\eclipsec -noSplash -data "c:\rtn\ti\coe-test" -application com.ti.ccstudio.apps.projectBuild -ccs.projects DirectIO_Lib -ccs.clean

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
CCS headless build starting... [Mon Sep 10 10:20:44 CDT 2012]
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

================================================================================
Pre processing...


!WARNING: Project 'DirectIO_Lib' was not found in the workspace! Ignoring...
    NOTE: use the '-ccs.autoImport' argument to automatically import projects found in the workspace root directory.


================================================================================
Building...

 

================================================================================
CCS headless build complete!

C:\rtn\ti\coe-test>

Any assiastance will be appreciated

 

Bob Coburn

  • 0
    Expert 1575 points

    Hi Robert,

    I don't know if it helps... I'm also still a little bit confused about the command line build under CCS V5. I use the generated makefiles to build my application. On my main PC (where I work with CCS V5), I check the generated makefiles into the source management system as if they were sourcefiles. On the target PC (a buildserver), I checkout the sourcecodes and the makefiles. CCS V5 is also installed there, I use the command

    (CCS-Installpath)/utils/bin/gmake -C (sourcePath)/Debug -k all

    to build the project. This avoids handling Eclipse workspaces and it seems to work

    bye,

    Thomas

  • 0 in reply to Thomas9070
    Intellectual 470 points

    Thomas, Thanks for the suggestion. Turns out I had a typo of the command line and I was pointing to an empty worspace with a similar name. I have the eclipse interface working now

     

    Bob

  • 0 in reply to Thomas9070
    Expert 1575 points

    followup:

    it is important to mention that the generated makefiles contain absolute paths. So if you try to build on a different location the wrong sources will be used. I find using generated makefiles dangerous to get strange behaviour because source files are used that one does not expect.

    It seems that the way is to create a portable project and import it in an empty CCS workspace (use an empty directory). With that the relative path information will be correct. There is documentation here:
    http://processors.wiki.ti.com/index.php/Projects_-_Command_Line_Build/Create
    http://processors.wiki.ti.com/index.php/Creating_portable_projects_in_CCSv5

    It seems that a CCS workspace is more a storage for temporary files than something bound to a project. And that you can delete it between the builds. I thought that it has to be created first before you can build but it can be created by just importing an existing project.

    bye,

    Thomas