• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 54 subscribers
  • Views 317 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.1 clean behavior of dependent projects

gbl
Intellectual 400 points

It seems that the clean behavior of dependent projects has changed in CCS5.1.09000 (at least compared to CCS5.1.05000).

Let's assume we have project A which makes use of libraries built in projects 0 and 1. The dependencies are mentioned in the project settings of project A.

Until now the 'clean project' command for project A this deleted all object files of projects A, 0 and 1 (because A depends on 0 and 1). Now it seems that the object files of project A only are deleted.

Is that intentionally? The behavior is a little strange as the 'build project' command builds projects 0 and 1 if required.

  • 0
    TI__Genius 15780 points

    Hi, 

    The behaviour has changed as you discovered. We felt that it is more accurate that clean apply to selection as libraries (i.e. dependent projects) would change less frequently. Is this behaviour causing an issue in your environment? One option that I have today is that doing a clean from Project menu allows you to clean all projects in your workspace. If your workspace contains main project and only dependent projects then that would be one way of doing a clean of all projects. 

     

    Martin

     

  • 0 in reply to MartinS
    Intellectual 400 points

    Hi,

    behavioral aspects are always difficult to judge as they rely on personal habits. I have to admit that I got used to the current procedure and thus the new one is irritating for me (although I am sure one can get used to it).

    The logic to keep the old behavior is that what applies to build (where dependent projects are built) should also apply to clean.

    The logic for the new behavior is that with destructive processes like clean one better is more cautious than with constructive processes like build (minimize possible damage caused by unintentional activity).

    In most cases your proposal to work with the workspace will help. An additional option is to keep those projects closed that shall not be touched.