Project Tick is a modular ecosystem of tools including MeshMC (Minecraft launcher), MNV (editor), and supporting infrastructure.
Product versions
- Actions = N/A
- CGit = 10.0.3
- CMark = 0.31.2
- CoreBinUtils = 10.0.3
- ForgeWrapper = ProjT
- GenQRCode = 4.1.1
- Hooks = 10.0.3
- images4docker = 10.0.3
- Json++ (json4cpp) = 10.0.3
- LibNBT++ = 3.1
- MeshMC = 7.4.0
- Meta = 10.0.3
- MNV = 10.0.3
- NeoZIP = 10.0.3
- Toml++ = 10.0.3
- Website = 10.0.3
MeshMC / Project Tick Monorepo
Highlights
- Major build system stabilization across CMake, CI, and monorepo library handling
- Full Nix integration with derivations for all Project Tick components
- Transition toward system-provided dependencies and cleaner packaging model
- Improved library bundling strategy and source archive consistency
- Compression backend migrated from zlib to neozip
Changelog
Added
- Nix derivations for all Project Tick projects
default.nixandshell.nixfor flake compatibility- CI steps for installing cxxtest on Linux and macOS
- Support for building and installing monorepo libraries (including neozip and vcpkg dependencies) in CI
- CMake support for collecting binary directories from
CMAKE_PREFIX_PATH - Additional CMake configuration for handling monorepo library bin paths
ldconfigstep to refresh dynamic linker cache for shared libraries- README documentation for bundled libraries
Changed
-
Reworked GitHub Actions to support flexible library bundling and cleanup
-
Refactored artifact naming in MeshMC workflow (removed Qt6 suffix)
-
Updated CMake configuration to:
- Use dynamic build types in CI workflows
- Improve Release build handling
- Resolve headers from installed system packages
- Support multi-config generator mappings
-
Dependencies are now assumed to be system-provided instead of bundled by default
-
Library integration model updated to allow independent compilation of subprojects
-
Replaced zlib with neozip for compression
-
MeshMC source tree reformatted for consistency
Fixed
- Issues with missing binary paths for monorepo libraries during build/link stages
- CI inconsistencies related to dependency installation and build configuration
- General CMake configuration inconsistencies affecting multi-platform builds
Removed
- Legacy assumptions around bundled dependencies in favor of system-based linkage
- Redundant or conflicting commits (cleanup via targeted revert)