• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 54 subscribers
  • Views 1181 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 Eclipse v6.1.0.x: Facing strange build issues after creating a new "Build Configuration" from an existing one.

Vijay Pothukuchi
Prodigy 545 points


I have a project fir building a CCS library for C6xx multi-core device. I have the default Debug and Release configurations on the project and last week I tried to create a new 'build configuration' for profiling by going through "Manage Configurations --> New --> Existing configuration". The original Debug/Release configuraions continue to build correctly but the new one I tried to create bails out with an error "No tool found that can build the extension specified with the build artifact name all". I checked the makefiles and they don't seem to have been generated correctly.

I used the exact procedure in the past and never had issues. The only difference was that in the past I used this method for the project building executable but not libraries but I don't think it should matter. I must be doing something fundamentally wrong but can't figure out where.

I did a quick search in the forum for any past posts on this but did not come across. It is likely that I did not search thoroughly in which case please point me to the relevant thread and I will take it from there.

Thanks,

Vijay

  • 0
    TI__Guru**** 472451 points
    Hi Vijay,
    I can reproduce the issue. I assume in your original configuration, you are using a custom name for the file extention, like .l66 vs the default .lib. While changing the name of the extension works in the default configs, it seems to cause a problem in custom ones. I'll continue to look at this and update you as I find more information.

    Thanks
    ki
  • 0 in reply to Ki
    TI__Prodigy 545 points
    Thanks Ki. The library name not being the default '.lib' could be causing this issue. I went back and looked at what else was different from what I did in the past and the extension is one thing that stood out.

    Let me know if you find a workaround. For what I am doing now, I need to live with extension '.oe66'.
  • 0 in reply to Vijay Pothukuchi
    TI__Guru**** 472451 points
    I filed a bug for this. Tracking ID: CCDSK-1990

    One workaround is to modify the .cproject. Another option to is use the default .lib extension and then run a post build step that will rename the .lib to .oe66. The latter is preferred (to me).

    Thanks
    ki
  • 0 in reply to Ki
    TI__Prodigy 545 points

    Thanks Ki. I looked at the last option you mentioned and this is what I started doing yesterday. The issue I had was that we have two build systems (pure command line based build system and the Eclipse IDE based one). I need to change the command line system to generate ".lib" version to match the Eclipse IDE based one. This is needed so that the linker command file (same linker command file shared between these two builds) rules for placing the code/data sections at specific memory locations match the symbols and the library names generated. Renaming the libraries would definitely work but the corresponding MAP files generated will have names different from the actual library name. I guess this is OK as long as we document what's going on.

    Let me know as soon as a solution is available. Until then I will have this temporary solution in place.

    Thanks for your time.

    Regards,

    Vijay