What is your question?

I'm using the workspace template (generated from conan new workspace) to explore workspaces with a super-install. When using this template, do I have ensure that add_project() calls must be ordered such that dependencies are declared before they are used?

For example when using the stock workspace template, if I move the add_project(app1) from below add_project(libb) to above it, it will fail to build. The "conan workspace super-install" will complete, however the following call to "cmake --preset conan-release" will fail because it can't find the libb package.

For a large project cmake does a reasonably good job of building the dependency tree such that add_subdirectory() calls do not have be in a specific order. Is there a way to use conan workspaces with a super-project to accomplish this?

In the above setup I'm using Ubuntu 22.04, Conan 2.19.0 and cmake 3.25.2.

Have you read the CONTRIBUTING guide?

• I've read the CONTRIBUTING guide