MusE
Least common denominator #1201
Replies: 14 comments
-
|
For Qt it might not be necessary to bump up the lowest version. As for C++ yeah, I've been watching and reading and thinking a lot about it lately. So there are a few places where we already set (or force) the C++ version. |
Beta Was this translation helpful? Give feedback.
-
|
I think we should have some fix point as a reference. Many use the oldest supported LTS version of Ubuntu for that, which is probably the best thing you can get in the volatile Linux world. I don't see much benefit in Qt6 ATM, there are hardly any essential improvements in the area of classic widgets AFAICJ. |
Beta Was this translation helpful? Give feedback.
-
|
Sounds reasonable. At least until the imagined point where we really want to use a feature that requires a newer version. |
Beta Was this translation helpful? Give feedback.
-
|
Out of curiosity I tried building with C++17 enabled and most of it went fine. Fails in scoreedit.cpp for std::map manipulation, didn't get exactly what was wrong so I commented out a bunch. The rest compiled. |
Beta Was this translation helpful? Give feedback.
-
|
I already have a branch waiting for Ubuntu 16.04 EOL with all the version updates and some cleanups. I'm also building that with c++17 but I don't get any errors in scoreedit.cpp, strange... I think there shouldn't be any incompatibilities in std::map. |
Beta Was this translation helpful? Give feedback.
-
|
The Ubuntu 16.04 EOL has been reached so I will merge the version updates soon (this weekend probably). |
Beta Was this translation helpful? Give feedback.
-
|
Looking forward to the 17 features. Could really use them right now. Bring it on! |
Beta Was this translation helpful? Give feedback.
-
|
It's in master now. Let me know if there are any problems with the build on your side. |
Beta Was this translation helpful? Give feedback.
-
|
Fails (so far) in score edit as you mentioned before, on two lines 2100 and 2591. |
Beta Was this translation helpful? Give feedback.
-
|
Fixed in master now. |
Beta Was this translation helpful? Give feedback.
-
|
Funny, no errors here, and the AppImage build works too. |
Beta Was this translation helpful? Give feedback.
-
|
With your fix it compiles too here, so everything is good. |
Beta Was this translation helpful? Give feedback.
-
|
I've not updated my rolling distro in about a year so you may actually have a newer version than me. |
Beta Was this translation helpful? Give feedback.
-
|
Not really, I have 7.5.0 🙂 |
Beta Was this translation helpful? Give feedback.
-
Trying to keep up with trends of our favourite tooling packages (well, not really trying, more like: sometimes stumbling on bits of information)
I saw qt6.0 was released the other month, at some point we should probably look at the portability. No hurry on my part 5.x will be supported for a few years still and 6.0 has probably not entered that many distributions yet.
This does bring me to my main thought though. Currently MusE supports:
Qt from version 5.7 (released 2016)
Gcc 4.x, or rather C++ 11 (4.8 with full c++11 was released in 2013)
For both of these I'm curious if there are systems out there (that are in our scope to support) that have such old libraries, or if we safely could increase the lowest version?
For Qt we have stumbled a few times, depending on things from newer versions but as I recall nothing major so we found other solutions, perhaps there isn't currently any need to increase this.
For C++ there has been three newer releases, 14, 17 and now 20. Not entirely sure what features they contain that we could make use of. Though I'm sure there are a bunch.
I was mostly interested if you had any thoughts on this?
Going back to Qt6 I see it requires C++17.
Beta Was this translation helpful? Give feedback.
All reactions