BYOS: build your own stack

A CMake build platform and dependency provider with reusable CI (continuous integration) pipelines. Reproducible builds. Reusable dependencies. Consistent CI. Fewer "works on my machine" surprises.

externpro standardizes toolchains, dependencies, and CI workflows across developers, machines, and repositories—so teams ship faster with less drift and duplication.

1. externpro (core) 🧰 CMake build platform + dependency provider model + reusable workflows (xpsync, xpbuild, xptag, xprelease).

2. buildpro (Linux toolchain images) 🐳 Linux Docker build images used by externpro-enabled repos to keep compilers/tools/system deps consistent.

3. tutorial (adoption walkthrough) 🎓 Vendor externpro as a .devcontainer submodule, run xpSync, follow xpTag → xpBuild → xpRelease, and consume externpro-produced deps via find_package().

1. Add externpro as a submodule to your project — the tutorial walks through the exact steps
2. Run the bootstrap script to set up the xpro branch, copy workflow templates, and configure externpro
3. Verify the setup works locally with cmake --list-presets and cmake --preset=<platform>
4. Run the xpSync workflow to sync externpro and open a PR that standardizes presets, workflows, and repo wiring
5. Use other org repos as reference implementations (see the externpro projects table: https://github.com/externpro/externpro/blob/main/cmake/README.md)
6. Start building and delivering your projects on multiple OSes, architectures, and compilers - creating packages that can be consumed by other projects quickly and consistently!
7. Read the core overview in externpro
8. Review the foundational patterns in buildpro

Most repositories in the organization act as reference implementations—examples of integrating externpro and using the workflow as intended. See the externpro projects table: https://github.com/externpro/externpro/blob/main/cmake/README.md