• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 52 subscribers
  • Views 1572 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CCS4: Output Build Folders & File Specific Options

John Wilkes
Expert 1315 points

Hello,

 

I have recently converted a C2x project from CCS v3.3 to v4.2. The exercise was successful but I have found the following annoyance: my project has four configurations and when built, the output build folders appear in the project folder with the same name as the configuration. This is fine, but a little untidy. I would like a single sub-folder in the project folder called ‘Build’ and the output build folders (named as the configurations) as subfolders of this. I had this scheme working in V3.3 but cannot seem to make V4.2 do it – anyone have any ideas?

 

Also I, too, ran in to the problem discussed in this post:

 

http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/57598/205238.aspx#205238

 

This thread was ‘resolved’ by filing ‘SDSCM00037412’ (I assume some kind of bug report). Is there any further news on whether this problem has been addressed? And how? Personally, I quite like the way that v3.3 handled file specific options – by presenting them as relative changes to the standard project options. It was easy to see which options have been changed for a specific file. In CCS V4, even if the bug didn’t exist and all project level option changes where propagated down correctly, it is still hard to see which options are different for the ‘triangled’ files.

 

Cheers,

 

John.

 

 

 

 

 

 

 

  • 0
    TI__Guru**** 173310 points

    John Wilkes said:
    I would like a single sub-folder in the project folder called ‘Build’ and the output build folders (named as the configurations) as subfolders of this. I had this scheme working in V3.3 but cannot seem to make V4.2 do it – anyone have any ideas?

    You can specify the location for the compiler/linker generated files such as the .obj, .map and .out using the Project Build options in CCS, however I have not found a way to change the location for the Eclipse generated files such as makefiles, .opt files etc. This is always set to the default project build directory which is a sub-folder within the project folder with the name of the build configuration (\Debug, \Release etc), and I have not found a way to change this.

    The defect SDSCM00037412 is fixed and scheduled to be in CCS release 4.2.2.

  • 0 in reply to AartiG
    Expert 1315 points

    Aarti,

    Thank you for your reply, that is pretty much the conclusion I came to too. I look forward to getting 4.2.2.

    Cheers,

    John.