Qt Creator and other tools

@hcroope For PyQt question you might ask at: https://riverbankcomputing.com/mailman/listinfo/pyqt

SOLVED: I tried everything Google told me (uninstalling and installing the software & Visual Studio, updating windows, repairing the microsoft Visual C++ redistributables...). The solution for me: I had installed in my system "Microsoft Visual C++ 2015 Redistributable (x64) & (x86)". Just the 2015 version, and not the 2015-2019 version. If you have the same problem as me, try installing these, which you can download from here: https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads

@AnneRanch It works for me on Linux with QtCreator 4.12.3

I am facing the same issue now in 2020. Anyone got any idea in latest Qt Ifw ?

@YuriRzhanov I only have x64 Qt installed and conversion produces only x64 configs. Do you have multiple Qt packages installed (32 and 64 bit)? If so which is set as default in Qt VS Tools?

Thank you everyone. I will just use QtCreator

Hi @In-Fo, please have a look at Windows > Views > Debugger Log. it might give some more insight. Regards

I am trying plain old pointers and none of the buf[0] kind of inspectors work.

@YuriRzhanov Please do not double post (https://forum.qt.io/topic/119464/convert-qt-project-to-visual-studio-with-x64-build)!

Well, there is no standard way, but at least, with info from your link, I could add if ( MSVC ) add_compile_options(/experimental:external /external:I C:/Qt/5.15.1/msvc2019_64 /external:W0) endif() So that I dont have warnings from Qt headers anymore. It created a lot (really a lot) of warning C4251, but they are usefull warning cause by a dll export of an entire class, which is bad design.

Nothing to do with Qt, just google "linux launch program on startup"

@Christian-Ehrlicher QtCreator. Probably from the clang backend However, the selected kit is relevant, because switching to MSVC-based toolchain makes the semantic issue disappear. I have wondered whether a) Enabling c++17 for MinGW isn't that straightforward (been there in the past, but can't remember the details) b) The MinGW shipped with Qt 5.15.1 isn't fully c++17 compliant (I'd love to check the MinGW docs, but they are a right mess - there's nothing like an easy-to-find release notes list for version)

@jsulm Then that is "semi-sad", because if Qt Creator thinks it's worth doing whatever --- in this case, setting up for no-sleep --- and finds it has to make a platform-specific call, then the devs might think "other people might want to do this, so we'll make sure there is a Qt library support for it so others can utilise it". Of course it's not an absolute requirement. But it's an indication this might be worthwhile. I semi-hope (yes, within reason!) that the whole of Creator can be written using only Qt calls, not platform-specific ones. IMHO.

@JonB Emmm. My colleague doesn’t understand comment syntax, so he wants to import the existing .html more easily.

OK, it is not that clear how to apply the process in Option wizard. I have a feeling the clone wizard is not working correctly, some option I can change, CMake I cannot. First - I have to start the ENTIRE cloning process over including physically downloading all github stuff. Second - no matter what I do I cannot deselect the Autorun. The Name field displays a name for the CMake installation. The Path field displays the path to the CMake executable. The Help file field displays the path to the CMake help file (.qch) provided by and installed with CMake. Deselect the Autorun CMake check box if you do not want to automatically run CMake every time when you save changes to CMakeLists.txt files. Select the Auto-create build directories check box to initially configure the project in a temporary directory. When you build the project Qt Creator starts from scratch and configures the project again using the build directory. Select Apply to save your changes. I'll try to do this NOT using wizard .

My project does use CMake -- I just don't invoke it via Qt Creator; I use the esp-idf command interface for that. It would be great to be able to build from Creator, but that's the next step. Perhaps I wasn't clear -- Creator is (now) correctly highlighting the source. I needed to work with the .includes file, but got it working. From this page: __STRICT_ANSI__ GCC defines this macro if and only if the -ansi switch, or a -std switch specifying strict conformance to some version of ISO C or ISO C++, was specified when GCC was invoked. It is defined to ‘1’. This macro exists primarily to direct GNU libc’s header files to use only definitions found in standard C. So maybe I should modify my .cxxflags file to match whatever settings the IDF toolchain uses?