-
-
Notifications
You must be signed in to change notification settings - Fork 165
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
docs: Altered minimum gcc version for Coro, fixed docs issues #1173
Conversation
✅ Deploy Preview for dpp-dev ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
are you sure 13 is the minimum? ive been using it on v12 in seven spells and beholder just fine, and on my local machine... |
Not entirely sure to be honest with you. I was under the impression it was gcc13 as minimum. If you're running coro on 12 then I'll change it to gcc12! |
It's for ARM that you need 13 For x86 11 and 12 work but have bugs with lambdas (we already warn about this one in docs) |
https://discord.com/channels/825407338755653642/825411707521728512/1252545524717064235 https://discord.com/channels/825407338755653642/825411707521728512/1225743126602317834 is it? Seems like 11 and 12 have issues on these machines (both cases are debian 12 though, so maybe it's a debian thing). |
|
So, to now update this, it seems it's only gcc12.3 or higher and then a specific version of gcc11 that works. From talks, it's best to just tell people to use gcc13 or higher. This answers your question about it working on your end @braindigitalis |
This PR raises the minimum gcc/g++ version for Coro from 11 to 13.
This PR also corrects
set_emoji
(too much text for a@brief
, moved most of it to@warning
and@note
) andset_disabled
(previously stated that both true and false would disable a component).Documentation change checklist
doxygen
, and testing examples).