Initial FreeBSD 14.0 Port of the Ren'py Build System

[bedwardly-down]

Core changes made:

• make_exec variable - FreeBSD uses gmake instead of make for native Makefile builds; this gives the ability to support other make systems too if and when needed
• build sysroot jails for FreeBSD to compile with at build time for FreeBSD x86_64 and i386 targets
• OpenSSL had to go through two builds to build the final version. A compatible version to build against is no longer available in the official repos
• Python 3.10 was used instead of 3.9 for FreeBSD due to system breakage otherwise; it introduced some bugs that took awhile to sort out
• Updated the Readme a bit (could probably have written that better)
• prepare-freebsd.sh was required due to different native package installation systems but this does fully build now

Areas that need heavy testing:

• The Python build is a bit hacked in; that could fail but so far has been working as intended on my end
• Python 2 hasn't been tested as thoroughly as 3
• SteamAPI and Live2D both do not natively support FreeBSD; for pygame_sdl2 to build properly, there's some manual intervention needed (such as manually copying over the Live2DCubism header used) along with possible platform specific bugs with the main Ren'py engine source code

[bedwardly-down]

In relation to this: https://github.com/renpy/renpy-build/pull/128

[renpytom]

I'll be honest - these are a lot of changes, and I don't really want to make Freebsd a supported platform for Ren'Py, as I don't have the ability to test it. (And I'm not really interested in developing the ability to support it, when according to https://web.archive.org/web/20230930003331/https://bsdstats.org/ , there are < 1700 users.)

I don't think that merits supporting a new version of Python, and separate paths for the build, etc.

What I'd suggest is that if you want to maintain it, you setup your own branch of renpy-build, with BSD specific changes. I can point to it in the official README, and if there are small changes that make sense to move into renpy-build proper to ease maintenance, then I can take those as individual PRs.

[bedwardly-down]

That works for me. I will need to redo the port work (and clean up quite a bit), but just supporting FreeBSD and possibly any offshoots will be plenty of work.

I did see some places where improvements could be made on your end and will get a PR setup for your README when it's ready. Just having a link to the repo would be perfect.

[bedwardly-down]

Closing this out with a new plan of action. This port work wasn't as clean as I'd like, and getting back to a similar place shouldn't be super difficult. Maintenance mode on.