Qt Creator and other tools

Then, please, try the official package.

Hi @aha_1980, This provided some useful additional info, which I've attached below. >408^running dNOTE: ENGINE RUN AND INFERIOR RUN OK sRunning. dState changed from EngineRunRequested(7) to InferiorRunOk(11) dNOTE: ENGINE RUN AND INFERIOR RUN OK sRunning. dState changed from EngineRunRequested(7) to InferiorRunOk(11) [master] dINFERIOR STARTED sApplication started. >*running,thread-id="all" dNOTE: INFERIOR STILL RUNNING IN STATE InferiorRunOk. >~"\nProgram" >~" received signal SIGSEGV, Segmentation fault.\n" >~"0x0000000000000000 in ?? ()\n" >*stopped,reason="signal-received",signal-name="SIGSEGV",signal-meaning="Segmentation fault",frame={addr="0x0000000000000000",func="??",args=[]},thread-id="1",stopped-threads="all",core="1" dNOTE: INFERIOR SPONTANEOUS STOP sStopped. dState changed from InferiorRunOk(11) to InferiorStopOk(14) dNOTE: INFERIOR SPONTANEOUS STOP sStopped. dState changed from InferiorRunOk(11) to InferiorStopOk(14) [master] <409importPlainDumpers off dHANDLING SIGNAL SIGSEGV sStopped: Segmentation fault (Signal SIGSEGV). The GDB version that it found is version 7.12.0.

In that case, just create the folders in your project folder and in your .pro file: SOURCES += \ $$PWD/controls/anyfileaboutcontol.cpp or alternatively you can add a .pri file per subfolder that you will include in your main .pro file.

@Exotic_Devel said in Qt Creator external tools paths: What about the problem with qmlviewer, can you give me any suggestions? I honestly have no idea what that is. Looking in the qmlviewer.xml file, it seems to be related to Qt Quick 1, so likely a Qt 4 remnant. Regards

@William-Lin said in How FLEX&BISON works with Qt？: but it didn't work What exactly?

@AnneRanch said in Missing (#include) "ui_device.h" ?: Perhaps there is an official way to do "version control" within IDE. You can use several version control tools with QtCreator, like Git, Subversion, Mercurial and CVS.

After few dead ends I found an older discussion which stated that "qtconnecetivity" examples are somewhat "unusable" in qt5. I have no intention to "go backwards" to previous versions of qtx and did not keep the compiler errors in case somebody really wants to know why it did not compile in qt5. It was missing some "configure" reference. So - at this point I shall go back to trying to cobble my own "example" and just use "qtconnectivinty" examples as a template code.

@AnneRanch You can mark it as solved: under "Topic Tools" on the bottom right side.

We could solve the first part together in a chat session by: git reset HEAD~2 git commit --amend git push HEAD:refs/for/master

Hi, It might be of interest and would likely benefit from a plugin in Qt Creator. However the first step would be to have it build various Qt project types. Note that cmake won't be transitional. It's going to be the build system of Qt 6 and thus it's going to stay like this for the whole Qt 6 lifetime at least. Just take a look at the lifetime of qmake.

What about using QProcess to run ffprobe ? It has the advantage of being cross-platform.

Most likely you enabled "Page protection", because this needs a LOT more memory (and should only be enabled if you are checking for heap overruns).

@aha_1980, thanks, I removed CONFIG += ORDERED. I prefer to keep tests separate from source, so I guess I have to live with this limitation.

@Mariana-Meireles yeah, such things sometimes happen after Creator updates. The sledgehammer solution is to quit Creator, delete the .pro.user and the build directories, and the restart Creator. But your solution should work too. Regards

Hi @aha_1980 , yes the store provides V2.4.1. The error happened to other people before: "The 'ProviderPackage' package did not load correctly." This leads to a slower startup of VS and the QT VS Tool button to be stuck on "initializing". Check: https://stackoverflow.com/questions/16176933/the-providerpackage-package-did-not-load-correctly/19428110 (even though QT might not have been the root of the issue in this particular thread) I actually proceeded to install older versions, f-ing up my VS. I re-installed it, tried 2.4.1 again and the Error above happened again. I again installed older versions using the command line interface of the VSIXInstaller. V2.3.0 happened to work. As this costed me a couple of hours I stopped there, not further investigating on the error. I can however provide the install-log of V2.4.1 if anyone of the QT-Team is interested. As it works now, I consider this case closed. I will stay on V2.3.0 for the sake of my mental health. If this really is a compatibility issue, a compatible Version table should be uploaded somewhere. Cheers and thank you nevertheless @aha_1980 , Dennis

Hi @RickFrank, are you using the MSVC or MinGW compiler and which version? For me with Creator 4.10 and Qt 5.12.4 MinGW 32 bit both Run and Debug print the messages to the Application Output. Only difference is, that on Debug the output is black while on Run it violet. Regards

never mind