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

CCSv4 Portable Projects and Command Line Build

Andreas Zoufal
Intellectual 305 points
Other Parts Discussed in Thread: CCSTUDIO

Hello,

I', trying to port our huge development environment from CCS 3.0/3.3 to CCSv4. We use DM642 and DM648 processors currently, and we have very much projects to build. Everything is stored in a Subversion repository and used by different developers.

In this scenario, we need 2 features:
a) portable projects (no absulte pathes anywhere in the projects),
b) one-button-build for all projects using batch/script files (for automated builds too)

Feature a) looks good for the moment, I use this Wiki article: http://tiexpressdsp.com/index.php/Portable_Projects. For feature b) I'm playing with the commands described in article http://tiexpressdsp.com/index.php/Projects_-_Command_Line_Build/Create. And here is one problem I cannot resolve: the command needs the project name AND the workspace. But the workspace is not stored in the Subversion repository, and every developer has his own place for this, therefore I cannot define a global script for this.

The question is, is there a smart and easy-to-implement-solution for this issue? With CCS 3.0/3.3 I have simple batch files, to run this files developers only open a DOS box, run DosRun.bat from the desired CCS version (typically within a link lie "%comspec% /k "C:\CCStudio\DosRun.bat""), change to the working folder ant run the script. Any idea?

Kind regards,
Andi

---

Exaple for CCS3.0/3.3 command line within build.bat

...

timake ..\..\Modules\SRTC\C64\SRTC_C64.pjt Debug
timake ..\..\Modules\SRTC\C64\SRTC_C64.pjt Release

timake ..\..\Modules\OFI\C64\OFI_C64.pjt Debug
timake ..\..\Modules\OFI\C64\OFI_C64.pjt Release

timake ..\..\Modules\MSG\C64\MSG_C64.pjt Debug
timake ..\..\Modules\MSG\C64\MSG_C64.pjt Release

...

 

  • 0
    TI__Guru**** 465901 points

    Andreas Zoufal said:

    For feature b) I'm playing with the commands described in article http://tiexpressdsp.com/index.php/Projects_-_Command_Line_Build/Create. And here is one problem I cannot resolve: the command needs the project name AND the workspace. But the workspace is not stored in the Subversion repository, and every developer has his own place for this, therefore I cannot define a global script for this.

    The question is, is there a smart and easy-to-implement-solution for this issue? With CCS 3.0/3.3 I have simple batch files, to run this files developers only open a DOS box, run DosRun.bat from the desired CCS version (typically within a link lie "%comspec% /k "C:\CCStudio\DosRun.bat""), change to the working folder ant run the script. Any idea?

    Could you not use an environment variable  in the *.bat file? That way everyone can have their own definition of the variable (which points to their workspace location) in their environment while the *.bat file would be generic/portable.

    ki

  • 0 in reply to Ki
    Intellectual 305 points

    Ki,

    Yes, you are right, this might be the solution for now.

    For the future, I guess it would be nice to have smarter solutions. One idea: maybe it will be possible to export portable makefiles from the project(s) which can be saved in the repository (in parallel to the project description files) and used nativly by gmake?

    Kind regards,
    Andi