• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 53 subscribers
  • Views 1000 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.

CCS/CCSTUDIO: Files generated during pre-build step do not get built

Kyle Altendorf
Prodigy 200 points
Part Number: CCSTUDIO

Tool/software: Code Composer Studio

I have a prebuild step which generates several .c and .h files.  This runs but those new files are not compiled during the first build.  If I build again then they are detected and compiled.  The 'simple' workaround is to keep the generated files in revision control so they are always present when the build launches but that's not preferable.

Is there any integrated-into-the-build way to run a custom external script prior to scanning for source files to compile?  Or, is there a way to trigger a re-scan during a build?

Cheers,

-kyle

  • 0
    TI__Guru**** 464431 points

    Hi Kyle,

    There is no clean solution for this. Please see the below thread for how one user implemented a workaround:

    https://e2e.ti.com/support/tools/ccs/f/81/p/733570/2708533#2708533

    Note that my initial suggestions were not enough, hence read the thread to completion on the next page.

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 200 points

    Thanks for the quick response, Ki.  I read through the linked issue and it seems that your final suggestion was to stop using the integrated managed build?  We have some interest in that anyways since dealing with the GUI is a hassle, but not yet.  The asker's solution was just to manually add the compilation of those files to the pre-build steps.  Unless I missed something about your comment "Ah, ok. Yes you need to specify the source files"?

    It would be nice to have an _actual_ pre-build step.  :]

    Cheers,

    -kyle

  • 0 in reply to Kyle Altendorf
    TI__Guru**** 464431 points

    Kyle Altendorf said:
      I read through the linked issue and it seems that your final suggestion was to stop using the integrated managed build? 

    That is one option, especially if you are comfortable working with makefiles directly. But the user in that thread ended up manually building those files as a post build step, which is also a very viable workaround.

    Another workaround that came to mind is a custom build command using the Scripting Console. Have that command run a *.bat/*.sh script first that will generate the files, then have it call the buildProject console command. You can have the custom command callable via a menu item.

    Kyle Altendorf said:
    It would be nice to have an _actual_ pre-build step.  :]

    If we could change the behavior of when the currently supported pre-build step runs, that is the ideal solution.

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 200 points

    Ki said:
    Kyle Altendorf
    It would be nice to have an _actual_ pre-build step.  :]
    If we could change the behavior of when the currently supported pre-build step runs, that is the ideal solution.

    Is this something controlled by TI code or by the underlying Eclipse code?  If the latter then I could take it up with them.

    Cheers,

    -kyle

  • 0 in reply to Kyle Altendorf
    TI__Guru**** 464431 points

    It is something we inherit from Eclipse CDT