Sysprogs forums › Forums › VisualGDB › QT project build
- This topic has 1 reply, 2 voices, and was last updated 1 year, 2 months ago by support.
-
AuthorPosts
-
August 27, 2023 at 10:30 #34636mmcafeParticipant
Hi,
I’m interested in purchasing VisualGDB, but I’m currently testing a trial version.
After creating my first project in Visual Studio 2023 using QT I got errors as below. I will ask for help.Regards,
Jaroslaw Kowalewski
http://www.mmcafe.plRemoving D:\Linux\LinuxProject1/build/VisualGDB/Debug…
Reconfiguring project due to missing Makefile…
Running CMake: C:\Users\mmcafe\AppData\Local\VisualGDB\CMake\bin\cmake.exe ../../.. -G “Ninja” -DCMAKE_BUILD_TYPE=DEBUG -DTOOLCHAIN_ROOT=D:/SysGCC -DCMAKE_MAKE_PROGRAM=”C:/Program Files (x86)/Sysprogs/VisualGDB/ninja.exe” -DCMAKE_TOOLCHAIN_FILE=D:\Linux\LinuxProject1/build/VisualGDB/Debug/toolchain.cmake
CMake Deprecation Warning at CMakeLists.txt:4 (cmake_minimum_required):
Compatibility with CMake < 2.8.12 will be removed from a future version of
CMake.Update the VERSION argument <min> value or use a …<max> suffix to tell
CMake that the project does not need compatibility with older versions.— The C compiler identification is GNU 10.2.1
— The CXX compiler identification is GNU 10.2.1
— Detecting C compiler ABI info
— Detecting C compiler ABI info – done
— Check for working C compiler: D:/SysGCC/bin/aarch64-linux-gnu-gcc.exe – skipped
— Detecting C compile features
— Detecting C compile features – done
— Detecting CXX compiler ABI info
— Detecting CXX compiler ABI info – done
— Check for working CXX compiler: D:/SysGCC/bin/aarch64-linux-gnu-g++.exe – skipped
— Detecting CXX compile features
— Detecting CXX compile features – done
— Configuring done
— Generating done
CMake Warning:
Manually-specified variables were not used by the project:TOOLCHAIN_ROOT
— Build files have been written to: D:/Linux/LinuxProject1/build/VisualGDB/Debug
Run “C:\PROGRA~2\Sysprogs\VISUAL~1/ninja.exe ” in directory “D:\Linux\LinuxProject1/build/VisualGDB/Debug” on local computer
C:\PROGRA~2\Sysprogs\VISUAL~1/ninja.exe
[1/5] Automatic MOC and UIC for target LinuxProject1
[2/5] Building CXX object CMakeFiles/LinuxProject1.dir/LinuxProject1_autogen/mocs_compilation.cpp.o
[3/5] Building CXX object CMakeFiles/LinuxProject1.dir/LinuxProject1.cpp.o
[4/5] Building CXX object CMakeFiles/LinuxProject1.dir/MainWindow.cpp.o
[5/5] Linking CXX executable LinuxProject1
FAILED: LinuxProject1
cmd.exe /C “cd . && D:\SysGCC\bin\aarch64-linux-gnu-g++.exe –sysroot=D:/SysGCC/aarch64-linux-gnu/sysroot -g -rdynamic CMakeFiles/LinuxProject1.dir/LinuxProject1_autogen/mocs_compilation.cpp.o CMakeFiles/LinuxProject1.dir/LinuxProject1.cpp.o CMakeFiles/LinuxProject1.dir/MainWindow.cpp.o -o LinuxProject1 D:/SysGCC/aarch64-linux-gnu/sysroot/usr/lib/aarch64-linux-gnu/libQt5Widgets.so.5.15.2 -lglib-2.0 -licuuc -lharfbuzz -licui18n -lpcre2-16 -lGL -ldouble-conversion -lzstd -lmd4c -lz D:/SysGCC/aarch64-linux-gnu/sysroot/usr/lib/aarch64-linux-gnu/libQt5Gui.so.5.15.2 D:/SysGCC/aarch64-linux-gnu/sysroot/usr/lib/aarch64-linux-gnu/libQt5Core.so.5.15.2 && cd .”
d:/sysgcc/bin/../lib/gcc/aarch64-linux-gnu/10/../../../../aarch64-linux-gnu/bin/ld.exe: cannot find -lglib-2.0
d:/sysgcc/bin/../lib/gcc/aarch64-linux-gnu/10/../../../../aarch64-linux-gnu/bin/ld.exe: cannot find -lharfbuzz
d:/sysgcc/bin/../lib/gcc/aarch64-linux-gnu/10/../../../../aarch64-linux-gnu/bin/ld.exe: cannot find -lpcre2-16
d:/sysgcc/bin/../lib/gcc/aarch64-linux-gnu/10/../../../../aarch64-linux-gnu/bin/ld.exe: cannot find -ldouble-conversion
d:/sysgcc/bin/../lib/gcc/aarch64-linux-gnu/10/../../../../aarch64-linux-gnu/bin/ld.exe: cannot find -lmd4c
collect2.exe: error: ld returned 1 exit status
ninja: build stopped: subcommand failed.
————————————————————-
Command exited with code 1
Executable: C:\PROGRA~2\Sysprogs\VISUAL~1/ninja.exe
Arguments:
Directory: D:\Linux\LinuxProject1/build/VisualGDB/Debug
Command-line action failed========== Project Rebuild Summary ==========
LinuxProject1 rebuilt in 00:06
========== Rebuild: 0 Succeeded, 1 Failed, 0 Skipped ==========- This topic was modified 1 year, 2 months ago by mmcafe.
August 27, 2023 at 15:51 #34638supportKeymasterHi,
It looks like the toolchain you are using, or the project itself, is broken. VisualGDB cannot automatically fix – all it can do is provide convenient configuration and debugging GUI that can make the development easier.
Please make sure you can build the project for the same device using the same toolchain and build system outside VisualGDB first. Once it works, feel free to share more details about your setup and we will help you configure VisualGDB to build and debug the project.
-
AuthorPosts
- You must be logged in to reply to this topic.