Action to build ModOrganizer 2 components within Github workflows.
Example usage:
name: Build UI Base
on:
push:
branches: master
pull_request:
types: [opened, synchronize, reopened]
jobs:
build:
runs-on: windows-2022
steps:
- name: Build UI Base
uses: ModOrganizer2/build-with-mob-action@master
with:
mo2-third-parties: fmt gtest spdlog boost
mo2-dependencies: cmake_common
The action must be run on windows-2022
since MSVC is required.
The following options should be specified most of the time:
mo2-third-parties
- List of project to build withmob
before anysuper
task, e.g.,fmt
,spdlog
,boost
,pybind11
, etc.- these dependencies are cached between runs depending on the latest release of
mob
.
- these dependencies are cached between runs depending on the latest release of
mo2-dependencies
- List of MO2 components to build before the current one.- these components will be built using
mob
and the current branch (when possible), e.g., if the current branch isdev-branch
, components will be built on thedev-branch
branch (if available) ormaster
otherwise. - these builds are not cached between runs.
- these components will be built using
The following options are not mandatory but can be used to customize the build:
mo2-branch
- The branch to build, default to the current branch.mo2-cmake-command
- The CMake command to run withmob cmake
, default to..
(same asmob
).qt-install
- Default is'true'
, set to'false'
to disable installing Qt (build will most likely fail unless Qt is installed before running this action).qt-version
- Version of Qt to install. Default is to use the version defined bymob.ini
in themob
repository.qt-modules
- List of extra Qt modules to install.