2025-02

The file names have the format

mumble_env.<triplet>.<build date>.<commit hash>.<extension>

• <triplet> specifies the vcpkg target triplet used. The same triplet must be specified as -DVCPKG_TARGET_TRIPLET when using these pre-built environments.
• <build date> is the date at which the env has been compiled
• <commit hash> is the hash of the vcpkg commit the env was built from. Note that this commit identifies a commit in this repository (the fork) and not a commit in the upstream Microsoft repository.
• <extension> specifies the type of archiving and compression used on the environment. This determines how you'll have to decompress the archive.

Important notes

• These environments contain only Release libraries. Thus, on platforms where Release and Debug builds are not ABI compatible (Windows) you can only use these for Release builds.
• These environments were built making use of overlay triplets that overwrite the standard triplets. Hence, libraries may not be compatible with externally built vcpkg libraries even though the triplet name is the same.

What changed?

• Updated all dependencies to latest versions available on vcpkg
• Switched from Qt 5 to Qt 6
• Include only subset of Boost libraries
• Introduce Mumble-specific overlay triplets
• Updated macOS deployment target to 13.0
• Windows archive no longer contains spurious PDBs

2024-07 (Qt 6)

The file names have the format

mumble_env.<triplet>.<build date>.<commit hash>.<extension>

• <triplet> specifies the vcpkg target triplet used. The same triplet must be specified as -DVCPKG_TARGET_TRIPLET when using these pre-built environments.
• <build date> is the date at which the env has been compiled
• <commit hash> is the hash of the vcpkg commit the env was built from. Note that this commit identifies a commit in this repository (the fork) and not a commit in the upstream Microsoft repository.
• <extension> specifies the type of archiving and compression used on the environment. This determines how you'll have to decompress the archive.

Important note

These environments contain only Release libraries. Thus, on platforms where Release and Debug builds are not ABI compatible (Windows) you can only use these for Release builds.

What changed?

• Updated all dependencies to latest versions available on vcpkg
• Switched from Qt 5 to Qt 6

2024-05

The file names have the format

mumble_env.<triplet>.<build date>.<commit hash>.<extension>

• <triplet> specifies the vcpkg target triplet used. The same triplet must be specified as -DVCPKG_TARGET_TRIPLET when using these pre-built environments.
• <build date> is the date at which the env has been compiled
• <commit hash> is the hash of the vcpkg commit the env was built from. Note that this commit identifies a commit in this repository (the fork) and not a commit in the upstream Microsoft repository.
• <extension> specifies the type of archiving and compression used on the environment. This determines how you'll have to decompress the archive.

Important note

These environments contain only Release libraries. Thus, on platforms where Release and Debug builds are not ABI compatible (Windows) you can only use these for Release builds.

What changed?

• Updated all dependencies to latest versions available on vcpkg
• Ready up for the database rewrite in the Mumble server
  • Removed Qt database related dependencies
  • Explicitly added SQLite3, PostgreSQL and MySQL libraries

2023-12

The file names have the format

mumble_env.<triplet>.<build date>.<commit hash>.<extension>

• <triplet> specifies the vcpkg target triplet used. The same triplet must be specified as -DVCPKG_TARGET_TRIPLET when using these pre-built environments.
• <build date> is the date at which the env has been compiled
• <commit hash> is the hash of the vcpkg commit the env was built from. Note that this commit identifies a commit in this repository (the fork) and not a commit in the upstream Microsoft repository.
• <extension> specifies the type of archiving and compression used on the environment. This determines how you'll have to decompress the archive.

Important note

These environments contain only Release libraries. Thus, on platforms where Release and Debug builds are not ABI compatible (Windows) you can only use these for Release builds.