The simulator now also comes built without AVX2, its file name ending in _noavx2 (eu07-x64_<date>_<hash>_noavx2.exe, eu07_noavx2 on Linux), and both builds can lie side by side in the game folder. The automatic choice took eu07.exe or the shortest name and never that one, so a processor without AVX2 got a simulator that stops at its first instruction and a notice telling it to build its own. Without AVX2 the automatic choice now takes the newest _noavx2 build, even one through Wine before a native build that would not run. With AVX2 the build made for it stays first and a _noavx2 one is used only when it is all there is. The notice comes only when what would start still needs AVX2. With a _noavx2 build in the folder but another chosen by hand it names both and offers to go back to the automatic choice; with none it says what such a build is called and that the starter picks it up from the game folder.
StarterNG
Launcher for the MaSzyna train simulator, written in C# with Avalonia.
Building a native (NativeAOT) build
The project publishes as a self-contained NativeAOT binary — no .NET runtime is
needed on the target machine. The commands below are the same ones CI runs, see
.github/workflows/dotnet.yml.
Requirements:
- .NET SDK 9
- Linux: a native toolchain and zlib headers —
sudo apt install clang zlib1g-dev(Debian/Ubuntu) orsudo dnf install clang zlib-devel(Fedora) - Windows: the Visual Studio C++ build tools (Desktop development with C++)
Restore for the target runtime first, then publish:
dotnet restore StarterNG/StarterNG.csproj -r linux-x64
dotnet publish StarterNG/StarterNG.csproj \
-c Release -r linux-x64 --self-contained true --no-restore \
-p:PublishAot=true -p:PublishTrimmed=true \
-o publish/linux-x64
For a Windows build swap both linux-x64 occurrences for win-x64 (and the
line continuations for PowerShell backticks). NativeAOT does not cross-compile,
so the Windows package has to be built on Windows and the Linux one on Linux —
that is why CI uses a windows-2022 and an ubuntu-22.04 runner.
The output directory is the whole distributable: the Starter executable, the
Skia/HarfBuzz native libraries and startercfg/ with the translations and the
default key bindings. The .dbg (or .pdb) file next to it is debug symbols and
can be dropped from a release. Trim/AOT analysis warnings during the publish are
expected and do not fail the build.
CI builds both runtimes on every push and pull request to main and staging,
and on manual dispatch. Pushes additionally replace a rolling pre-release with
the packaged artifacts — tagged latest for main and staging for staging.
Development build
dotnet build StarterNG/StarterNG.csproj