Add build process #1

Open
opened 2026-05-11 00:49:28 +00:00 by AmbientImpact · 0 comments
AmbientImpact commented 2026-05-11 00:49:28 +00:00 (Migrated from codeberg.org)
  • Download pre-built Featureful binaries (DLLs, SOs, etc.); currently developing against the 2026-05-05 release
  • Also download files we don't need to have committed like delta.lst (it's unmodified)
  • Add build-to-game target:
    • rsync files to the game directory (or selectively cp?)
    • Run each campaign's setup.sh

For the build-to-game target, an important question is whether we should first delete the files we know our setup.sh will create to ensure it's continuously verified to work? I'm leaning towards adding a variable to the setup.sh files (false by default?) that tells them to clean and start from scratch, leaving other files intact (such as saved games, user configs, etc.).

- [x] Download pre-built Featureful binaries (DLLs, SOs, etc.); currently developing against [the `2026-05-05` release](https://github.com/FreeSlave/halflife-featureful/releases/tag/featureful-2026-05-05) - [ ] Also download files we don't need to have committed like `delta.lst` (it's unmodified) - [x] Add `build-to-game` target: - [x] `rsync` files to the game directory (or selectively `cp`?) - [x] Run each campaign's `setup.sh` For the `build-to-game` target, an important question is whether we should first delete the files we know our `setup.sh` will create to ensure it's continuously verified to work? I'm leaning towards adding a variable to the `setup.sh` files (false by default?) that tells them to clean and start from scratch, leaving other files intact (such as saved games, user configs, etc.).
Sign in to join this conversation.
No milestone
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
unforeseen-consequences/featureful-campaigns#1
No description provided.