Their supported standards list 'libc++' [1] which implies LLVM and potentially Clang. I could not find info online.
"IAR Embedded Workbench C++ is dialectal and contains some features not part of standard C++." [2] Their extensions seem to be to relax some awkward syntax, and for embedded systems support such as memory positioning (?)
Qt is huge in the embedded space, such as automotive, where I see IAR is as well. Makes sense as an acquisition. I used to work as the C++Builder product manager, which has custom C++ language extensions, and I always personally (not a statement from my prior employer in any way) wondered if Qt might someday look to that toolchain too -- it does not target embedded computing, but it has excellent expertise in custom compiler changes including extensions to address exactly the same problems (as I understand) that Moc tries to solve. In general especially with the state of the C++ committee, and Qt dealing with some custom handling, I would expect owning a compiler toolchain with a willingness to customise the language to be highly beneficial for them.
[1] https://www.iar.com/embedded-development-tools/iar-embedded-...
[2] https://en.wikipedia.org/wiki/IAR_Systems#IAR_Embedded_Workb...
why would Qt want to customize a compiler when they still need to support llvm/gcc/msvc?
My first thought is that they can extend Qt's test library to also manage test data across a pipe to the embedded processor.
They routinely smoked GCC and Clang, and sometimes ARMs tools on a variety of tasks.
I'm not sure I see the advantage on Qt owning a compiler though - one of Qt's strengths is portability.
reflection could replace moc, (likely c++29 needed) but if compilers don't implement that part of reflection qt can't use it. If qt can get compilers updated that helps them.
https://wiki.qt.io/C%2B%2B_reflection_(P2996)_and_moc
C++ Builder still has a special place on my heart, Microsoft has never managed to create something as good on their C++ stack for doing GUI applications in C+*, there is nothing visual about Visual C++, unfortunely they seem not able to deliver anything better than MFC.
C++/CLI never had the same access to the GUI tooling used by VB and C#, C++/CX got sabotaged by an internal group that rather write IDL files in Notepad and push that experience to everyone, than caring about paying customers.
Regarding IAR, maybe it is a way to solidify their offering, and counter advances from Android, Electron and Flutter being adopted on the same industries.
So I agree with you, Qt tends to be a lot cleaner than standard C++ (or even C++ with Boost). I highly value consistency in a codebase, and Qt really makes that possible.
There were many hacks, like filling the stack with sentinels to detect it at run-time. The linker script was horrible. Rewrote everything from scratch. The resulting code was many KB too large for the available space, it would have needed to slim down the stdlib. Even with the much better optimizations and LTO it was still too big.
Nice for that time, but essentially unusable. The company needed 10 years for that code, my plan is to rewrite it in 2 weeks.
I've tried sdcc, but this was atrocious in array access for 8bit Atmel. Only solved with asm
I'm pretty sure it's the stdlib, IO probably, which is only needed for debugging anyway.
Their IDE is horrendous.
Why is Qt support so poor on mobile (and especially PyQT)? They're basically just 2 OSes at this point, they've been around for 15+ years. They do change, but they're also quite backwards compatible.
I would imagine that Qt would want to target such a huge market.
joezydeco•3mo ago
rrgok•3mo ago
Could you kindly ELI5 me what is wrong with QT licensing model?
joezydeco•3mo ago
CoastalCoder•3mo ago
ogoffart•3mo ago
joezydeco•3mo ago
joezydeco•3mo ago
I've switched to vanilla web technologies. Node, React, etc. It's painful and it sucks but hardware keeps getting faster and cheaper. I can find contractors easily and I don't need an increasingly expensive subscription^H^H^H^Hcontract with Qt to keep my developer seat hot. They tried multiple times to get me to abaondon my Qt5 license to switch to their new revenue model. I told them to fuck off.
HeyLaughingBoy•3mo ago
What was painful about switching to web tech for UI? I've proposed it at work a few times for exactly the same reasons: get away from Qt and ease of finding developers. Since our GUIs all run on Linux (we usually do the realtime stuff on an external ARM processor) it seemed like an easy transition, but I've been shot down every time.
Would be nice to hear what the downsides are.
markfeathers•3mo ago
https://www.qt.io/qt-licensing
https://fossa.com/blog/open-source-software-licenses-101-lgp...
>And everytime I end up confused about it.
I think this is the point. If you're making a real application you may pay for the licensing to avoid the uncertainty/risk.
michaelsbradley•3mo ago
https://doc.qt.io/qt-6/licensing.html
Over the years it has been noted by many that Qt’s wording and warnings about the LGPL amount to spreading FUD or outright misinformation in what seems like an attempt to scare managers and C-suite folks into buying commercial licenses “just in case”.
bradfa•3mo ago
In every major Qt release, there's a handful of super useful but kind of niche widgets which aren't released under open source licenses, presumably as a sales tactic as buying licenses gets you these widgets and sometimes that is cheaper than building them yourself, but unless you need these, you probably don't care about this.
Although my experience attempting to buy licenses from Qt is about a decade out of date now, the way it roughly worked was you paid a per-seat-per-year fee to get a developer license or build-machine license. Then you bought bundles of deployment licenses, and the bigger the bundle then the lower the cost per license. If you are buying a bundle of a few thousand devices then you pay more per license than if you're buying a bundle of a few million. Either way, it is a significant chunk of cash you have to front to get your block of licenses and normally embedded projects are EXTREMELY sensitive to per-unit costs.
seba_dos1•3mo ago
bobmcnamara•3mo ago
This right here! We customers and users alike are often confused by QTs piecemeal licensing model.
freedomben•3mo ago
linhns•3mo ago
Macha•3mo ago
rcxdude•3mo ago
pjmlp•3mo ago
Qt licensing is rather easy to understand.
Don't want to pay Qt? Then get the same money yourself, zero.
Want to get paid while selling a product based on Qt? Give something to Qt.