• State Resolved
  • Locked Locked
  • Replies 9 replies
  • Subscribers 98 subscribers
  • Views 842 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.

CCS5: Should I store config.bld under version control?

David Aldrich
Expert 1345 points

Hi

I am building a portable project using CCS5.03. The project files are stored in Subversion.  Another developer sees the following build error:

Error: Can't find import file: 'C:/SVNProj/MyProj/trunk/Source/PingTest/.config/xconfig_cpsw_example/config.bld'
(not found along 'D:\MyProj\tags\MyTag\.config\xconfig_cpsw_example/; <snip>) config.bld /PingTest/.config/xconfig_cpsw_example line 3 C/C++ Problem

I am wondering whether I was correct in putting config.bld under version control as it appears to be auto-generated.  However, another developer, who has a similar environment to mine, did need it.

Should I store config.bld under version control?

If not, how does another developer generate it?

David

  • 0
    TI__Mastermind 26780 points

    David,

    I think that file is auto-generated as part of the project build. (You’ll probably see “/* THIS IS A GENERATED FILE -- DO NOT EDIT */” at the top of the file.)  It should be regenerated if you clean the project and rebuild.  

    If you want to snapshot the project “as built”, it can be saved in version control.  

    If other developers will be checking out the project and then routinely rebuilding it, then it does not need to be saved.

    Does this help?

    Scott

  • 0 in reply to ScottG
    Expert 1345 points

    Hi Scott

    Thanks for answering my question. Yes, config.bld does indicate that it is auto-generated. But if I delete it and do a clean build I get error:

    C:\TI\ccsv5\utils\gmake\gmake -k all

    gmake: *** No rule to make target `<mypath>/.config/xconfig_cpsw_example/config.bld', needed by `configPkg/compiler.opt'.

    gmake: Target `all' not remade because of errors.

     

    Please can you suggest how to fix this?

    David

  • 0 in reply to David Aldrich
    TI__Mastermind 26780 points

    Does your makefile have a “clean” target?  Can you do this:

     gmake clean

     And then try the:

     gmake –k all

     If there is no clean target then I think you could also try:

     gmake --always-make

    Does this work?

    Scott

  • 0 in reply to ScottG
    Expert 1345 points

    Sorry, I haven't tried running gmake. I always build from the GUI.  (Although I am familiar with makefiles).

    How do you run gmake?

  • 0 in reply to David Aldrich
    TI__Mastermind 26780 points

    I missed that you were building with the GUI.  

    If you right click on the project (in the Project Explorer view), you can select “Clean Project”.  This should be right below “Build Project”.  Then after cleaning, invoke “Build Project”.

    Scott

  • 0 in reply to David Aldrich
    Expert 1345 points

    Hi Scott

    What happened was that part of my message got lost, leaving only the gmake command and the error.  I think its because I am using IE9, or maybe its a bug in the forums.

    Anyway, the bottom line is that I deleted config.bld, cleaned the project and then did make, all using the GUI. Then I saw in the console window:

     

    C:\TI\ccsv5\utils\gmake\gmake -k all

    gmake: *** No rule to make target `C:/SVNProj/Orione/trunk/Source/PingTest/.config/xconfig_cpsw_example/config.bld', needed by `configPkg/compiler.opt'.

    gmake: Target `all' not remade because of errors.

     

    So a clean build is not generating config.bld. Do you have any thoughts about this please?

     

    David

  • 0 in reply to David Aldrich
    TI__Mastermind 26780 points

    David,

    OK, thanks.  I asked around, and think I know what is going on now.  Some older versions of CCS have a bug during project creation where a reference to the config.bld in that .config directory gets added to the project build options. 

    The .config directory is used as a temporary work area for the graphical tool.  These files should *not* be referenced in the actual project build, and should *not* be stored in your source control system. 

    If you look in the project build options (right click on the project, select Properties->XDCtools->AdvancedOptions), you will probably see a reference to that config.bld in the .config directory in the “Build configuration file (-b)” box.  If you delete this reference (clear the contents of the box), and save and clean and rebuild the project, the error should go away.  We tried this here and it worked, but I’m not positive it will for your particular install.  The ultimate fix for this project creation problem is to update to a later version of CCS.

    Please let me know if this works around the problem.  If it does not, please clean the project, and post the complete build output shown in the console window.  If you can’t post all the output, the command line shown after the “'Invoking: XDCtools'” line is the important one.

    Thanks,
    Scott

  • 0 in reply to ScottG
    Expert 1345 points

    Hi Scott

    The situation was exactly as you described and is now fixed. I have also removed the .config folder from version control.

     

    Which version of CCS 5 would you recommend? (we are using 5.0.3)

    David

  • 0 in reply to David Aldrich
    TI__Mastermind 26780 points

    David,

    OK, good, thanks.

    I'd recommend moving to the latest CCS 5.1 release.

    Scott