Qt Creator and other tools

@J.Hilk said in What's The Name of exe?: clangbackend.exe thank you

@sierdzio Ah I see, dang, I was hoping I could do extensive auto reformatting of qml code.

continues here: https://lists.qt-project.org/pipermail/qt-creator/2019-May/008052.html

@JonB Thanks for the reference. I will pass this on to our build meister and see if it helps. It does look very much like the problem we are having.

@krobinson I have the same problem. You decided ? Tell me how

@luojun Good to know that your issue has been solved for you. Please mark the thread as "Solved" then. Under button "Topic Tools" click on "Mark as Solved"

Oh okay, I had considered the underlining to be a type of line annotation, apparently that is not the case. It is the underlining I have a problem with - I use a lot of designated initialisers in C, like this: struct foo_s bar = { .x = 1, }; They all end up underlined with the warning: "expected token ;...." So there is no way to disable the underlining?

Hi @Michael-Uman, Do you calll qmake CONFIG+=debug in first place? That generates -g compiler option, which has always been enough for me. Why do you need -g3? Regards

Hmm, I've never installed Qt UWP flavor from a .zip fip, I use the "online"-installer, you can download it here

qmake can also create Visual Studio solution files and there is also a Qt VS Addin

@Archie888 You should file a bug in the QtCreator bug tracker. See https://bugreports.qt.io/projects/QTCREATORBUG/summary

Ok, my problem has nothing to do with CMake's CMAKE_AUTOMOC and CMAKE_AUTOUIC, but... with Qt Creator itself! Indeed, I was using Qt Creator 4.9.0, but I have just tried with Qt Creator 4.8.2 and it's all working fine! (I have been thinking about filing a bug report, the problem is that my project is pretty big and I haven't been able to come up with a small test case...)

and then i instantly saw the problem: you also have to check "generate separate debug info"

that's good actually! but it really should be a single button, not related to selection. thanks!

Update: The same thing happens on another PC, with the same project. Also tested another, way smaller C++ project - semantic highlighting works there! Restarting QtCreator has no effect. The highlighting worked for the problematic project with the older QtCreator version 4.8.x.

Just an update. It looks like the QtCreatorDeployment.txt file is only taken into account by CMake Project or Generic Project. So I created a Generic Project, add the Python file(s) to the .files file, removed all the steps from the Build Settings tab, and configured the Run Settings with a Custom Executable where I set python as the remote executable, and main.py as the command line arguments while enabling Forward to local display. And it worked :-)

Hi @raven-worx , Thanks again, I've got it working the way I want, though I had to do some extra things. For completeness and others: What happens is that if I use your example, the listing.qrc file is created the first time, and not on every build. If I use a fake file as output, the custom compiler is executed everytime, however, when the listing.qrc already exists, and due to not being the output it is probably?? not seen as a pre-target for RCC so it is executed before the custom compiler. I've tried to add a depends_command or a dependency to a custom target in which I remove the file. Removal of the file works, but now the custom compiler is stuck in a loop it seems. Not entirely sure why. What seems to work, is to have the files for the custom command explicitly listed in the input, which even makes sense, no input file change, no need to build. But, since the files are created outside the QT project, I do not have a full/explicit listing. Using $$files(path/*, true) works to get the listing, but now there are many warnings like: Makefile:1379: warning: overriding commands for target `../../Project/ui/ui.web/listing.qrc' Makefile:1376: warning: ignoring old commands for target `../../Project/ui/ui.web/listing.qrc' To get rid of this warning I added the combine option, since there are many inputs but only one output, which again makes sense. So now I have a setup which only executes the custom command if the input files have changes, or if the output file is missing. The resulting qmake lines: npmcompiler.name = NPM Compiler npmcompiler.input = WEBFILES npmcompiler.commands = pushd $$PWD; npm run-script build -- --prod --base-href \"/ui/\"; popd npmcompiler.output = $$PWD/listing.qrc npmcompiler.CONFIG += combine ignore_no_exist no_link no_clean target_predeps QMAKE_EXTRA_COMPILERS += npmcompiler WEBFILES = $$files($$PWD/src/*, true)

@lazzyfox if I have a Qt for linux 64b system I can't have linux 32b kit on same system as well? No, you can. You will need a 32b compiler, though. Regards