Qt Creator and other tools

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

Hi, To add to @ankit-thakar, take a look at the moc related articles from Woboq some of them might be old but are still relevant. By the way, you should go with the Qt 5 version of the moc documentation.

Hi Did you also build the "LLVM/Clang 6.0.0 or newer for the Clang Code Model related plugins." it seems it crashes loading that. Its now default ON in newer creators. You could try to start it with -noload all so none of the plugins are loaded then go to About plugins and disable the codemodel and see if that makes crash go away. [image: F0Aa6E.png]

@aha_1980 This problem has been solved. The version of qtcreator I used is 4.0.1. After updating to qtcreator 4.3.1, this problem will not exist

Hi, The IFW writes all files relative to the given base installation directory. One option might be that in the component's installscript.qs you move the files to desired destination directory. Note that here you need to take care of elevated permissions if needed and also implement the "undo" operation so that when you uninstall (MaintenanceTool(.exe)/Uninstaller(.exe)) the packages it knows what to uninstall. To make IFW natively support installing packages with absolute paths please open a Jira ticket/suggestion, I think it might make sense in such cases.

@artwaw thanks for the suggestion. I'd tried a clean and run qmake (in that order) with no success. The missing step (for me, anyway) was the rebuild command.