Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The current build process for building the fox32 suite of software (fox32asm, fox32rom, tools (gfx2inc), fox32os and the fox32 emulator) is a bit messy. The dependencies between projects are not documented too well and compatible versions between the tools (mostly fox32os, fox32rom and fox32asm) aren't very clear. The easiest way to figure out how to build all the software (IMO) is looking at the GitHub workflows.
I have added Nix Flakes to these tools, specifying dependencies to libraries and between themselves. I host the repositories at my own Gitea instance (githug.xyz) but they are mirrored at GitHub:
Most of these have an unmodified or lightly modified Makefile, and can be built without Nix just like before. All of them build, you can run
nix run github:xenia/fox32-mirror
(with needing to even clone the repo) ornix run github:xenia/fox32-mirror#fox32-with-os
to launch it with Fox32OS loaded (disk stored in/tmp/fox32os.img
).Things that need to be implemented/resolved before merge / other noteworthy stuff:
Notes about specific projects:
(dev)
.def
file./fox32asm/
and./fox32rom/
instead of../fox32asm
and../fox32rom
.check
in the Nix Flake)