• Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 183 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.

Custom module build flow

Clement FR
Genius 4750 points

Hello everyone,

(target C6678, CCS 5.5, BIOS 1.25, XDCTools 3.25)

I now use custom modules (for example : a specific Timestamp implementation)
but I build them directly with the command line xdc all.
Totally outside of Eclipse.

I also have a project application inside Eclipse that use the custom module.

What I would like to do is, inside Eclipse:
if the custom module was modified, rebuild it and then build the application.
else don't rebuild the custom module and simply build the app.

How can I do it ?

Thank you,
Clement

  • TI__Mastermind 37985 points

    Clement,
    there is no support in CCS for referencing non-CCS RTSC packages. However, I have a method that works for me, so you may want to try it.
    The 'xdc' command is really a gmake shell, and it will behave just like gmake. If your custom module was modified, 'xdc' will rebuild your package, otherwise it will quickly exit. Now, you just need to run 'xdc' in your non-CCS package before building your CCS project. To do that, you can use Project Properties->CCS Build->Steps and then enter something like this in the text field Command for Pre-build steps:
    C:/ccsproducts/xdctools_3_25_03_72/xdc.exe -P C:/temp/idioms/i204

    Your path and the XDCtools version will be different, but you get the idea. The option -P means that the xdc command will build the package found in the given path. I have a package idioms.i204 in the repository C:/temp, so create your path for your non-CCS package accordingly. Check this page for more info about various -P options: http://rtsc.eclipse.org/docs-tip/Command_-_xdc

  • in reply to Sasha Slijepcevic
    Genius 4750 points

    Hello Sasha,

    I wanted to see if there was another way than pre-build steps.

    I had my command in a batch file (.cmd) so I simply put the file path as the pre-build step and it works.

    For anyone else reading, here's a good resource :

    http://processors.wiki.ti.com/index.php/Projects_and_Build_Handbook_for_CCS#Pre_and_Post_Build_Steps

    Thanks.

    The tip about -P is useful too.

    Clement