stefankoelle/marcer-gamedvd-launcher
1
0
Fork 0
mirror of https://github.com/skoelle/marcer-gamedvd-launcher.git synced 2026-09-17 18:50:25 +00:00
Code Issues Packages Projects Releases Wiki Activity

fix release pipeline

Browse Source
This commit is contained in:
stefankoelle
2026-08-10 21:31:39 +02:00
parent d06ee381be
commit 87720e6db4
4 changed files with 27 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+8 -9
View File
@@ -75,16 +75,15 @@ A performant, consistent console launcher for the Hatari emulator on Windows. Co
## Usage
1. Edit `launcher.config.example.json` to set your `RootDirectory`, optional `PatchDirectory` and the `Hatari` settings, then copy it to `launcher.config.json` for local use. Relative paths are resolved against the EXE folder (build output).
2. **Windows:** Build via `build.cmd`.
3. **Linux:** Build via `build.sh` (run `chmod +x build.sh` first to make it executable).
4. **Always start using `start.cmd`.**
5. In the console, all subfolders and ZIPs in root (and recursively below) will be shown; other file types/hidden files are always ignored.
6. Complete navigation/control with arrow keys, Enter, Backspace, ESC, PgUp/PgDn, as described above.
7. **IMPORTANT:** Navigation/scroll/backspace:
2. **Windows:** Build via `build.cmd`, start via `start.cmd`.
3. **Linux/macOS:** Build via `build.sh` (run `chmod +x build.sh` first to make it executable), start via `start.sh`.
4. In the console, all subfolders and ZIPs in root (and recursively below) will be shown; other file types/hidden files are always ignored.
5. Complete navigation/control with arrow keys, Enter, Backspace, ESC, PgUp/PgDn, as described above.
6. **IMPORTANT:** Navigation/scroll/backspace:
- Backspace never escapes the root
- In root, Backspace has no effect
- Empty directories are reported (display stays stable)
8. **Overlay/patch logic:**
7. **Overlay/patch logic:**
- If a ZIP/folder exists in both patch and main, always the patch version opens/launches
- All navigation is relative to root path—for consistent experience
@@ -139,8 +138,8 @@ Releases are automated via GitHub Actions. When a tag matching `v*` is pushed, t
4. The GitHub Action handles the rest.
**Local builds** (for development/testing):
- **Windows:** `build.cmd`
- **Linux/macOS:** `build.sh` (run `chmod +x build.sh` first)
- **Windows:** `build.cmd` to build, `start.cmd` to run
- **Linux/macOS:** `build.sh` to build, `start.sh` to run (run `chmod +x *.sh` first)
## Community