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.

How to run CCS 4.1 generated makefile?

I need to generate six near identical output files for the six cores of a C6486 and am trying to find a way to automate the process (same source files, only the external memory base address changes). Creating 6 separate projects is silly, a maintainence nightmare and should be totally unnecessary since all the source files are the same or can be adapted by a-D define passed to the *.TCF file (controls the external memory address). 

The easiest solution is to create a batch file that calls the CCS4 generated makefiles 6 times but passes a different -D for each call. However, CCS4.1 makefiles do not want to work outside of the CCS environment. What do I need to add/set to make things behave?

Thanks,

Calvin

  • Calvin,

    What about creating separate project configurations?  

    Create Debug1...Debug6.  Right click on the tcf file and select properties, select C/C++ Build on the left then add a -D to the command line, click apply, change the configuration in the dropdown at the top of the dialog and repeat.

    I will see if there is a way to set the active configuration from the scripting console.  If there is you could create a little function that would loop through and build each configuration and then launch the debugger for you.

    There is also a way to build the CCS projects outside of Eclipse if you need to do that: http://tiexpressdsp.com/index.php/Projects_-_Command_Line_Build/Create

     

    Regards,

    John

  • Unfortunately I could not find a way to set the active configuration from the scripting console.  I filed a request for this: SDSCM00035255  

    Did you have a chance to take a look at the command line build facility for projects?

     

    john

  • Creating separate projects or configurations is just the nightmare I am trying to avoid. I want to automate the process not create more work (thought it does not have to be automated within CCS).  I'm looking at the command line functions but this seems overly complicated. Ultimately CCCS calls gmake. I also just want to call gmake but from a cmd.exe window not part of CCS. We have to post process the .out files anyway to get them into a form they can be loaded from our host processor.

    So let me restate the question. CCS4.1 sets a number of environment variables before its call to gmake to make sure gmake finds everything it needs. What are those environment variables and what do I need to set them to so I can call gmake outside of CCS? I had better luck when I tried this in CCS4.0. What changed between 4.0 and 4.1?

  • Just to let you know I have asked someone else reply with info on how to use the generated makefiles.

  • John,

    I found the problem. My path was picking up the cygwin gmake (v 3.81) and not the TI installed version (3.78). Apparently the generated make files don't work reliably with the latest gmake 3.81. By copying the TI version into my local directory I am now able to re-run the generated makefiles.

     

    Thanks for checking into this!

    Calvin

  • Calvin,

    Thanks for letting us know.  I will mark your post as the answer just in case anyone else runs into the same issue.

    Regards,

    John