This is the native side of the experimental "waterbox" project for bizhawk.
It consists of a modified musl libc, and build scripts to tie it all together.
1. Set up your platform.
The prescribed possibilities are not exhaustive. Other platforms may work.
Here are the supported alternatives:
PREPARE A WIN10 WORKSTATION:
Using the guidance at (https://docs.microsoft.com/en-us/windows/wsl/wsl2-kernel & https://docs.microsoft.com/en-us/windows/wsl/install-win10):
1. Install WSL2
2. Install Ubuntu 20.04 LTS (https://www.microsoft.com/en-us/p/ubuntu-2004-lts/9n6svws3rx71)
3. Clone the bizhawk repository. You can use it through /mnt or /home if you really like
4. Install build tools: sudo apt-get update && sudo apt-get install gcc g++ make cmake llvm
4b. (Note for future work: ideally the llvm installed above would not be required)
PREPARE A WIN10 VM:
1. Make sure the VM has "yo dawg" virtualization enabled on the guest. For example in VMWare Workstation, "Virtualize Intel VT-X/EPT or AMD-V/RVI"
2. Follow WIN10 Workstation preparation guide
3. If you wish to clone bizhawk on your host system (slower but maybe more convenient), you can use a VMWare shared folder and: `sudo mount -t drvfs Z: /mnt/z -o rw,relatime,metadata,uid=1000,gid=1000` (WSL won't auto-mount the shared drive)
PREPARE A LINUX WORKSTATION:
1. TODO. This should work, but no one has tested it yet
2. Clone bizhawk sources
* Make sure git's core.autocrlf is set to false, as the alternatives cause git to modify the line endings in .sh-looking files which WILL break the build process, from the very first step.
* This is NOT git's default. You will need to change it!! Go ahead and set it false globally permanently, since do you really want git modifying files?
* Make sure you have initialized and updated the needed submodules in the waterbox directory (for example, /waterbox/llvm-project and /waterbox/musl, etc.)
3. Consider whether it is time to update your build environment (i.e. sudo apt-get upgrade). We are not prescribing versions for build environment tools (gcc, etc.) so you may as well upgrade everything to the latest if you're making builds for other people.
4. Build libraries.
cd musl
./wbox_configure.sh
./wbox_build.sh
cd ../emulibc
make
cd ../libco
make
cd ../libcxx
./do-everything.sh
cd ..
5. If errors happen in the libcxx part, it can be due to musl mismatching your current build environment. This happens when your build environment is updated; musl does not track its build dependencies correctly. do `make clean` on musl (and delete the non-checkedin directories just to be safe) and try again from the musl step.
6. Some additional preparation is required before all the cores can be built:
cd nyma && ./build-and-install-zlib.sh
7. You are now ready to start building cores. Each supports `make` and `make install`, as well as `make debug` and `make install-debug` for local development. From the root directory, the following should all be valid:
cd gpgx && make install
cd libsnes && make install
cd melon && make install
cd nyma && make -f faust.mak install
cd nyma && make -f ngp.mak install
cd nyma && make -f turbo.mak install
cd nyma && make -f hyper.mak install
cd nyma && make -f pcfx.mak install
cd nyma && make -f ss.mak install
cd nyma && make -f shock.mak install
cd picodrive && make install
cd snes9x && make install
cd uzem && make install
cd vb && make install
59d011334f