[jallard]

The pre-built Qt binaries work. Thank you.

We love the concept of VisualGDB, and although there are some kinks to work out and documentation that needs updating (at least with Beaglebone support), the technical support, alone, is worth the cost.

[jallard]

Followed tutorial preview. Now getting this:

$ ../qt-everywhere-opensource-src-5.5.0/configure -platform win32-g++ -xplatfor
m linux-arm-gnueabi-g++ -release -device linux-beagleboard-g++ -sysroot C:/SysG
CC/Beaglebone/arm-linux-gnueabihf/sysroot -prefix /usr/local/qt5 -device-option
CROSS_COMPILE=c:/SysGCC/Beaglebone/bin/arm-linux-gnueabihf- -qt-xcb
+ cd qtbase
+ /c/qt/qt-everywhere-opensource-src-5.5.0/qtbase/configure -top-level -platform
win32-g++ -xplatform linux-arm-gnueabi-g++ -release -device linux-beagleboard-g
++ -sysroot C:/SysGCC/Beaglebone/arm-linux-gnueabihf/sysroot -prefix /usr/local/
qt5 -device-option CROSS_COMPILE=c:/SysGCC/Beaglebone/bin/arm-linux-gnueabihf- –
qt-xcb

Preparing build tree…
Running configuration tests…
The test for linking against libxcb failed!
Use of pkg-config is not enabled, maybe you want to pass -force-pkg-config?
You might need to install dependency packages for libxcb.
See src/plugins/platforms/xcb/README.

Seems like libxcb is in the proper location: C:\SysGCC\Beaglebone\arm-linux-gnueabihf\sysroot\lib\arm-linux-gnueabihf

Not sure why we’re getting the error.

Also, there’s no “tools” folder or “updatesysroot.bat” in the beaglebone toolchain install.

 

[jallard]

We are getting this error when attempting to build configure Qt:

$ ../qt-everywhere-opensource-src-5.5.0/configure -platform win32-g++ -xplatfor
m linux-arm-gnueabi-g++ -release -opengl es2 -device linux-rasp-pi2-g++ -sysroo
t C:/SysGCC/Raspberry/arm-linux-gnueabihf/sysroot -prefix /usr/local/qt5 -devic
e-option CROSS_COMPILE=C:/SysGCC/Raspberry/bin/arm-linux-gnueabihf- -qt-xcb

Preparing build tree…
Running configuration tests…
The OpenGL ES 2.0 functionality test failed!
Use of pkg-config is not enabled, maybe you want to pass -force-pkg-config?
You might need to modify the include and library search paths by editing
QMAKE_INCDIR_OPENGL_ES2, QMAKE_LIBDIR_OPENGL_ES2 and QMAKE_LIBS_OPENGL_ES2 in
c:/qt/qt-everywhere-opensource-src-5.5.0/qtbase/mkspecs/devices/linux-rasp-pi2-
g++.

[jallard]

Thanks for the info. My point, though, is that even the Angstrom tutorials do not seem to work, apparently because the new VisualGDB tools only support Debian as far a we can tell. In other words, it appears that there is no way to use the latest VisualGDB with a Beaglebone Angstrom or Debian image.

We will try the Raspberry Pi cross-compile and see if we can make sense of this.

 

[jallard]

Either Angstrom or Debian would be fine. We are trying to develop with Qt but it is unclear what distro we are supposed to use. The tutorials do not seem to match the choices we have in VisualGDB. VisualGDB only has Debian as a choice, but other parts of the tutorial seem to rely on Angstrom.

Thanks,
Jim

[Author]

Posts