Qt Creator and other tools

The second failure ninja: build stopped: subcommand failed. is a direct successor of the first error. Fix the first error, and the second will disappear. the file does exist and is in the include directory Can you tell us the path to this directory? According to the compiler command line, your compiler searches in the following directories: -I/Users/jamesmartin/sourceCode/C++/qt/QTCurvesCPP2/build/Desktop_arm_darwin_generic_mach_o_64bit-Debug/QTCurvesCPP2_autogen/include -isystem /Applications/qt/6.7.2/macos/lib/QtCore.framework/Headers -iframework /Applications/qt/6.7.2/macos/lib -isystem /Applications/qt/6.7.2/macos/mkspecs/macx-clang -isystem /Applications/qt/6.7.2/macos/include -isystem /Applications/qt/6.7.2/macos/lib/QtWidgets.framework/Headers -isystem /Applications/qt/6.7.2/macos/lib/QtGui.framework/Headers which seems a bit strange to me as it does not have any source directory in the list. Can you show your CMakeLists.txt?

Sureway to reproduce is @J-Hilk 's. But I can try to procure something later on today.

@hy1011 said in Qt Creator: Contains source code and should be able to jump to the erroneous program without debugging symbols when the program encounters an error Debugger stops exactly where segfault occurs. Often this is somewhere in Qt libraries, 3rd party libs or system libs. You just need to move a few steps back in stack view to find the last part of your code which got executed (and is usually the reason for the crash).

The circle of life

@Sarfaraz Recently somebody else reported same issue (you can search here in forum).

@artwaw That sound like a solid solution. Thank you. Script as file in repository or CMake target set to run AFTER build is completed. I struggled a little with CMake target approach - as by default - Qt Creator set flag Stage for installation which is not accessible by CMake. Still - unmark manually by user is far easier then setup 6 deploy steps in GUI. XML approach I rejected as too big (~40 XML lines where most of them are just copy-paste) and too brittle (file ~/.config/QtProject/qtcreator/profiles.xml).

Hello from the future. 5 years later and still not a feature, but here's a ugly workaround I have been using to some degree of satisfaction: On the main Qt Creator window: pull up the bottom panel divider all the way up covering as much of the window as possible select <no document> open a new window(s) form the "split" icon, and use that as the main editor window This way, I have a window just for the output separated from the code editing. Anyway, not pretty, but gets the job done.

It turned out that my string for the ABI was incorrect. The correct string for this toolchain is: arm-linux-poky-elf-64bit Though "generic" will work for "poky." Thanks to all who looked.

Can you provide a minimal compilable reproducer that shows this issue ?

I noticed that when in the Edit mode there was an error at the top of the code listing saying the file was not part of a project. Even though the set of files were opened in the process of opening a project, the files opened were not part of the project. Strange. I managed to get it to Build and Run. In the Mode Selector, click on the Projects icon In the Build and Run section, click the Run icon. That will build and then run. After that the Run and Debug icons in the Mode Selector are no longer grayed out and are active, and the files no longer have the error message that they are not part of a project.

@JimmyHan as @cristian-adam suggested: Providing information about your build failure helps us help you 🙂

@cristian-adam Hi Cristian. Thank you so much for this! With the lines you suggest in [ClangdSettings] the warning message goes away and Creator allows me to come back in with the Use clangd setting. I raised https://bugreports.qt.io/browse/QTCREATORBUG-31541 for this earlier on, and there is another gut stuck on this at https://stackoverflow.com/questions/78811212/clangd-is-disabled-at-every-launch-by-qt-creator. I will update both of those. 12GB seems excessive, since it works fine on 4GB with only 2GB free. I realise it will depend on size of code, but still. Per that guy's stackoverflow post and my QTCREATORBUG I think there needs to be some way for users to "permanently" disable this warning, e.g. after clicking "Enable anyway", without having to resort to finding this post here. I will mention it in my bug report, up to you guys. P.S. IMHO wanting 12GB for a code model is just ridiculous! But that's modern computing for you :)

@cristian-adam said in Add Android kit: I guess the Android setup should not mark as green a JDK that's not working. The green mark only says that the path exists and is writable. AFAIK an SDK is needed to test, if the JDK is compatible.

The usual way is to use some git repository and share it via GitHub or other such service. But you can copy-paste files if you want, too - it should work. Just remember to delete .user file, it contains QtCreator information specific to one particular PC. Your new PC will generate it's own .user file. If you are using CMake, the file will be in root directory and named CMakeLists.txt.user. If you are using qmake, it will be also in root dir with name <project name>.pro.user.

@cristian-adam thanks for the reply, I'll be waiting for this patch. I will use qt creator version 10.0.0 thanks all, i will close this topic

@QT_NA said in QT creator: /snap/core20/current/lib/x86_64-linux-gnu/libpthread.so.0 Are you trying to build a Snap package?

@chenqichen please write in english or use the appropriate subforum for your language.

I am just guessing - not an expert on design studio: Looks to me as if the project uses widgets, which is obviously not covered by the reduced version of design studio. What kind of project is it?