• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 52 subscribers
  • Views 1170 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.

CCSv5 RTSC library projects

Thomas S
Intellectual 600 points

I need to write my own RTSC libraries. Unfortunately there is no particular CCSv5 project type available yet for triggering the external xdc tool.
Since we use Subversion we do just check-in plein source files. So every developer has to rebuild the RTSC libraries in the process of rebuilding the project.
Unfortunately the xdc tool requires some absolute paths settings (build.cfg,XDCPATH,...) , which I have already set in my development project environment.

Is there a solution (in pipe-line)?

regards

Thomas

  • 0
    TI__Guru**** 451311 points

    Hi Thomas

    Thomas S said:
    Since we use Subversion we do just check-in plein source files. So every developer has to rebuild the RTSC libraries in the process of rebuilding the project.

    Is the need for a separate RTSC library project due to trying to avoid the constant rebuild of the RTSC libraries when building the main project?

    Thanks

    ki

  • 0 in reply to Ki
    Intellectual 600 points

    Hi Ki-Soo

    It is especially for constant rebuild. In my project, we write our own RTSC components. So far I create for this components a RTSC project in CCS and change to custom build and call the xdc tool suite with the following C++ build command: "${XDC_CG_ROOT}/xdc" --xdcpath="${XDCPATH}"

    The disadvantage: I still have to create the config.bld and package.bld file manually instead of beeing created automatically by the files/resources added to the project.

    Best regards

    Thomas