How to set the default "build configuration"?

Hi Jeff,

have you tried the following.

Select the project.  Right-click and go to Build Configurations->Manage.  Set the one you want as "default" to be the active configuration.  It should then still be the active configuration next time.

Give that a try and keep us informed.

Best Regards,

Lisa

Hi Lisa,

Thanks for your suggestion.  This is correct as long as you operate from the same workspace.  I guess I wasn't exactly clear enough.  The real problem is when a user copies my project into their workspace.  We keep our projects in a repository, and so often project are imported into other people's workspaces, used and then deleted when they are done.

When a different user or a different workspace is used with the same project copied out of the repository, the original (first) configuration seems to alwys be selected. 

This requires them to select the active configuration in order for it to work.  In this case, my project will not build upon import of the project into their workspace because the RAM configuration is selected by default in the "new" workspace, and RAM doesn't build any more.

The users don't necessarily know this, and they will tell me my project is broken!

What they need to do is to manually go into Build Configurations -> Set Active and select "Flash".  Once they do that they can build just fine from that point forward.  

I am simply looking for a way to choose that as the primary method so that the users don't keep telling me that my project won't build and me having to explain to them that they need to first change the build configuration.

Once it is set correctly, there are no issues in that workspace - it is just when the project is introduced to a workspace.

I hop this is clearer?  Thanks for the suggestion though - I appreciate the quick response!

-Jeff

Hi Jeff,

so am I correct in understanding you use source control?  Let me look into this for you with some more expert colleagues.  If you do use revision control, what system?  What gets checked in/out with what permissions?

Best Regards,
Lisa

Hi!

Yes - we are using GIT as our source control system, and we check everything in/out including .cproject, .ccsproject, .project, .settings, .cmd liner files, .ccxml files and gel files - (in addition to sources!)

The mechanism is that we can build and run any of our projects on any machine regardless of location, arch, etc.  So we are pulling down the complete workspace (minus the build areas).

Permissions are user level - we control access to git that way.  When a user checks a project out, all files will be owned by that user.

-Jeff

Baltasar,

we are having the same issue, using ClearCase instead of GIT. However, your suggested solution does not work. Whenever I create a new workspace from the repository and import the projects to become visible, one of the projects always starts with the debug configuration, but not with the desired release configuration. Here's my version of the .ccsproject file:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<?ccsproject version="1.0"?>

<projectOptions>
<deviceVariant value="com.ti.ccstudio.deviceModel.TMS470.GenericARM9Device"/>
<deviceEndianness value="little"/>
<codegenToolVersion value="4.9.1"/>
<isElfFormat value="true"/>
<connection value=""/>
<templateProperties value="id=org.eclipse.rtsc.project.templates.EmptyRtscConfiguration,buildProfile=release,"/>
<deviceFamily value="TMS470"/>
<defaultConfiguration value="Release"/>
</projectOptions>

CCS 5.2.1.0008 just seems to ignore that value. Are there more settings I need to provide/adjsut for the release configuration to make that defaultConfiguration entry work?

Thanks and best regards
Stefan

Hi Stefan,

I would, if possible, very strongly recommend using the latest released version, v5.3.   Do not update but install a full fresh installation to a clean simple directory like c:/myccs as an example.

You may well find the issue fixed and/or the work around will work in a later version.

Please keep us informed how that goes.

Best Regards,

LIsa

Lisa,

thanks for the suggestion. However, in the current phase of the project we need to postpone an upgrade to v5.3. May I put your attention to the following:

Our ARM solution consists of two projects, one holding the code, the other contributing some configurable settings. The "code" project has a dependency to the "config" project. Astonishingly, CCS v5.2.1 comes up with the "Release" configuration instead of the "Debug" configuration for the "code" project upon creating a new workspace from ClearClase. But the "config" project behaves differently. When changing the configuration, the "config" project obviously does not change any file within its repository.

So I am wondering how the "code" project manages to come up with the desired "Release" configuration, and how we can adopt this to the "config" project.

Any recommendations are welcome.

Best regards
Stefan

Hi Stefan,

As Lisa had mentioned, it would be best to upgrade to the newest CCS as soon as you can - CCS v5.4.0 would be released soon, so you may wish to skip 5.3.0.

But, until you're able to upgrade, is there a reason you're using CCS v5.2.1.00008?  Maybe it was just a typo on your part - the GA build is 5.2.1.00018.  I've just verified that the <defaultConfiguration> element in the .ccsproject file does work in CCS v5.2.1.00018.

- Baltasar

Baltasar,

you're right, that's a typo. We are using CCS 5.2.1.00018.

Thanks for verifying that the "defaultConfiguration" element should work. Referring to my post as of March 21, did I enter the element at the correct position? I actually made the exercise with having the "defaultConfiguration" within the project options and beneath that block, but no success.

Does the "defautConfiguration" depend on other settings I have not activated accidentally?
Could you possibly post a sample .ccsproject file (or the one you used for verification) for reference?

Thanks and best regards
Stefan

Stefan,

No, the exact position of the element, within the root element, is not important.  And no, its behaviour does not depend on any other settings.  As long as you have CCS v5.2.1.00018 (or newer), it should work.

You mentioned that it does work for your "main" project, but not for the "config" project.  Your "config" project - is it a RTSC Configuration project?  If it is, does it actually have a "Release" build-configuration?  Because by default, all RTSC Configuration projects have only one build-configuration named "Default".  Did you manually create a build-configuration named "Release" for that project?

- Baltasar

Baltasar,

as all other projects have a "Debug" and "Release" configuration, I deleted the original (but unused) "Release" configuration of the "config" project and renamed its "Default" configuration to "Release" – just to preserve the configuration's settings and to avoid manual copying. I then attempted to make that renamed "Release" configuration the default instead of (the automatically chosen) "Debug" configuration, but the patched ".ccsproject" did not work.

Did I chose an inappropriate approach? Should I better stay with the original "Default" configuration and declare this one the default in the ".ccsproject" file?

And yes, the "config" project is a RTSC Configuration project.

Thanks and best regards
Stefan

Hallo,
I have simmilar problem (I thing). I have problem with activating DEBUG-mode (and debugging). I use CCS 5.2.1.00018.

I have 2 simmilar projects. In one of them there no problem witch swiching between Release and Debug mode (Project->Build Configuration->Set Active). In another one I have no item 'Debug' (after selecting [Project->Build Configuration->Set Active])  so I can't select it. I have commpared both projects and I haven't find difference in configuration. I haven't find also option where I could add (or activate) Debug mode. Mayby somebady could give information how to add to project
Debug mode (and activate it).
I appreciate any advice you may have for me.
Pawel