Are Project's Dependencies not stored in project?

[photon3108]

If I remove project from workspace, project's dependencies setting also lose.

Sometimes I need to change the projects of workspace so it is important to me.

If project can store its dependencies, I don't need to select them again at next

time.


How to store the setting?

[oBFusCATed]

There is no way to do this (I think).
The dependencies are stored in the workspace file.

By the way, I also think that is the wrong place to store them  :lol:
Here is an example that shows the problem with this approach:

We have 4 projects libA, libB, appA and appB.
We have the following dependencies:
libB depends on libA
appA depends on libB
appB depends on libB

appA and appB are in separate workspaces

With the current approach the user have to set the dependencies of libB (depends on libA) in the workspace for appA and appB.
And if something changes (another lib is added) should redo the work in both workspaces again.
And this was just a simplified example, in practice there 10-20 libs and 10-20 apps (my current project at work is such one).

Storing the dependencies in the *.cbp file will enable C::B to automatically add the missing lib projects to the current workspace or to show an error message that some project can't be opened