Skip to content
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

Fix linux build and QT Deprecations #3305

Merged
merged 13 commits into from
Jul 10, 2023
Merged

Fix linux build and QT Deprecations #3305

merged 13 commits into from
Jul 10, 2023

Conversation

contra-bit
Copy link
Contributor

This fixes #3292 and subsequent errors mentioned in the issue.
Also this fixes most QT deprecation warnings.

Please merge,

@samaaron
Copy link
Collaborator

@contra-bit - thanks so much for this. One question I have is why including QtQuick was necessary? I'm pretty sure it's not used. Perhaps it pulls in deps which are? (In which case it might be better to be more specific rather than relying on transitive deps?)

@lilyinstarlight - do you have any comments on these commits?

@contra-bit
Copy link
Contributor Author

Good call, I just removed the QtQuick and could still build.

Prior I added QtQuck, due to this error: QQuickWindow: No such file or directory.

Please note, that I have reverted the addition of QtQuick.
Thank you for the quick review.

@samaaron
Copy link
Collaborator

@contra-bit thanks for checking and reverting the QtQuick addition.

One other thing is that I'm a bit wary of patching upstream deps (as you have done with atomic). I've therefore taken this opportunity to update active_support to the latest version which drops thread_safe/atomic in preference for concurrent_ruby. I'm therefore interested to know if this fixes/messes things up for you in linux land. I'm hoping it should be fine...

f760751

Switches transient gems - thread_safe and atomic are replaced with concurrent_ruby. tzinfo is also pulled in.
Recent Ruby versions introduced a detailed_message method to Exception which includes the useful "did you mean" information which was dropped from the message method.
@contra-bit
Copy link
Contributor Author

I can confirm, that removing atomic_reference.c does not break the build :)

@samaaron
Copy link
Collaborator

@contra-bit - great. Any chance you could fix the conflict so I can run the CI tests?

@contra-bit
Copy link
Contributor Author

Yes. Thanks for asking. I overlooked that merge conflict.

I am so gratefull for your work. Thaks alot. I learn so much about sonic pi and tau this week. I appreciate your time and effort, espcially your fast and high quality responses ❤️ 🎧 🎉 🥧

@contra-bit
Copy link
Contributor Author

This resolve was weird (0 bits changed) . I manually deleted atomic_reference.c, please check if there are any other files, which have reappeared.

@samaaron samaaron merged commit 4f0d2be into sonic-pi-net:dev Jul 10, 2023
10 checks passed
@samaaron
Copy link
Collaborator

@contra-bit - thanks so much for this - hugely appreciated!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Build errors with GCC 13
2 participants