• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 99 subscribers
  • Views 309 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.

CCSTUDIO: System project variables and postSteps

Martin Otzen
Intellectual 902 points
Part Number: CCSTUDIO

Hi

I recently added a system project to our dual core build.

I wanted to move the post steps up into the system project, but this post step is mainly about copying some output files fro the build into another folder.

However i fail to find a suitable variable to define the location of the build folder of the included sub projects. 

And I can't see that it is possible to export variables from dub-project to system-project.

The system-project does have the knowledge of the sub-project location and the active build-configuration, and in the end it's all defined i the same system.xml file.

I am seeking something that looks something like this.

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<system>
    <project configuration="@match" id="project_1" name="GrandProject_CPU1"/>
    <core id="C28xx_CPU1" project="project_1"/>
    <project configuration="@match" id="project_2" name="GrandProject_CPU2"/>
    <core id="C28xx_CPU2" project="project_2"/>
    <postBuildSteps>
        <step command="cp ${PROJECT_1_BUILDFOLDER}\fw1.bin ../outfolder" />
    </postBuildSteps>
</system>

as a minimum

<step command="cp  ../GrandProject_CPU1/${BUILD_CONFIG__1}\fw1.bin ../outfolder" />`

Is this possible?

And yes I could hard-code the path, but it would break if user changes build config.

  • 0
    TI__Guru**** 464181 points

    Hello,

    Martin Otzen said:
    However i fail to find a suitable variable to define the location of the build folder of the included sub projects. 

    Yes, I believe this is a known limitation. We do have plans to improve system projects and I believe this may be something we plan on adding. I will need to follow up with engineering.

    Thanks

    ki

  • 0 in reply to Ki
    Intellectual 902 points

    Hope engineering has something to add :-)

    I can add this

    I did find a variable getting close the "SYSTEM_EXECUTABLES" that is an array with the path to the two .out files. So if I could just strip the filenames, I would have the path's.

    Do you know if eclipse/CCS variable reference/expansion has some extra features like the the Gnu-make variables does, especially the "$(dir names…)" link ?

  • +1 in reply to Ki
    TI__Guru**** 464181 points
    Ki said:
    I will need to follow up with engineering.

    As per engineering:

    They can use the “ccs_eval_var” function to evaluate variables in another project.  The format is ${ccs_eval_var:/<project-name>/<variable-name>}.  For example, to resolve the build-directory location in a project named “myLib” - ${ccs_eval_var:/myLib/BuildDirectory}.  This would resolve to the absolute path to the build-directory in project “myLib”.

  • 0 in reply to Ki
    Intellectual 902 points

    Hi

    This is indeed usable, Though I would prefer something like the "SYSTEM_EXECUTABLES" Where I don't have to hardcode the names and count of sub-projects. But I guess that's for a future release.

    However to complete this request, could you tell if there is any doc on this ccs_eval_var thing, it sounds as something that could come in handy in other places?

    I was not able to find any doc on it myself, neither google, not TI-Search could find anything (Partly due to TI-search insisting on ignoring the underscores ans search for "ccs eval var" instead)

  • 0 in reply to Martin Otzen
    TI__Guru**** 464181 points
    Martin Otzen said:

    However to complete this request, could you tell if there is any doc on this ccs_eval_var thing, it sounds as something that could come in handy in other places?

    I was not able to find any doc on it myself, neither google, not TI-Search could find anything (Partly due to TI-search insisting on ignoring the underscores ans search for "ccs eval var" instead)

    I do not believe this is explicitly documented anywhere. It is hidden functionality. However, it is pretty useful and it is something that we will look to document in the future.