Linux Build using Github Actions about romwbw HOT 7 CLOSED

It is working great. Might be possible to clean the intermediate files to reduce the size. There is probably a way to expose the builds in a way that is easier for casual users to find as well.

Don't change anything right now. I want to learn a bit more first.

I am going to leave this issue open for now in case we want to make some changes.

Thanks!

Wayne

from romwbw.

the directory naming logic goes something like this:

Tools/unix contains the portable shell script(s) and source code of the binary tools
Tools/Linux gets the executables for the linux build
Tools/Darwin gets the executables for the mac os build
the Tools/Makefile.inc points BINDIR at the right executable directory

from romwbw.

Well, this is interesting indeed. I would not mind having a CI pipeline.

Will see what Curt thinks...

from romwbw.

Happy to help. I will try and investigate the build failure. It's using the Ubuntu latest Docker container, so should theoretically behave exactly the same as on a clean Ubuntu install.

Realised you possibly can't see the build log as it's my repo - attached is the log output

build_output.txt

from romwbw.

I figured out it was because the ncurses headers weren't installed.

Here's a PR that builds RomWBW on every pull and generates a zip:

#90

from romwbw.

Thanks for merging. It seems to be working OK. Archives generated are ~67MB which I think is greater due to the size of the build tools.

Let me know if you would like it to anything differently.

from romwbw.

I'm going to go ahead and close this issue. The GitHub CI build process seems to be working fairly well. We can open new issues if something else is found.

Thanks!

from romwbw.