I see Qt6 is out, and they have a CMake build now.
Yup, I attended the conference last week. Pretty cool stuff!
https://wiki.qt.io/Building_Qt_6_from_Git
/me tries building it...
Lots of interesting bits, but looks like they're embracing cmake hard now.
Glad to see they didn't try any tricks with holding back the source for 6 months...
Oof. C++17 minimum. Well, I guess It'll be a while anyway before 6 is shaken out enough for us to target it...
Yep, I think that's fine for GUI. It's just not something we'd want to spread to the core libs
starseeker said:
Glad to see they didn't try any tricks with holding back the source for 6 months...
is C+17 compiler support coming to brl , ready to rock open source cad projects :)))
Our core codebase is still capped at C/C++11 standards right now. We tend to stick with older standards until there's some compelling feature or need that motivates requiring the newer standards, since the shift means older platforms will cease to work with the newer versions. The GUI (as opposed to the core) may opt for a different approach - we don't want to get stuck with an older Qt API when the newer one is available, and modern GUIs are usually problematic on older platforms anyway - but an across the board move to C++17 is probably not imminent.
For example, if we develop and demonstrate a command subprocess communication system using Cap’n Proto that allows us to Ctrl-c interrupt our GED commands without bringing down the main application, that would be compelling enough to motivate consideration of requiring C++14 (needed for capnproto). But we'd need to actually have the feature in hand before we introduced the requirement, since libged and GED commands are part of the core library set.
Last updated: Jan 09 2025 at 00:46 UTC