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.

  • Resolved

CCSv5 command line compile not generating makefile

Prodigy 70 points

Replies: 3

Views: 1909

I am trying to turn our IDE project into a command line build using Nant. I am getting stuck because the makefile is not being generated. The .project, .cproject, and .ccsproject files are in source control and downloaded with the source code before calling the builder. Here is the relevant Nant output:

     [exec] Starting 'c:\ti\ccsv5\eclipse\eclipsec (-nosplash -data "C:\tidcs\AV-900 Upgrade\DC Controller\TestBuild" -application com.ti.ccstudio.apps.projectBuild -ccs.autoImport -ccs.projects "M3 ARM" -ccs.configuration Flash)' in 'C:\tidcs\AV-900 Upgrade\DC Controller\TestBuild'
     [exec]
     [exec] %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
     [exec] CCS headless build starting... [Wed Jan 23 16:58:03 PST 2013]
     [exec] %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
     [exec]
     [exec] ================================================================================
     [exec] Pre processing...
     [exec]
     [exec]
     [exec] ================================================================================
     [exec] Building...
     [exec]
     [exec]
     [exec] **** Build of configuration Flash for project M3 ARM ****
     [exec]
     [exec] C:\ti\ccsv5\utils\bin\gmake -k all
     [exec] gmake: *** No rule to make target `all'.
     [exec]
     [exec] **** Build Finished ****
     [exec]
     [exec]
     [exec] ================================================================================
     [exec] CCS headless build complete!
     [exec] C:\tidcs\AV-900 Upgrade\DC Controller\TestBuild\AV900.build(195,4):
     [exec] External Program Failed: c:\ti\ccsv5\eclipse\eclipsec (return code was 1)

It says it can't find target 'all', but the directory shows that makefile and the associated *.mk files were created with file size zero (empty). The ccsObjs.opt and ccsSrcs.opt file seem to be ok. When I compile from the IDE workspace using the same project file set, it generates the makefile. The build workspace is separate and created on the fly with autoImport used to add the project files to it. The auto generate makefiles options is set in the project file according to the IDE.

Any ideas on what the problem might be? This is the first time I've tried to set up command line script compilation.

Thank you

  • Hi Raymond,

    I just completed doing something similar using the following inside of a batch file (located in the WorkSpace):

    ECHO Building ALL CCSv5 projects in workspace

    eclipsec -verbose -noSplash -data "%cd%" -application com.ti.ccstudio.apps.projectBuild -ccs.workspace

    @note: Of course the project has to build in CCSv5.

    A single project in the same batch:

    eclipsec -verbose -noSplash -data "%cd%" -application com.ti.ccstudio.apps.projectBuild -ccs.projects %1 -ccs.configuration Debug

    Also, I learned a lot about issues with spaces in the path & filenames; which may be your issue.

    I know its a completely different environment (not Nant) but it may be of some help.

  • Guru 328635 points

    Raymond,

    Raymond Virzi
    The build workspace is separate and created on the fly with autoImport used to add the project files to it.

    If you try to do a command line build using the same workspace as when building from the IDE, does that work?

    Thanks

    ki

    -----------------------------------

    Did you read the CCS Forum Guidelines & FAQ? If not, PLEASE read it. If you haven't read it in awhile, please read it again to see if any updates were made.

    Having CCS problems? Check out the CCS Troubleshooting Guide

    Looking for CCS Training/Documentation? Check out the CCS Resources page

    Curious about the status of a bug and know the tracking ID? Track it via the public bug tracking portal

    NOTE: When a bug is filed and a tracking ID is provided, the thread may then be suggested as "TI Thinks Resolved". Why? Please read the first FAQ of the CCS Forum Guidelines & FAQ

  • In reply to Ki:

    (Logging in from my home account)

    I should have re-posted that I found the problem. The .settings directory was in source control and we being pulled in as read only files. The makefile creation failed because it could not update the core preferences file. I simply removed the .settings files from source control and it worked. It turns out the build works just fine without them.

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.