Qt Creator and other tools

@d14bl0 said in Cant build stanford CS106L projects using QTCreator: @cristian-adam Hey thank you very much! that worked :D I was just about to give up. Thanks again!!! Don't forget to mark the thread as Solved.

@cristian-adam said in Are there plans to have Codeium plugin/extension in Qt Creator?: @pgathogo See https://github.com/Palm1r/QodeAssist QodeAssist is an AI-powered coding assistant plugin for Qt Creator The above plugin does not actually support Codeium. The best option it would be for you to talk with Codeium themselves https://codeium.com/contact

@asisisyah said in qt 5.15 and qt 6.5.3 no found pdf and pdfwidget: so, how can i install pdf, pdfwidget module I'm not sure but it can be that these modules needs to be selected in the Qt Online Installer or Qt Maintenance Tool (the later can be used to change already installed Qt).

for first need to copy here: /home/myuser/Qt/5.15.2/gcc_64/plugins/designer/file.so .... (if usr/lib .... is quite equal, need to find tool folder too ... so better a non root installations). BUT forgot to copy here too .... /home/myuser/Qt/Tools/QtCreator/lib/qtcreator/plugins/file.so if 2 different version need to use one only at time OR file.so compiled for QT5 and one for QT6, but you can use only if you compile and use: mycustoWidgetqt5 and other different mycustoWidgetqt6 these solve the problem.

Now I change version with fresh install ... use qtcreator14, qt6.6.3 .... install open62541 from git using doc of open62541 guy, I install qtopcua using "how to" of guy of basyscom .... add necessary INCLUDEPATH and LIBS on .pro file .... and all work. Only if add a switch on .pro file for system-open62541 these fails with "system-open62541" file not find. If leave these switch all work ..... ps: on debian 12 is not possible to install libopen62541-dev from repo .....

@gfxx after these regarding the issue of files being corrupted by qmake, the problem stems from the fact that these were old files edited with 'Notepad' and also with 'gedit' on Ubuntu, which of course uses a more common encoding compared to Debian 12, which instead follows standardized encoding. Once imported into Debian 12, these files cannot be correctly encoded by QT6, regardless of the 'locale' settings. The solution is to open the old files with 'xed' and save them. At that point, QT6 encodes them according to the system's requirements, does not corrupt them, and interprets them correctly. P.S. It is not advisable to use Debian Bookworm with QT6... Just today, my 'mirror' sent me kernel updates, which, among other things, involve uninstalling libdcb6 and using a proprietary library integrated directly into the kernel... I don’t know if this might cause problems, but I fear it could, and quite a few at that... P.S. -2- For other reasons I upgrade to qt6.7.2 .... all utf-8 messages about encoding is disappear ....

@gfxx because definitively an other problem now ... I open I new post .... If these is wrong, moderator can joint these two.

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 🙂