-
-
Notifications
You must be signed in to change notification settings - Fork 880
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ci: Add GCC build job for Linux #2027
Conversation
Personally I don't think we need to add the builds to the release, it will just confuse users with more options and add support burden dealing with more build variants. I think just a job to verify it compiles would be enough, and we can skip packaging and uploading for those jobs and remove from pre-release dependencies. |
This also removes the packaging step for linux-sdl-gcc and linux-qt-gcc so that the only available artifacts for download are compiled with Clang
Updated accordingly. |
renaming linux builds might break updater , better just use -gcc only and don't add -clang to linux |
Done that as well. |
@tomboylover93 @abouvier It does not hurt to check if a PR breaks compilation with GCC but it might also be a good idea for the AUR shadps4-git package to try to stick to the way shadps4 is built for official releases. |
I suggested that it be changed to use Clang as well but that's up to them. |
Ive had random problems debugging using gdb/lldb when compiling with clang, and better luck with gcc. So I vote for having a gcc action |
This sounds good to me |
I believe this is ready for review, both requirements are satisfied (not having a packaging and uploading step for GCC jobs, like a "dry run" of sorts, as well as proper naming for Clang jobs to avoid breaking the updater). |
I think this is good idea. |
something seems to fail here , if you can fix it will go on with merge |
The error that it gives now that I merged the main branch into it is this:
which fixing it is out of scope for this PR and way beyond my C++ knowledge. But it's a good thing that it's there because errors like this are why I made this PR. |
error should be fixed , if you can rebase we can check |
GCC checks still fail. |
GCC version in CI runner is too old? |
Default is 13, there is 14 in universe repo but I don't know if GH CI enable that repo or not. |
I probably need to specify gcc-14 and g++-14 as the compilers instead of just gcc and g++. |
Ah, I see you already install 14. |
Now it fails in a dependency:
|
Same error osmcode/osmium-tool#276. |
You can skip building |
Try |
I use Arch which doesn't have a |
I looked at Launchpad before adding that and it just said |
Hmm, It would still fail if that only a header lib 😭 |
I tried looking for a .deb file for the actual |
Been wondering why I can build with Arch's |
Fixing up the discord-rpc rapidjson here: shadps4-emu/ext-discord-rpc#1 |
Merged if you can ,update the submodule in the branch to check |
Both Qt and SDL GCC jobs pass now. |
As described in this reply for issue #1994, the idea behind this is to catch compilation errors with GCC, especially with new PRs, so that they can be fixed before being merged. A lot of people on Arch Linux use the shadps4-git PKGBUILD, which does not explicitly use Clang as the compiler and often causes compilation issues. This could also help with code quality as GCC is a more fleshed out compiler and less "tolerant" with errors than Clang.