Conversation
Removed unused 'with' parameters from FreeBSD workflow.
Updated FreeBSD workflow to install dependencies and build.
Added bash installation to FreeBSD workflow and ensured bash is used in the build process.
Add installation of libraqm package for FreeBSD builds.
|
@1111Windows Can you push a(n empty) commit (I've re-enabled the freebsd workflow on our side and want to see how it goes). |
Updated FreeBSD CI workflow to include architecture and output directory changes.
I changed some content to try to upload the file after compilation. Please allow it. Thank you. |
|
I've re-disabled the FreeBSD builds again because they took too long to run. I will re-enable them as soon as they pass for you on your fork's CI. |
Maybe we should try cloning SuperTux and compiling it on a FreeBSD VM? |
I tried that using the same VM that the workflow uses: I executed the same commands as the workflow. It worked and the issue didn't occur. Feel free to try yourself. |
This issue will cause the compilation to fail when creating a release. See https://github.com/1111Windows/supertux/actions/runs/20692953472/job/59403728228 |
The issue is in the compile step earlier: |
|
I noticed that changing sync from 'zfs' to 'rsync' allows compilation to succeed, but at the next step it fails to find some files: |
I'm currently testing the compilation of SuperTux in another repository. Once I've finished testing, I'll submit this pull request.I'm currently testing the compilation of SuperTux in another repository. Once I've finished testing, I'll submit this pull request. If you're interested, you can check out https://github.com/1111Windows/FreeBSD-test/ |
|
For some reason, after cloning SuperTux, it started complaining about not finding physfs, even though physfs was already installed. So I gave up on the idea of cloning SuperTux inside the FreeBSD VM. After switching from ZFS to rsync, it successfully compiled when used by release, but it couldn't find the uploaded files.
By the way, after switching from ZFS to rsync, its compilation speed has significantly improved. |
|
Can you please update the workflow file to use vmactions/freebsd-vm@v1.3.6. The freebsd vm author claims to have fixed rsync issues, following my issue report. |
|
I think I got it to work. Can you do me a favour and test the artifacts? |
|
The 14.3 binaries in #3523 were tested by someone from the freebsd community and, apart from a library version mismatch, worked fine. Can you cherry-pick the last 2 commits from there onto this branch? |
For certain reasons, I am temporarily unable to use the FreeBSD machine.
ok |
|
It can now upload Release builds to Release. |
|
Can I mark this as ready for review? |
yes,you can |
FreeBSD VMs are connected via SSH, and it appears that variables are not passed.
This PR attempts to fix the BSD build.
Currently, only compiling SuperTux and testing its executability have been implemented.
I found that using the -DWERROR=ON option on FreeBSD causes compilation failures, so -DWERROR is disabled.
The current issue is: compilation is too slow.