Community
Participate
Working Groups
Build Identifier: 3.23.00.29 1) The first time you create and build a project with CCS, the custom build flow behavior is correct. 2) As expected, building the project again results in a null re-make of the sysbios.lib. 3) Changing a BIOS .c file, and then building your project again yields the correct behavior (ie sysbios.lib is rebuilt). 4) The issue comes about if you change to a new version of SYS/BIOS. Problem A) invoking 'build' after switching to the new SYS/BIOS simply results in another null re-make of the sysbios.lib. No re-generation of the library occurs. Problem B) if you try to resolve Problem A by performing a 'clean' and then a build, two builds of sysbios.lib occur. The first one is simply a remake using the old makefile. The second occurs after the makefile gets regenerated due to the clean. Reproducible: Always Steps to Reproduce: 1. follow procedure described in 'Details' 2. 3.
I think the problem is almost* entirely in the hands of the BIOS makefile template: Problem A: changing to a different SYS/BIOS version requires a change to the package path. Since _everything_ in your build depends on the package path, the package path should be recorded in your generated makefile. If all your objects depend on your generated makefile, this should trigger a rebuild. Problem B: a clean should trigger your makefile to clean what it generated. A subsequent build should force your makefile to be regenerated (as part of the re-run of config) and re-run (to create the new libraries as expected). * There is an unmentioned problem with CCS: changes to the package path do not trigger a re-run of config.
CCS bug was reported as IncidentReport:SDSCM00042519
