Qt Creator and other tools

@Chris-Kawa Thanks for the input. "That's horrible. Both the fact you're using PATH for that and the reason for it." - I'd be happy to learn a better way. "a build step that copies dependencies to your output directory" - I don't know what this means or how to accomplish it. In general, I have control over where the output directory is and what goes into it but I don't understand putting "dependencies" in it. I broadly understand static vs dynamic linking, but certainly do not many fine details. For the bulk of libraries I create, I just make the .a with no affiliated .dll. One of my big confusions is why the relevant info is not available through whatever mechanism it always has been. For the immediate situation, the .a and .dll are in the same location, and I think the compile process specifies that location. Not sure what you mean by "mapped directories". Mapped where and by whom? The sources are where they were at compile time. I have, and have always, copied the created libraries to a general library location. that is somehow magically found when some app is ultimately executed. All of the libraries under question were built by me from source with the same set of tools. I don't know how to make the debugger load debug info and I apparently don't know where it looks for sources. I have monkeyed around with the path mapping feature, but apparently not yet in a useful way for reference, below is an extract from the transcript for the build process for this library showing the exact compiler and linker options. Below that is a comparable transcript from building another of my libraries. The second library is rather heavily used and regularly part of a debugging session. \usr\local\MinGW-w64\x86_64-7.2.0-posix-seh-rt_v5-rev1\mingw64\bin\g++ -c -MT debug/zzzzsomefile.o -MMD -MP -MF debug.d/zzzzsomefile.Td -g -fno-keep-inline-dllexport -Og -std=c++1z -fno-exceptions -Wall -W -Wextra -Wvla -Wdate-time -Wshift-overflow=2 -Wduplicated-cond -Wno-stringop-overflow -DUNICODE -D_UNICODE -DWIN32 -DMINGW_HAS_SECURE_API=1 -DWINVER=0x0601 -D_WIN32_WINNT=0x0601 -DQT_NO_NARROWING_CONVERSIONS_IN_CONNECT -DQT_BUILD_zzzz_LIB -DQT_BUILDING_QT -D_CRT_SECURE_NO_WARNINGS -D_USE_MATH_DEFINES -DQT_NO_CAST_TO_ASCII -DQT_ASCII_CAST_WARNINGS -DQT_MOC_COMPAT -DQT_USE_QSTRINGBUILDER -DQT_DEPRECATED_WARNINGS -DQT_DISABLE_DEPRECATED_BEFORE=0x040800 -DQT_NO_EXCEPTIONS -DQT_QML_DEBUG -DQT_GUI_LIB -DQT_CORE_LIB -I. -isystem C:\usr\local\Qt\Qt-5.12_x86_64-7.2.0-posix-seh-rt_v5-rev1\include -isystem C:\usr\local\Qt\Qt-5.12_x86_64-7.2.0-posix-seh-rt_v5-rev1\include\QtGui\5.12.0 -isystem C:\usr\local\Qt\Qt-5.12_x86_64-7.2.0-posix-seh-rt_v5-rev1\include\QtGui\5.12.0\QtGui -isystem C:\usr\local\Qt\Qt-5.12_x86_64-7.2.0-posix-seh-rt_v5-rev1\include\QtGui -isystem C:\usr\local\Qt\Qt-5.12_x86_64-7.2.0-posix-seh-rt_v5-rev1\include\QtCore\5.12.0 -isystem C:\usr\local\Qt\Qt-5.12_x86_64-7.2.0-posix-seh-rt_v5-rev1\include\QtCore\5.12.0\QtCore -isystem C:\usr\local\Qt\Qt-5.12_x86_64-7.2.0-posix-seh-rt_v5-rev1\include\QtCore -isystem \usr\local\Boost\boost_1_69_0\include\boost_1_69 -o debug/zzzzsomefile.o zzzzsomefile.cpp \usr\local\MinGW-w64\x86_64-7.2.0-posix-seh-rt_v5-rev1\mingw64\bin\g++ -Wl,-s -shared -Wl,-subsystem,windows -Wl,--out-implib,debug/libzzzzzzzd.a -o debug/zzzzzzzd.dll long list of .o files -LC:\usr\local\Qt\Qt-5.12_x86_64-7.2.0-posix-seh-rt_v5-rev1\lib C:\usr\local\Qt\Qt-5.12_x86_64-7.2.0-posix-seh-rt_v5-rev1\lib\libQt5Gui.a C:\usr\local\Qt\Qt-5.12_x86_64-7.2.0-posix-seh-rt_v5-rev1\lib\libQt5Core.a debug/zzzzzzzd_resource_rec.o -lglu32 -lopengl32 -lgdi32 -luser32 copy debug\libzzzzzzzd.a \users\owner\documents\mike\src\lib\x86_64-7.2.0-posix-seh-rt_v5-rev1\gcc_dll copy debug\zzzzzzzd.dll \users\owner\documents\mike\src\lib\x86_64-7.2.0-posix-seh-rt_v5-rev1\gcc_dll \usr\local\MinGW-w64\x86_64-7.2.0-posix-seh-rt_v5-rev1\mingw64\bin\g++ -c -MT debug/myLogWindow.o -MMD -MP -MF debug.d/myLogWindow.Td -g -fno-keep-inline-dllexport -O0 -std=gnu++11 -Wall -W -Wextra -fexceptions -mthreads -DUNICODE -D_UNICODE -DWIN32 -DQT_QML_DEBUG -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_CORE_LIB -DQT_NEEDS_QMAIN -I. -I\users\owner\documents\mike\src\include -isystem C:\usr\local\Qt\Qt-5.12_x86_64-7.2.0-posix-seh-rt_v5-rev1\include -isystem C:\usr\local\Qt\Qt-5.12_x86_64-7.2.0-posix-seh-rt_v5-rev1/mkspecs\win32-g++ -isystem C:\usr\local\Qt\Qt-5.12_x86_64-7.2.0-posix-seh-rt_v5-rev1\include\QtWidgets -isystem C:\usr\local\Qt\Qt-5.12_x86_64-7.2.0-posix-seh-rt_v5-rev1\include\QtGui -isystem C:\usr\local\Qt\Qt-5.12_x86_64-7.2.0-posix-seh-rt_v5-rev1\include\QtCore -isystem \usr\local\Boost\boost_1_69_0\include\boost_1_69 -o debug/myLogWindow.o myLogWindow.cpp ar -ruv debug/libmyqtlibd.a debug/myLogWindow.o *****long list of .o files ***** copy debug\libmyqtlibd.a \users\owner\documents\mike\src\lib\x86_64-7.2.0-posix-seh-rt_v5-rev1\gcc_dll\libmyqtlibd.a

Hi, Thanks for a quick response. Regarding your suggestion, I am afraid that is not possible with the way the code base is set up. Plus, I might have used the term, 'project' incorrectly. I didn't mean it as a project in the context of IDE, but a general project that I work on, of which there are multiple at any given time and share the code base.

Hi But did it produce the qm file ?

@aha_1980 Thanks for the pointer - I'll check it out.

@aha_1980 I'll try to provide this information. First, I noticed that the two such files get created each time I start the debug mode in Qt Create - none if I run without the debugger. Platform: Windows 10 Build System: (not certain what you mean) Use qmake to generate the relevant Makefiles, mingw32-make to process the Makefiles, then MinGQ-w64 for compilation and linking and debugging. Specifically, compile and link with a version of Gnu C++ (MinGW-w64\x86_64-7.2.0-posix-seh-rt_v5-rev1\mingw64\bin\g++) and the corresponding Gnu debugger (MinGW-w64\x86_64-7.2.0-posix-seh-rt_v5-rev1\mingw64\bin\gdb). Shadow-builds: don't know what this is so likely don't use it.

@Rika https://doc.qt.io/qt-5/qserialport.html#dataTerminalReady-prop

Thanks for you two.

Hi, Absolutely, in the same creator session I can toggle between toolchains, Desktop is fine, but Raspberry Pi is giving the aforementioned problem. This is my setup. Build settings: [image: c290c213-7a38-4add-9bdc-6e52d0fd6a79.png] [image: f133a4d7-5040-4b61-be94-1cc1f32f3c70.png] PATH: /home/ubuntuvm/raspi/qt5/bin:/home/ubuntuvm/raspi/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian-x64/arm-linux-gnueabihf/bin Kit: [image: 2e7d508f-5969-414d-ab2d-c6cffe6d3002.png] Device: [image: 84de4e08-e542-460d-ba9c-262d5a4ff498.png] Qt Versions: [image: d2ad4810-0593-4b3c-9a85-519dba5d8e27.png] Compilers: [image: a0a3ee52-708b-42ff-a218-6e53a8446256.png] [image: d5f2ef63-a479-4f9f-a54c-42493222cca8.png] Compiler Path (C & C++): /home/ubuntuvm/raspi/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian-x64/arm-linux-gnueabihf/bin/gcc Debuggers: [image: f6dbd68c-f15f-44f8-b54c-069630d35c9e.png] Qbs: [image: cafc88c2-128d-4242-af7b-2f5113e6fa6b.png]

Maybe you first named it 'renderarea'? I would un-promote the widget and re-promote it to be sure the correct class name is used.

It looks like it. Since it's the moc related code that has issue, I would check what version is run when you try to build your project.

Hi. The problem resolved in MacOS 10.14.4 Beta (18E220a).

@andyDT What do you see when you put the mouse cursor over that red exclamation mark? My guess is that qmake was build for ARM not x86.

@ScumCoder P.S. could you please tell me the best practice concerning insertion of screenshots on this website? I can't find the "spoiler" markdown code. I always do it like you did and that feels Ok for me. So no need to worry.

I solved a lot of imports by including QT += quick QT += widgets And I guess this is the reason I can't edit files in design mode https://felgo.com/developers/forums/t/troubles-using-designer-in-qt-creator

@hskoglund Hi, Thanks! Problem got resolved by renaming the netlib library to netagentlib, and Qt 5.12.1 builds and runs the application without any issue. These are all my code changes to rename the library: On my netlib library project file i.e. netlib.pro file I changed: -TARGET = netlib +TARGET = netagentlib Also, on my application executable project *.pro file I replaced these lines: win32:CONFIG(release, debug|release): LIBS += -L$$OUT_PWD/../netlib/release/ -lnetlib else:win32:CONFIG(debug, debug|release): LIBS += -L$$OUT_PWD/../netlib/debug/ -lnetlib else:unix: LIBS += -L$$OUT_PWD/../netlib/ -lnetlib with these lines: win32:CONFIG(release, debug|release): LIBS += -L$$OUT_PWD/../netlib/release/ -lnetagentlib else:win32:CONFIG(debug, debug|release): LIBS += -L$$OUT_PWD/../netlib/debug/ -lnetagentlib else:unix: LIBS += -L$$OUT_PWD/../netlib/ -lnetagentlib

@QiFen Thanks for sharing

Hi, Check this article. Hope this helps