Skip to main content

Why esys-conan

LibESys libraries and esysrepo share the same third-party Conan graph: Boost, Poco (XML-only), OpenSSL, libxml2, xmlsec, zlib, expat, libiconv, and related options (layouts, disabled Poco components, openssl pins).

Without a shared tool, every repository would duplicate:

  • Conan remotes and Artifactory login
  • Boost / Poco / OpenSSL / xmlsec option sets
  • Manual “seed Artifactory” jobs so CI can download binaries instead of compiling Boost on every pipeline
  • Shared vs static package ids for a Go-style fat esysrepoexe (third-party linked in; only the OS C/C++ runtime remains dynamic)

esys-conan is that shared CLI and Python package:

esys-conan publish boost --profile linux-ci --layout versioned --linkage both
esys-conan publish esysrepo-deps --profile linux-ci --linkage both

Lib repos depend on esys-conan for remotes and option helpers instead of copying conan_tooling.py.

What this site shows​

The package matrix lists only packages that esys-conan publish seeds on artifactory.libesys.org (not first-party esys* packages). Green check = Release binary present for that platform and linkage; red cross = missing.