-
Notifications
You must be signed in to change notification settings - Fork 113
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Added a separate .NET 6 Windows build because .NET 8 is not available on Windows 7/8
- Loading branch information
Showing
7 changed files
with
64 additions
and
62 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -3,14 +3,17 @@ name: Build Mesen | |
on: [push] | ||
|
||
env: | ||
# I'm not a fan of the telemetry as-is, but this also suppresses some lines in the build log. | ||
DOTNET_CLI_TELEMETRY_OPTOUT: 1 | ||
# This removes even more spurious lines. | ||
DOTNET_SKIP_FIRST_TIME_EXPERIENCE: 1 | ||
|
||
jobs: | ||
windows: | ||
strategy: | ||
matrix: | ||
platform: [ | ||
{netversion: 6.x, targetframework: net6.0}, | ||
{netversion: 8.x, targetframework: net8.0} | ||
] | ||
fail-fast: false | ||
runs-on: windows-latest | ||
|
||
|
@@ -23,26 +26,26 @@ jobs: | |
- name: Install .NET Core | ||
uses: actions/setup-dotnet@v3 | ||
with: | ||
dotnet-version: 6.x | ||
dotnet-version: ${{ matrix.platform.netversion }} | ||
|
||
- name: Setup MSBuild.exe | ||
uses: microsoft/[email protected] | ||
with: | ||
msbuild-architecture: x64 | ||
|
||
- name: Execute unit tests | ||
run: dotnet test -nologo | ||
- name: Restore packages | ||
run: dotnet restore /p:TargetFramework="${{ matrix.platform.targetframework }}" | ||
|
||
- name: Build Mesen | ||
run: msbuild -nologo -v:d -clp:ForceConsoleColor -m -p:Configuration=Release -p:Platform=x64 -t:Clean,UI | ||
run: msbuild -nologo -v:d -clp:ForceConsoleColor -m -p:Configuration=Release -p:Platform=x64 -t:Clean,UI /p:TargetFramework="${{ matrix.platform.targetframework }}" | ||
|
||
- name: Publish Mesen | ||
run: dotnet publish -nologo -c Release /p:Platform="Any CPU" /p:OptimizeUi="true" Mesen.sln /p:PublishProfile=UI\Properties\PublishProfiles\Release.pubxml | ||
run: dotnet publish -nologo --no-restore -c Release /p:Platform="Any CPU" /p:OptimizeUi="true" /p:TargetFramework="${{ matrix.platform.targetframework }}" Mesen.sln /p:PublishProfile=UI\Properties\PublishProfiles\Release.pubxml | ||
|
||
- name: Upload Mesen | ||
uses: actions/upload-artifact@v3 | ||
with: | ||
name: Mesen (Windows) | ||
name: Mesen (Windows - ${{ matrix.platform.targetframework }}) | ||
path: | | ||
build/TmpReleaseBuild/Mesen.exe | ||
|
@@ -73,16 +76,13 @@ jobs: | |
- name: Install .NET Core | ||
uses: actions/setup-dotnet@v3 | ||
with: | ||
dotnet-version: 6.x | ||
dotnet-version: 8.x | ||
|
||
- name: Install dependencies | ||
run: | | ||
sudo apt-get update -qy | ||
sudo apt-get install -qy libsdl2-dev # The compilers are already installed on GitHub's runners. | ||
- name: Execute unit tests | ||
run: dotnet test --nologo | ||
|
||
# stderr is not detected as a TTY, so diagnostics are by default printed without colours; | ||
# forcing colours makes the log a little nicer to read. | ||
- name: Build Mesen | ||
|
@@ -107,7 +107,7 @@ jobs: | |
- name: Install .NET Core | ||
uses: actions/setup-dotnet@v3 | ||
with: | ||
dotnet-version: 6.x | ||
dotnet-version: 8.x | ||
|
||
- name: Install dependencies | ||
run: | | ||
|
@@ -144,15 +144,12 @@ jobs: | |
- name: Install .NET Core | ||
uses: actions/setup-dotnet@v3 | ||
with: | ||
dotnet-version: 6.x | ||
dotnet-version: 8.x | ||
|
||
- name: Install dependencies | ||
run: | | ||
brew install sdl2 | ||
- name: Execute unit tests | ||
run: dotnet test --nologo | ||
|
||
# stderr is not detected as a TTY, so diagnostics are by default printed without colours; | ||
# forcing colours makes the log a little nicer to read. | ||
- name: Build Mesen | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,21 @@ | ||
Running Mesen through the Steam Deck's _Game Mode_ is possible with some caveats regarding rendering the UI. | ||
Due to Gamescope (SteamOS' compositor) not handling Avalonia UI's popups very well (a [solution](https://github.com/AvaloniaUI/Avalonia/pull/14366) is available but [has been reverted due to other issues](https://github.com/AvaloniaUI/Avalonia/pull/14573)), Mesen's menus for settings are not working through Gamescope unless running Mesen [through running KDE Plasma's Desktop through a script](https://www.reddit.com/r/SteamDeck/comments/zqgx9g/desktop_mode_within_gaming_mode_updated_for_new/). | ||
|
||
Installation instructions: | ||
* Download the **[Linux - AppImage](https://nightly.link/SourMesen/Mesen2/workflows/build/master/Mesen%20(Linux%20x64%20-%20AppImage).zip)** nightly build. | ||
* **Mark the AppImage as executable.** (right click > Properties > Permissions > Is executable) | ||
* Add the application as a non-Steam shortcut to be able to run it through Steam on both _Desktop Mode_ and _Game Mode_. (right click > Add to Steam) | ||
* Customise the non-Steam shortcut through Steam to your desire. (in Steam: search the AppImage's filename, right click > Properties; from there you can change the icon, shortcut name and launch options) | ||
* Create a folder called `Mesen.AppImage.Config` in the same directory where the AppImage is stored. | ||
* Run it the first time. When asking where to store the settings, choose the `Store the data in my user profile` option. ![254295455-88c1942d-b81f-48ee-a3a3-74b9f3ecd9b7-1](https://github.com/kevin-wijnen/Mesen2/assets/58944808/9f4ff1e3-4df6-4441-958b-ce96599ef69d) | ||
* Set up the controls as asked by Mesen. | ||
|
||
**Due to Gamescope not rendering the UI menus, it is recommended to bind some keyboard shortcuts to L4/R4/L5/R5 (the Back Grip Buttons).** You can rebind controls in _Game Mode_ by clicking the Controller icon. You can save the layout by clicking the Cog icon (next to `Edit Layout`) > Export Layout > select `New Template` as the Export Type to use it across multiple shortcuts. | ||
It is recommended to: | ||
* Bind `Control Key + O Key` to open the file picker for opening a game file. | ||
* Bind `Escape Key` to pause emulation. | ||
* Bind `F11` to enter in or out of fullscreen. | ||
|
||
**If sound does not work**, check if an audio device is chosen by Mesen. (in Mesen: Settings > Audio > General (Device)) | ||
|
||
**To make game-specific shortcuts**: Repeat the non-Steam shortcut step on the Mesen AppImage. Customise the new shortcut with a Launch Option (in Steam: right click > Properties; Launch Options). To find possible Launch Options, check the Command-line options menu (in Mesen: Help > Command-line options). When you want to supply a game with the shortcut, put the entire file location of the game in double quotes ("game-filepath") as the first part of the launch options. Add additional options (`--fullscreen` for example) _after_ the file location. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters