- This topic has 1 reply, 2 voices, and was last updated 8 years, 2 months ago by
.
-
Posts
-
Hello there,
i’m trying since yesturday to crosscompile the QT projcet for beaglebone using MS Visual Studio. Everything go fine, even the compiling and running the “Test Application” by the project wizard …
but as soon as i get to the application itself and try to build it it fails!
1>—— Erstellen gestartet: Projekt: LinuxProject1, Konfiguration: Debug Win32 ——
1> VisualGDB: Run “C:\SysGCC\Beaglebone\arm-linux-gnueabihf\sysroot\usr\local\qt5\bin\qmake.exe LinuxProject1.pro CONFIGNAME=Debug” in directory “C:\bbb_vs\LinuxProject1\LinuxProject1” on local computer
1> VisualGDB: Run “cmd.exe /c “C:\SysGCC\Beaglebone\bin\make.exe”” in directory “C:\bbb_vs\LinuxProject1\LinuxProject1” on local computer
1> C:\SysGCC\Beaglebone\arm-linux-gnueabihf\sysroot\usr\local\qt5\bin\uic.exe MainWindow.ui -o Debug\ui_MainWindow.h
1> make: *** [Debug\ui_MainWindow.h] Error -1073741515
1> ————————————————————-
1> Command exited with code 2
1> Executable: cmd.exe
1> Arguments: /c “C:\SysGCC\Beaglebone\bin\make.exe”
1> Directory: C:\bbb_vs\LinuxProject1\LinuxProject1
1>VisualGDB : error : Command-line action failed
1>EXEC : error : Build has failed. See the Output window for more details.
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.MakeFile.Targets(38,5): error MSB3073: Der Befehl “”C:\Program Files (x86)\Sysprogs\VisualGDB\VisualGDB.exe” /build “C:\bbb_vs\LinuxProject1\LinuxProject1\LinuxProject1.vcxproj” “/solution:C:\bbb_vs\LinuxProject1\LinuxProject1.sln” “/config:Debug” “/platform:Win32″” wurde mit dem Code 1 beendet.
========== Erstellen: 0 erfolgreich, 1 fehlerhaft, 0 aktuell, 0 übersprungen ==========can someone help?
Hi,
This error usually happens when some libraries are not found in the PATH directories. Please try launching the C:\SysGCC\Beaglebone\arm-linux-gnueabihf\sysroot\usr\local\qt5\bin\qmake.exe executable manually from Explorer and check if it complains about any missing libraries.
Normally VisualGDB should setup the paths automatically, so most likely your toolchain is corrupt (perhaps your antivirus triggered a false positive on some of the DLLs from the toolchain?). Please try reinstalling the toolchain and check your antivirus log for messages about blocked files.
- You must be logged in to reply to this topic.