BeagleBone-Debian Qt5 Toolchain

[manoncloud9]

I’m evaluating VisualGDB for a project to be built on the BeagleBone and have been going through the tutorials.

I followed the instructions to download, burn the image to a SD Card and successfully booted the Debian image from the card. This is the image I used:

bone-debian-7.8-lxde-4gb-armhf-2015-03-01-4gb.img

Following the tutorial titled “Creating Qt5 Projects for Beaglebone-Debian with Visual Studio”, I downloaded the matching toolchain:

beaglebone-gcc4.6.3-Debian.exe

and installed it successfully.  When attempting to start a project and “using previously configured Qt tools” as stated in the instructions, I can’t find the ..\user\local\qt5\.. portion of the installed toolchain.  Did I misread the tutorial where it says to “download our toolchain with a pre-built QT” or are there additional steps that I need to perform that I’ve overlooked?  Should I have actually completed the other tutorial where the Qt 5.5 framework is built?

Your assistance with this evaluation will be greatly appreciated!

Thanks!

[support]

Hi,

Sorry for the confusion, looks like the Beaglebone page contained the wrong toolchain link. We have updated the page, please try downloading it again.

[manoncloud9]

Great!  I downloaded the toolchain and loaded it successfully.  Now when I create the demo project I have to find the toolchain by selecting the option (Select toolchain manually by locating gdb.exe) because a new entry for the installed toolchain does not show up in the “Cross-toolchain” drop down of the “New Linux Project” dialog box.  I assumed it was referring to arm-linux-gnueabihf-gdb.exe which I found in C:\SysGCC\Beaglebone\bin.

I then followed the instructions to “configure QT settings” finding the appropriate Qmake binary and Cross-specs directory and press OK.  The “Mismatching environment detected” dialog box did not appear so I pressed “Finished” and received the following Error Message:

“Test program appears inconsistent. Expected return code 108. Actual return code 127”

and in the detailed log box:

Tool arguments:
/home/debian/VisualGDB_ToolchainTestProgram_Deployed: error while loading shared libraries: libQt5Widgets.so.5: cannot open shared object file: No such file or directory

Are these problems now a result of having loaded the incorrect toolchain to begin with?

What course of action should I pursue from here?

Thanks

 

[support]

Hi,

Looks like we forgot to mention in the tutorial that you need to upload the Qt libraries from the toolchain to your device. We have updated the tutorial, please upload the files as shown below:

[manoncloud9]

Thanks for the guidance and fixes to the tutorial, I now have the files copied to the Beaglebone as instructed and ready to build.

The next issue occurs when I get to step 7 of the tutorial.  According to the documentation reopening the project should straighten out IntelliSense so I can compile.  What happens if that doesn’t work and I’m still stranded unable to build the demo?

If I can get through this issue and actually compile and run both on the local platform and on the Beaglebone, I’m inclined to go ahead and purchase the product and get started on my project.  Your assistance is greatly appreciated!

[support]

Hi,

The ui_MainWindow.h file is generated during build. So if you build the project and re-open it, IntelliSense should it pick it. If this does not happen, please check whether the file actually exists and whether its directory got added to the IntelliSense directories in VisualGDB Project Properties.

[Author]

Posts