When building a project as a dependency of another project, its currently active configuration is built regardless of the main project's settings.
To reproduce, follow these steps:
I think these problems also manifest when the workspace was inherited from a previous CCS version but they are less visible and harder to replicate, hence the request in step 1 to start with a fresh WS.
I have been unable to reproduce exactly as you described. I have followed your steps and found that the configuration that gets built is as expected. However, for me in step 8 proj2 was not built, however I did find following your steps it also did not build project 1 saying "nothing to build" . So I will look into this and thanks for flagging that.
I will get back to you with any feedback as soon as possible but please note the holidays mean there should be some delays in responses.
I have been doing more digging myself and do not seem to see a bug. what triggered the message is simply that I forgot CCS had previously built the release configuration and if no file changes then CCS will not rebuild. Can you try doing a clean before following your steps to see any difference?
I found out why you couldn't reproduce the bug. The bug does not happen when right clicking on the project and selecting "Build Project", but only when invoking the keyboard shortcut bound to "Build Project". There is no such binding by default, so create one: Window > Preferences > General > Keys, scroll down to Build Project and bind it to some keyboard combination. Now follow the steps in the original message, using your keyboard shortcut whenever it says to build.
There is one more bug I've found that is also easy to reproduce. For this one it doesn't matter whether you use the keyboard binding or not:
This may seem like a trivial inconvenience but is in fact very problematic when dealing with a large project that takes a long time to build.
By the way, since I've mentioned keyboard bindings, the "Watch" keyboard command would have been very useful but does nothing. (There are two commands by that name, neither works.)
Thank you and happy new year,
I have actually tracked this to a known bug SDSCM00045990.
You should be able to track this using the following link:
Sorry for the inconvenience and all the best with development.
Thanks, I will follow that bug. However, please note my last message, I have noted another bug that happens regardless of whether you use the keyboard binding. I also mentioned another keyboard binding that does not work at all (Watch). Please direct your attention to these issues as well.
thanks for all the feedback. Regarding the no need to build. This looks like it is because separate folders and hence .out copies are kept for each project and each build configuration. This is why CCS doesn't know about the .out. I am looking into watch binding and can file something if/as appropriate.
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.