3 ms·
Fun, I have exactly the opposite experience re. VS and Qt Creator - VS sometimes takes, like 15 minutes to start a debug session on a large project while QtC ca
by jcelerier 7y ago
Fun, I have exactly the opposite experience re. VS and Qt Creator - VS sometimes takes, like 15 minutes to start a debug session on a large project while QtC can get to work in the same time that it would take gdb to start. And that's without counting the clang-based code model, all the niceties under the locator (ctrl-k), etc etc
> Where can I define macros in QtC?
the IDE is imho not the place to do that. Just use CMake and target_compile_definitions(my_target PRIVATE MY_MACRO=123)
> - In debug mode, QtC is unable to display certain types of variables, way too often.
very strange, but then I mostly use it on Linux with gdb / lldb, maybe the cdb integration is less good.
> - I have fiddled for days with the .PRO file, read all the StackOveflow posts, and I still can't suppress reams of pedantic warnings
If CONFIG += warn_off in your .pro (switch to cmake !!!) does not work please file bugs !
- TravHatesMe 7y agoNot sure if this applies to Qt, but VS2019/netcore has made tremendous strides with its tiered compilation.
- GnarfGnarf 7y agoSorry, I meant keyboard shortcut macros (Ctrl M, R in VS 2017).
- jcelerier 7y agohmm.. this ? https://doc.qt.io/qtcreator/creator-macros.html https://doc.qt.io/qtcreator/creator-macros.html