-
Notifications
You must be signed in to change notification settings - Fork 135
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
[Build Issue]: Compiling fails with "error: unknown type name 'uint32_t'" #1287
Comments
Mind trying the suggestion outlined in ^? :) |
You're using a more modern GCC version (13) than our CI does (8,9,10), so quite possible we're doing something wrong that wasn't triggered before and is now. |
I sillily ignored the note because I assumed there was some sort of issue on my end. (oops). After adding Edit: performance issues disappeared after reinstalling pipewire |
Interesting, might mean that change should be made as a PR too :) I'm actually going to re-open the issue until ^ is worked out. RE: performance problems, you're probably building a debug build (the default) instead of a release one. If your goal is playing the game, not writing code for it, that's likely your fix. |
just added a workflow for clang 16 and g++ 13 and it worked fine. reopen if reproducible problem arises |
Someone else encountered this just now, so should probably be reopened and fixed properly :) See: https://discord.com/channels/261758887152058368/582052471040376832/1238434218820894761 |
having the same issue right now on fedora even when I tried the including cstdint |
Have you read through the build instructions before reading this?
What operating system are you seeing the problem on?
Linux (any distro)
Describe the build issue
If compiling with Crashpad, building will fail with
error: unknown type name 'uint32_t'
. Neither build type nor generator seems to affect where it errors.If compiling without Crashpad, building will fail with similar errors, like
'uint32_t' has not been declared
and'uint32_t' does not name a type
. It errors in a different location than it would with Crashpad, but build type and generator doesn't seem to affect this location.Relevant log output
With Crashpad:
Without Crashpad:
Anything else?
I am using Arch Linux x86-64
Here is the relevant version info for everything (hopefully)
I also wrote a script to test building with/without crashpad and also to test different build types and different generators. Script and the build logs should all be in the attached .zip
build_logs.zip
The text was updated successfully, but these errors were encountered: