Because of the holidays, TI E2E™ design support forum responses will be delayed from Dec. 25 through Jan. 2. Thank you for your patience.

  • State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 52 subscribers
  • Views 667 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.

CCS/TMS320F28335: Building with external makefile does not export the active configurations

Johan Eriksson50
Prodigy 250 points
Part Number: TMS320F28335

Tool/software: Code Composer Studio

Hi!

When I create a CCS project and deselect "Use default build command" and "Generate Makefiles automatically" I do not seem to be able to acquire the name of the active configuration (such as Debug, Release, or what ever I decide to name it). It is important to get this information since CCS assumes that I put the artifacts into a folder with the same name, so I need to be able to put them there in my custom build script. The intuitive solution would be an exported environment variable, such as ACTIVE_CONFIGURATION=Debug.

I tried to define it automatically with some arbitrary named variable from the view -> Project Properties -> Build -> Variables, but they don't seem to be exported either.... Which seems very counter intuitive in itself.

Is there a work around and will you implement this feature through preferably both functions mentioned above?

BR,

~Johan

  • 0
    TI__Guru**** 173310 points

    Johan Eriksson50 said:
    When I create a CCS project and deselect "Use default build command" and "Generate Makefiles automatically" I do not seem to be able to acquire the name of the active configuration (such as Debug, Release, or what ever I decide to name it).

    When you de-select "Generate Makefiles automatically" the Variables button should become enabled. You should be able to click on it and select a variable. I think config_name might be the one you are looking for. 

    I found an Eclipse reference on it here: https://help.eclipse.org/kepler/index.jsp?topic=%2Forg.eclipse.cdt.doc.user%2Freference%2Fcdt_u_prop_build.htm

    Hope this helps.

  • 0 in reply to AartiG
    Prodigy 250 points

    Hello AartiG!

    Do you mean that I should populate the field "Build command" or the field "Build directory" with this variable?

    I tried populating both of these fields, but none of them seem to work. It did not register. Is it maybe the wrong variable?

  • 0 in reply to Johan Eriksson50
    TI__Guru**** 173310 points

    Johan Eriksson50 said:
    Do you mean that I should populate the field "Build command" or the field "Build directory" with this variable?

    I thought you were looking to populate the "Build directory" with a path that makes use of the variable (that resolves to the name of the build configuration).

    Perhaps you could try the ConfigName variable. 

    Personally I haven't tried such a scenario myself as I work more with the managed make environment that uses the auto-generated makefiles.
    Also, for general Eclipse questions like this you might even find some good tips on the internet from other users who may have tried something similar.

  • 0 in reply to AartiG
    Prodigy 250 points
    Hi!

    No, I just want to have a way of accessing the configuration name from within my external script. I do not want to tamper with CWD.

    However, it seems that the ConfigName variable actually gets populated, so I was able to solve this by appending the build command with OUTDIR="${ConfigName}"

    I am fairly sure that this works as intended from a fresh Eclipse CDT, but I would need to verify it.


    Thanks for the help!
    ~Johan