In the package manager code, CMAKE_PREFIX_PATH and CMAKE_MODULE_PATH have a special treatment. They are forwarded to the project and are forwarded to users too.

However, there's also CMAKE_FRAMEWORK_PATH and CMAKE_APPBUNDLE_PATH that are useful on mac.

Then, we have <PackageName>_DIR that could also be forwarded, which is useful when we want to force a path for a dependency.

As the title says.

When cloning a package, the only action needed should be subgine-pkg install. Right now, running subgine-pkg setup is mandatory, but should not be.

You can specify custom CMake arguments when building dependency using profiles, but relative path are not forwarded correctly as of right now.

There should be a whitelist of arguments that should be transformed into absolute path when passing down to dependencies.

Commands such as install or update should regenerate the generated profile code if the manifest has changed since last invocation.

The generated profile need some code to find files in each dependencies. Those dependencies are listed, hard coded in the generated file. If a user is adding a new dependency, that list is not updated.

We could regenerate the profile file, or generate a new file with only the set of dependency since last invokation. The latter is my preferred solution.

We currently use the same dummy project to find dependencies for all profile. An argument that affect the cache (such as compiler) will bleed on other profiles.

Furthermore, you can screw the cache using only one profile by setting an argument and then remove it.

We should have one dummy project by profile and clean it if the profile arguments has changed.