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.
Hi,
I want to assemble programs which use similar components by linking identical libraries to different projects. That all for different configurations in a command line build environment.(2 Programs lib_test_main1.out and _main2.out, both using libraries lib_test_print1.lib and _print2.lib, first clean everything, then do incremental builds for Release and Debug configuration). Example project and output are attached.
What I see is that:
For the first (Release) configuration everything works as expected. For the second (Debug) configuration there is a lot on unnecessary clean and rebuild action, which extends the build time. Uncommented, filtered output in real_life_build.txt, comments about what I would expect in expected_build.txt.
Can you please give me a hint how to remove the additional clean builds and to use existing libraries instead of re-building them again?
(Splitting the clean builds between the releases is not a solution - the real application is even more complicated with with a 6 projects * 2 configurations * 2 other_parameters matrix, where one of the 24 configurations shall be build first as a touchstone build, with 11 of the remaing 23 later, thus a total clean at the beginning should be most efficient).
I've opened a CQ to track this problem - SDSCM00041269 Unnecessary builds in CCS5 when using command line builds for different configurations. I will look into addressing this for CCSv5.1.0 M8 (beta2).
Thanks,
- Baltasar
Thank you for starting to investigate this.
If you offered a solution in CCSv5.1.0 M8 (beta2) it would be great to have one for the thread "Unwanted .project file modifications in CCS5.1.0.06000" as well (because this new behavior in CCS5.1.0.06000 also prevents us from upgrading at the moment).
Hi,
can you confirm that a correction for this problem made it to CCS5.1.0.08000?
No, no fix has been implemented for this problem yet. You should be able to track the status of the CQ using the "Bug tracking" link on the left-hand side menu on this page.
- Baltasar
It seems that even in Code Composer Studio v5.1.0-M9 (Release Candidate) this problem is not solved yet. When will this be the case?
This problem's root cause is in the Eclipse/CDT platform, so it is not easily fixable. I am looking into this currently, trying to implement a workaround. I will let you know once I have any news on this.
Thanks,
- Baltasar
FYI - the solution to this problem requires that a couple of bugs first be fixed in the Eclipse Platform. I've submitted a patch to fix these - https://bugs.eclipse.org/bugs/show_bug.cgi?id=361675. Until this patch is accepted by the open source community, there is no workaround for this problem, unfortunately.
- Baltasar
Thank you for following these issues. I hope there will be improvements in Eclipse soon and TI can use them for CCS. Please continue to watch this.
FYI - our Eclipse patch has been accepted for Eclipse 3.7.2. This issue is now fixed in the upcoming CCSv5.2.0.
- Baltasar