CMake and CI about azure-sdk-for-c HOT 4 CLOSED

I feel like having each project have its own build folder is the best approach. We do this with other monorepos already. The build pipeline will be able to publish build artifacts from all of the different build folders.

from azure-sdk-for-c.

The most important things are to have your dependencies that will live in the same monorepo export targets (with install(EXPORT)) and make sure that you always create an alias target so that you can use the project the same way if you found it "on the system" with find_package as you can from the build tree.

I think we'll want a central core repo pretty fast, and that can demonstrate this.

from azure-sdk-for-c.

@bsiegel which option do you prefer?
@barcharcraz what's the best practice for CMake and multiproject repo?

from azure-sdk-for-c.

For cmake monorepos it's common to do both. The example cmake file in #2 is designed so that you can call add_subdirectory from a parent folder and it will behave nicely.

Also: the build folders can be anywhere you want, and for the CI machines I would make them totally outside of the checked out repo (especially since they CI may build multiple different configurations)

from azure-sdk-for-c.