Move to VCPKG

[Holt59]

Move to VCPKG

Note: I consider this branch the next master branch for (hopefully) 2.6.0 release. Once everything is stable, this branch will replace the master branch.

Here are the changes integrated (or to be integrated) into this branch:

• Move to VCPKG (see below)
• SemVer versioning from Move to semver versioning for MO2. #154
• New extension system from WIP: Extensions #129

---

Move to VCPKG

Use vcpkg instead of mob to obtain dependencies for uibase.

• Bring mo2-cmake (CMake utilities, old cmake_common), spdlog and gtest from VCPKG
  • spdlog from MO2 registry to remove fmt dependency and force use of std::format
• The dependency on boost-algorithm has been removed because
  • the only two functions used were iequals and ireplace_all,
  • adding boost-algorithm to VCPKG dependency requires ~100 packages due to the way Boost is packaged with VCPKG, so this was substantially increasing build time for uibase.
  • iequals and ireplace_all have been implemented and encapsulated.

Proper CMake Targets

Refactor code to generate proper CMake targets, the goal is to be able to do find_package(mo2-uibase) to obtain proper targets to link to.

In order to obtain "clean" targets, the following has been done:

• Move headers file to include/uibase directory at root
• Add CMake stuff to generate config files for uibase

The following can be used to configure, build and install uibase without external dependencies (except Qt):

# - QT_ROOT_DIR should be set/replaced to match actual Qt installation
# - UIBASE_TESTING will add tests
# - CMAKE_INSTALL_PREFIX can be set to anything where the target should be installed
cmake --preset vs2022-windows `
            "-DCMAKE_PREFIX_PATH=${env:QT_ROOT_DIR}\msvc2019_64" `
            "-DCMAKE_INSTALL_PREFIX=install" -DUIBASE_TESTING=ON

# it is possible to build targets in all configurations
cmake --build vsbuild --config Debug --target uibase-tests --verbose
cmake --build vsbuild --config RelWithDebInfo --target uibase-tests --verbose

# tests can be run without any extra configurations (Qt DLLs, etc.)
ctest --test-dir vsbuild -C Debug --output-on-failure
ctest --test-dir vsbuild -C RelWithDebInfo --output-on-failure

# targets can be installed properly
cmake --install vsbuild --config Debug
cmake --install vsbuild --config RelWithDebInfo

To use uibase in a CMake project, one can simply:

1. Add install/lib/cmake to CMAKE_PREFIX_PATH (where install is the location set when configuring uibase).
2. Use find_package(mo2-uibase CONFIG REQUIRED) to find uibase
3. Link to uibase with target_link_libraries(mytarget PRIVATE mo2::uibase)

Note: Since header files have bee reorganized, one should use #include <uibase/XXX.h> instead of #include <XXX.h> (or #include <uibase/game_features/FFF.h> for game features). To avoid having to update all existing projects, one can use set(MO2_CMAKE_DEPRECATED_UIBASE_INCLUDE ON) before find_package(mo2-uibase) to make all headers available.

Automated Release on Tag

When a Github tag is published, a new release will automatically be made.

• Use these release in VCPKG registry to fetch uibase.
• Check the tag against version.rc or something like that.