Qt Creator and other tools

@Raad A documentation update is in the works that will explain that.

Ok, solved. defineReplace(somefunc) { SOURCES += my_new_source.cpp export(SOURCES) return() }

@Himanshu-charde In fact in the case you show I think your process.start("literal string") will work OK, but only because it doesn't happen to have any special characters which need quoting. But @jsulm suggestion to use the separated string list arguments is more robust if that changes. The vital thing is that as @jsulm says you are not attempting to read any output from the process back into your Qt app. You'll want https://doc.qt.io/qt-5/qprocess.html#readAllStandardOutput and possibly https://doc.qt.io/qt-5/qprocess.html#readyReadStandardOutput. And while you are at it, always do the same for https://doc.qt.io/qt-5/qprocess.html#readAllStandardError. And the https://doc.qt.io/qt-5/qprocess.html#errorOccurred signal. People don't bother and then wonder what's happening when an error is reported....

@fcusolito I don't see ClangPchManager in my plugin list. Maybe that was an experimental plugin you enabled and that no longer exists? Regards

@Milosz said in Using Qt classes in VS project: n other words I have to create a new project - I cannot modify the current one. did i understand correctly? Perhaps you can try to use Qt Visual Studio Tools. It may include an import feature, but I don't know. I never use it. Yes, you need to create a new project, because using Qt requires to made deep changes in your code.

I have the same problem on MacOS but this seems not coming from CMake but from the last version of QT Creator 4.11.x I installed an instance of Qt Creator to 4.10.x and get back project structure as folders structure.

Since these are two different build systems there are for sure different flags. If you need a specific flag you have to make sure it's there for both build systems. Both can create a running Qt application.

the build error is following: [image: 6e038656-1bd8-4311-80de-f072ef391ae1.png] I guess it's not supposed to be built in this way. Looks like I should build it as a new Qt module like described "here":http://qt-project.org/wiki/Creating-a-new-module-or-tool-for-Qt#55af8d3b581bc7a96ac2a08eb19da92c. Please correct me if I'm wrong.

OK I figured it out myself. First one must place some widget in the pages and then right-click on the stackedWidget object name and from the menu select Layout and the select the desired layout.

This topic is quite old, but for any future time-travelers coming by this way, I found a workaround, that works at least in my case. My projects is structured as a SUBDIRS project, with all the subprojects listed in the main .pro file. In each subproject file, I "include(PARENT_PROJECT.pro)", on the very first line. Moving this include statement to the bottom of the subproject's .pro file fixed the QtCreator syntax highlighting issue for me. Hopefully this helps someone, somewhere out there.

Problem is solved, using the old rev_09 of VS Tool, it is working...

@LeLev i understand

Related to my post... Yesterday Cristian Adam has published another interesting article on Qt's blog about Building Qt Creator plugins with GitHub Actions.

@Christian-Ehrlicher said in Trying to build qt creator from source with MSVC: Cannot open include file: 'stddef.h': No such file or directory: and do you really opened a visual studio command prompt Thank you that was it! Wrong command prompt.

@MartinD Use -settingspath parameter to specify different directories for settings.

Hi @Szymon-M-Sabat, that was already mentioned in the blog post comments, there is also a workaround. You might want to look that up. Regards