CCS/MSP430FR5969: ignores the eclipse variable “BuildDirectory”

Michael T Schneider

Tool/software: Code Composer Studio

Hello Team,

Ran into an odd problem today with CCS 8.2.0.00007 where it completely ignores the eclipse variable “BuildDirectory”. This is a problem because it pollutes the project directory with build artifacts. Is there a fix for this issue, am I missing something trivial?

Thanks!

Mike

over 7 years ago

0 AartiG over 7 years ago

TI__Guru**** 173310 points

Mike,

Could you provide some additional details?

Is this a regular CCS managed make project? And the build is placing the build artifacts (.obj, .out etc) in the root project directory instead of the build configuration directory?

Did this project build fine before and this issue just started happening? If so, could you try importing the project into a new workspace and see if that helps?
Also check the settings in the Project Properties->Build->Builder tab.

0 AartiG over 7 years ago in reply to AartiG

TI__Guru**** 173310 points

Mike,

Are you still facing this issue or have you been able to move past it? If it is still happening, could you please provide more details and if possible a simple project that demonstrates the issue?

0 AartiG over 7 years ago in reply to AartiG

TI__Guru**** 173310 points

This is being worked offline.

0 AartiG over 7 years ago in reply to AartiG

TI__Guru**** 173310 points

To summarize the offline discussion, the “BuildDirectory” variable is not used and cannot be changed by the user for default "managed make" build environment in CCS. In this case, the Build directory defaults to the <projectdir>/<buildconfigdir> and cannot be edited.

To have full control over the BuildDirectory and other details, a custom makefile approach is the recommended way to go.

0 Michael T Schneider over 7 years ago in reply to AartiG

TI__Expert 3790 points

Thanks Aarti for the support!

Code Composer Studio™︎

Code Composer Studio forum

CCS/MSP430FR5969: ignores the eclipse variable “BuildDirectory”