A CMake build platform and dependency provider with reusable CI 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 (xpinit, xpupdate, 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 xpInit, 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 a CI workflow to intialize things
3. Make small modifications to existing CMake (or introduce CMake)
4. Use other org repos as reference implementations (see the externpro projects table: https://github.com/externpro/externpro/blob/main/cmake/README.md)
5. Start building and delivering your projects on multiple OSes, architectures, and compilers - creating packages that can be consumed by other projects quickly and consistently!
6. Read the core overview in externpro
7. 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