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-system: cmake: added compiler flags for c++17 #6246
base: develop
Are you sure you want to change the base?
build-system: cmake: added compiler flags for c++17 #6246
Conversation
Thanks for this. I tested it on MacOS 14.4.1 (M1 max chip) and Ubuntu 22.0.4 (ARM64). I attach all output messages in terminal.
|
At line 40453 of
But neither the PR's copy nor the |
Thank you for your feedback! It is strange... I thought that I used a clean copy. I have tested again with a clean copy of the source. |
You don't seem to have the patch. What branch are you on? Make sure you're on the PR branch from my fork: doubtfulpalace:topic/fix-build-with-apple-clang-15
|
@prko What branch are you/ Can you do |
Updating `boost` fixes one of the two errors, I forget which. Unfortunately, it breaks our build, as some `boost` sources end up in the `libscsynth` target and fail to build. I believe it’s because newer `boost` uses a completely different build system. Fixing that was beyond my rudimentary `cmake` skills.
On Apr 4, 2024, at 12:43 AM, smoge ***@***.***> wrote:
@doubtfulpalace I think at least some of the errors could be fixed by updating the boost library.
|
Ehm , I think I do not understand what you mean. Any way in terminal I get this:
|
The |
@doubtfulpalace
Thus, I pasted the text you modified into the corresponding file of the develop branch. Now, I seem to succeed uin building only with boost errors. However, On sonoma, interpreter quits, and on Ubuntu server does not start... Anyway, thanks for your work! I do not understand the details of the errors. However, I remember @JordanHendersonMusic recently worked with Boost, I do not know if he can fix this bug, but I worry if his implementation of ReplaceRegex should be touched again. #6213 |
You have to do what it says:
Always the case when first cloning SuperCollider. The server crash is:
I don't think it has anything to do with this change. The problem is that Cmake incorrectly thinks it has found Vorbis, etc.:
which is beyond my ability to fix, at least tonight, and I'm leaving town for a couple of weeks tomorrow. You could try patching the current release branch and see if that works. |
I was able to build with Is this the best solution though? In the next c++ standard I assume these features are gone? |
Upgrading to current boost would be better, I think, but doesn’t “just work” as they have changed their build system. I tried incorporating that, but quickly got into the weeds. Someone who knows the build system might have better luck.Tim Walters | The Doubtful Palace | http://doubtfulpalace.comOn Apr 18, 2024, at 1:28 AM, Scott Wilson ***@***.***> wrote:
I was able to build with -DCMAKE_CXX_FLAGS="--std=c++17 -D_LIBCPP_ENABLE_CXX17_REMOVED_FEATURES" which I gather has the same effect as this PR.
Is this the best solution though? In the next c++ standard I assume these features are gone?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
|
@doubtfulpalace I don't know if this is helpful for this issue, and may be stating the obvious, but the README_Boost file notes that some boost files have been patched for SC. |
At least one function causing problems was deprecated in c++11 and removed in c++17. So some features are already "gone": https://en.cppreference.com/w/cpp/utility/functional/unary_function (It's not used in the SC codebase, but older boost versions) |
I'm out of town and can't check or give details, but IIRC the problem with updating boost was that boost builds its libraries with something called "b2", and our build script doesn't use that.
I tried modifying the cmake files to do it the new way, but (probably due to my lack of cmake skills) it just made a mess, putting boost library source into the Xcode project, which then wouldn't build.
… On Apr 20, 2024, at 9:47 PM, smoge ***@***.***> wrote:
At least one function causing problems was deprecated in c++11 and removed in c++17. So some features are already "gone":
https://en.cppreference.com/w/cpp/utility/functional/unary_function
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Purpose and Motivation
Fixes #6244 (on my Mac at least).
Types of changes
To-do list