• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 53 subscribers
  • Views 860 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.

CCS: build configuration folder

Guy Mardiks
Genius 4135 points

Tool/software: Code Composer Studio

Hello,

I am working with CCS projects and use the "generate makefiles automatically" option. 

The problem is that when choosing the above option i am NOT allowed to change the build location and as a result every build configuration have a different build location that is fixed to the configuration's name.

I have searched a lot and so far was not able to find a way to change the build location.

I also considered using a post build script but the problem is that the build configuration folder is still used by the CCS process even during the post build, making it impossible to delete/rename the build folder.

I would appreciate your help so that i am able to change the build configuration folder or at least some way to automatically rename or copy to another location & delete it after the build is done .

Thanks

Guy

  • 0
    TI__Guru**** 173310 points

    Guy Mardiks said:
    The problem is that when choosing the above option i am NOT allowed to change the build location and as a result every build configuration have a different build location that is fixed to the configuration's name.

    Correct. This is the default behavior set by Eclipse for managed make projects that "generate makefiles automatically" and cannot be changed.

    You can certainly copy the contents of the folder to another location in a post-build, but I'm not sure why you are looking to delete the build configuration folder after the build is done.  

    You can also control where certain build output files get placed ( like .obj, .asm, .out etc) using compiler/linker options. But in order to have full control over the makefiles and their location you would need to go with a custom makefile approach rather than a managed make approach.