Release binary compile options

[MeteorsLiu]

matrix

The Matrix design mechanism is primarily implemented to provide diversified build configurations for pre-compiled binaries. Its core architecture follows a key-value pair pattern:

matrix:
    k1: [v1, v2, v3...]
    k2: ....

Common configuration dimensions include:
os (target operating system platform)
arch (target processor architecture)
type (build variant such as debug/release)

Compiler

Default to clang.

The decision to configure clang as the default compiler strategically mitigates matrix dimension explosion caused by multi-compiler compatibility requirements.

Cross-toolchain support would induce exponential expansion of the build parameter matrix's combinatorial space, substantially escalating configuration maintenance complexity.

Problem

It should be noted that matrix configurations may lead to combinatorial explosion, resulting in significantly divergent binary artifacts.

To effectively manage build scale, the matrix mechanism must be strictly confined within a single software package, prohibiting cross-package propagation.

When precise build variant specification is required, explicit declaration through -tags should be implemented.

[luoliwoshang]

Conan's pre-built binaries are packages built for specific OS, architecture, and compiler versions. For example, zlib/1.3.1 will only have one pre-built package per OS/architecture combination.

For macOS/ARM, the pre-built binary package can only be used if the compiler matches (e.g., Clang 13) and the build options are identical.

For instance, my local environment uses Clang 18, there is no pre-built package in remote repositories matching this compiler version and configuration matrix. Attempting to install it will result in an error:

llcppg/build on  main [$!?⇕] took 15s 
❯ conan install --requires=zlib/1.3.1 --output-folder=./build    

======== Input profiles ========
Profile host:
[settings]
arch=armv8
build_type=Release
compiler=clang
compiler.cppstd=gnu17
compiler.libcxx=libc++
compiler.version=18
os=Macos

Profile build:
[settings]
arch=armv8
build_type=Release
compiler=clang
compiler.cppstd=gnu17
compiler.libcxx=libc++
compiler.version=18
os=Macos


======== Computing dependency graph ========
Graph root
    cli
Requirements
    zlib/1.3.1#b8bc2603263cf7eccbd6e17e66b0ed76 - Cache

======== Computing necessary packages ========
Connecting to remote 'conancenter' anonymously
Requirements
    zlib/1.3.1#b8bc2603263cf7eccbd6e17e66b0ed76:204c7d3974815bb40393554da214035504965e71 - Missing
ERROR: Missing binary: zlib/1.3.1:204c7d3974815bb40393554da214035504965e71

zlib/1.3.1: WARN: Can't find a 'zlib/1.3.1' package binary '204c7d3974815bb40393554da214035504965e71' for the configuration:
[settings]
arch=armv8
build_type=Release
compiler=clang
compiler.version=18
os=Macos
[options]
fPIC=True
shared=False

ERROR: Missing prebuilt package for 'zlib/1.3.1'. You can try:
    - List all available packages using 'conan list "zlib/1.3.1:*" -r=remote'
    - Explain missing binaries: replace 'conan install ...' with 'conan graph explain ...'
    - Try to build locally from sources using the '--build=zlib/1.3.1' argument

More Info at 'https://docs.conan.io/2/knowledge/faq.html#error-missing-prebuilt-package'

To resolve this, Conan allows you to force local compilation using:

conan install --requires=zlib/1.3.1 --build=missing --output-folder=./build  

Therefore, maintaining a limited number of pre-built binaries for common configurations and relying on local builds by users for version/configuration matrix combinations outside this scope is a viable solution.