QT 4.8.5 and BeagleBone Black problem

Sysprogs forums › Forums › VisualGDB › QT 4.8.5 and BeagleBone Black problem

Log In Register Lost Password
Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • January 17, 2014 at 09:53 #746
    Mantas
    Participant

    Hi,

    I’ve set up everything as per tutorial up to step 15, but I have the following error when trying to compile:

    1>

Build started: Project: QT, Configuration: Debug Win32

1>  VisualGDB: Attempting inline build...
    
1>  VisualGDB: Executing prebuild actions
    
1>  VisualGDB: Run "C:SysGCCbeagleboneQtOtherqmake.exe  QT.pro CONFIGNAME=Debug " in directory "F:BeagleBoneBlack_ProjectsQTQT" on local computer
    
1>  VisualGDB: Run "cmd.exe /c "C:SysGCCbeaglebonebinmake.exe"" in directory "F:BeagleBoneBlack_ProjectsQTQT" on local computer
    
1>  The syntax of the command is incorrect.
    
1>  make: *** [Debug/QT] Error 1
    
1>

1>  Command exited with code 2
    
1>  Executable: cmd.exe
    
1>  Arguments: /c "C:SysGCCbeaglebonebinmake.exe"
    
1>  Directory: F:BeagleBoneBlack_ProjectsQTQT
    
1>EXEC : error : Build has failed. See the Output window for more details.
    
1>C:Program Files (x86)MSBuildMicrosoft.Cppv4.0V120Microsoft.MakeFile.Targets(38,5): error MSB3073: The command ""C:Program Files (x86)SysprogsVisualGDBVisualGDB.exe" /build "F:BeagleBoneBlack_ProjectsQTQTQT.vcxproj" "/solution:F:BeagleBoneBlack_ProjectsQTQT.sln" "/config:Debug" "/platform:Win32"" exited with code 1.
    
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========
    

    
Build Summary

00:01.091 - Failed  - Debug Win32 - QTQT.vcxproj
    

    
Total build time: 00:03.638
    

    
========== Build: 0 succeeded or up-to-date, 1 failed, 0 skipped, Completed at 2014.01.17 11:41:31 ==========

    Best regards,
    Mantas

    January 18, 2014 at 02:22 #2969
    ket
    Participant

    HI,

    Please check inside the Makefile in the project directory if there are any obvious issues with targets or recipes like non-existing path names.

    You can also run the make command with the -d argument to get a more thorough output from make. For this add the -d flag to make command arguments on the qmake project settings page in VisualGDB Project Properties. Then examine the log for any errors.

    July 11, 2014 at 12:22 #2970
    Anonymous
    Participant

    Hi,
    did you solve the problem?
    I have the same problem. but with a raspberry pi.

  • Author
    Posts
Log In Register Lost Password
Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.