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.

TMS320F28377S: Builders do not persist through git commits

Part Number: TMS320F28377S
Other Parts Discussed in Thread: CCSTUDIO

I want to add a builder as part of the compilation setup.

I am able to select a .bat file, send in arguments and see the compilation work with it.

However, I am not able to commit the ccstudio files (.cproject, .project) to a branch, checkout that branch on a new git clone and use the same builder.

This is the error i get: 

Im guessing this is due to the path of the .bat file not being saved.  

Any ideas?

Thank you!

  • Hi Alex,

    Can you share the three .*project files in your project folder?

    Thanks

    ki

  • Here is my .ccsproject file:

    [removed]

    the .cproject file is very long and is the actual compilation itself.  

    for .project file (the one i think that needs to be modified)

    This is what gets added (green highlight on the right) when i make a new builder in ccstudio.

    [removed]

    Please let me know if you need me to provide more information!  Thanks!

  • Can you add the files to a zip and post the zip to this thread?

  • My work would rather me not send out the full files due to privacy concerns.

    Although i dont think that would be needed/super helpful to have the extra files.

    All i am trying to do is save a builder that calls a .bat in a .*project file and then someone else would be able to checkout the same code and have the builder work for them.  For what its worth, the .*project files could be a blank canvas.



    I notice that when i add a builder, it only saves some configuration the .project file.  What it saves isnt enough to persist between different setups.

  • The reason why I asked for the files is that with those three files, I can import the project to my workspace to take a closer look. I won't be able to build the project since I will be missing the source, but I will be able to see the project properties as you see it in the IDE.

    You can start a private E2E conversation with me if you wish to share privately.

  • I have an idea.  I can use a public repo to replicate the issue.

    https://github.com/sal0w/CC3200-Ultrasonic-sensor-HC-Sr04

    So, if i open ccstudio and add a builder to this project (the bat file is just a bunch of echoes):

      ->

    I notice that it ONLY changes the .project file.  (.cproject and .ccsproject stay the same).

    Here is the new .project file (With the builder added) (e2e not letting me upload but here is the diff:

    However, if i attempt to make a fresh clone, and move the .bat file and .project file to the fresh clone i get the Invalid External Tool Builder

  • However, if i attempt to make a fresh clone, and move the .bat file and .project file to the fresh clone i get the Invalid External Tool Builder

    You also need to copy over the .externalToolBuilders folder. This has the additional launch file for prebuild_builder

  • I think that worked!  Let me double check

  • You will also likely need to update the path to the bat file, which likely points to the first project.

  • Yep, i set it to use ${git_work_tree}\myfile.bat so it works for all

  • Thanks for the help Ki!



    Funny enough, the issue is that we use gitignore.io and for eclipse it automatically makes git ignore the .externalToolBuilders folder & *.launch files.

    That public repo i used doesnt use gitignore and i was more clearly able to see that ccstudio updated that .externalToolBuilders folder.