Qt wiki will be updated on October 12th 2023 starting at 11:30 AM (EEST) and the maintenance will last around 2-3 hours. During the maintenance the site will be unavailable.

Snowball: Difference between revisions

From Qt Wiki
Jump to navigation Jump to search
No edit summary
 
No edit summary
Line 1: Line 1:
=Snowball=
h1. Snowball


==General==
== General ==


===Device===
=== Device ===


General information about the hardware can be found “here”: http://www.igloocommunity.org/
General information about the hardware can be found "here": http://www.igloocommunity.org/


The mainstream Linux images are Ubuntu 12.04. There is a vast amount of documentation, some of it indicates that you have to manually splice a hwpack (binary blobs) with a vanilla release, but you appear to be fine if you simply grab the Linaro 12.04 image from [http://igloocommunity.org/download/linaro/images/2012.03.1/ here] ''[igloocommunity.org]''
The mainstream Linux images are Ubuntu 12.04. There is a vast amount of documentation, some of it indicates that you have to manually splice a hwpack (binary blobs) with a vanilla release, but you appear to be fine if you simply grab the Linaro 12.04 image from "here":http://igloocommunity.org/download/linaro/images/2012.03.1/


Everything is there including a binary blob repo which should keep your blobs in good shape. There is a metapackage you need to track called:
Everything is there including a binary blob repo which should keep your blobs in good shape. There is a metapackage you need to track called:
Line 13: Line 13:
hwpack-linaro-lt-snowball-x11-base
hwpack-linaro-lt-snowball-x11-base


===Toolchain===
=== Toolchain ===


Since Ubuntu already package a arm-linux-gnueabihf toolchain, I simply grabbed theirs. There might be a better mechanism. One absolutely filthy thing I found myself doing (Since I primarily use Arch Linux) is:
Since Ubuntu already package a arm-linux-gnueabihf toolchain, I simply grabbed theirs. There might be a better mechanism. One absolutely filthy thing I found myself doing (Since I primarily use Arch Linux) is:
Line 21: Line 21:
1) Required to get the tools running
1) Required to get the tools running


Exporting a library containing 64bit, <span class="caps">ARM</span> centric binaries:
Exporting a library containing 64bit, ARM centric binaries:


export LD_LIBRARY_PATH=/opt/os/precise/usr/x86_64-linux-gnu/arm-linux-gnueabihf/lib
export LD_LIBRARY_PATH=/opt/os/precise/usr/x86_64-linux-gnu/arm-linux-gnueabihf/lib
Line 27: Line 27:
2) Required to get the toolchain finding its bits
2) Required to get the toolchain finding its bits


Symlinking Ubuntu’s arm-linux-gnueabihf folder into my personal system
Symlinking Ubuntu's arm-linux-gnueabihf folder into my personal system


ln -s /opt/os/precise/usr/arm-linux-gnueabihf /usr/arm-linux-gnueabihf
ln <s>s /opt/os/precise/usr/arm-linux-gnueabihf /usr/arm-linux-gnueabihf
<br />h3. Lighthouse backends
<br />The EGL implementation shipped as part of the aforementioned Ubuntu image is tied to X11. For this reason, the xcb backend is the logical choice (although we would like to get Qt running directly on the framebuffer on this device) and is what we have tested on the device.
<br />h2. Configuration
<br />h3. On target
<br />As per usual with Debian based hosts, adjust your apt repositories to include the appropriate source repos and:
<br />apt-get build-dep qt4-x11
<br />h3. On host
<br /> ./configure &amp;#45;device linux-snowball-g++ &amp;#45;device-option CROSS_COMPILE=/opt/os/precise/usr/bin/arm-linux-gnueabihf</s> &amp;#45;sysroot /stores/st/rootfs -opengl es2


===Lighthouse backends===
== Usage ==


The <span class="caps">EGL</span> implementation shipped as part of the aforementioned Ubuntu image is tied to X11. For this reason, the xcb backend is the logical choice (although we would like to get Qt running directly on the framebuffer on this device) and is what we have tested on the device.
The Snowball has a mini USB port so you require an appropriate adapter to interface this with standard USB hardware. Outside of this, your primary means of interacting with the device is via minicom/screen, again driven through this micro-USB port.


==Configuration==
== Caveats ==


===On target===
Spurious errors about an inability to find a DRI module and hence falling back to software rendering:
 
As per usual with Debian based hosts, adjust your apt repositories to include the appropriate source repos and:
 
apt-get build-dep qt4-x11
 
===On host===
 
./configure -device linux-snowball-g++ -device-option <span class="caps">CROSS</span>_COMPILE=/opt/os/precise/usr/bin/arm-linux-gnueabihf- -sysroot /stores/st/rootfs -opengl es2
 
==Usage==
 
The Snowball has a mini <span class="caps">USB</span> port so you require an appropriate adapter to interface this with standard <span class="caps">USB</span> hardware. Outside of this, your primary means of interacting with the device is via minicom/screen, again driven through this micro-<span class="caps">USB</span> port.
 
==Caveats==
 
Spurious errors about an inability to find a <span class="caps">DRI</span> module and hence falling back to software rendering:


http://igloocommunity.org/pipermail/users/2012-March/000597.html
http://igloocommunity.org/pipermail/users/2012-March/000597.html
No worries, apparently, although this leaves me weary

Revision as of 10:33, 24 February 2015

h1. Snowball

General

Device

General information about the hardware can be found "here&quot;: http://www.igloocommunity.org/

The mainstream Linux images are Ubuntu 12.04. There is a vast amount of documentation, some of it indicates that you have to manually splice a hwpack (binary blobs) with a vanilla release, but you appear to be fine if you simply grab the Linaro 12.04 image from "here&quot;:http://igloocommunity.org/download/linaro/images/2012.03.1/

Everything is there including a binary blob repo which should keep your blobs in good shape. There is a metapackage you need to track called:

hwpack-linaro-lt-snowball-x11-base

Toolchain

Since Ubuntu already package a arm-linux-gnueabihf toolchain, I simply grabbed theirs. There might be a better mechanism. One absolutely filthy thing I found myself doing (Since I primarily use Arch Linux) is:

(/opt/os/precise is an Ubuntu Precise chroot)

1) Required to get the tools running

Exporting a library containing 64bit, ARM centric binaries:

export LD_LIBRARY_PATH=/opt/os/precise/usr/x86_64-linux-gnu/arm-linux-gnueabihf/lib

2) Required to get the toolchain finding its bits

Symlinking Ubuntu's arm-linux-gnueabihf folder into my personal system

ln s /opt/os/precise/usr/arm-linux-gnueabihf /usr/arm-linux-gnueabihf
h3. Lighthouse backends
The EGL implementation shipped as part of the aforementioned Ubuntu image is tied to X11. For this reason, the xcb backend is the logical choice (although we would like to get Qt running directly on the framebuffer on this device) and is what we have tested on the device.
h2. Configuration
h3. On target
As per usual with Debian based hosts, adjust your apt repositories to include the appropriate source repos and:
apt-get build-dep qt4-x11
h3. On host
./configure &#45;device linux-snowball-g++ &#45;device-option CROSS_COMPILE=/opt/os/precise/usr/bin/arm-linux-gnueabihf
&#45;sysroot /stores/st/rootfs -opengl es2

Usage

The Snowball has a mini USB port so you require an appropriate adapter to interface this with standard USB hardware. Outside of this, your primary means of interacting with the device is via minicom/screen, again driven through this micro-USB port.

Caveats

Spurious errors about an inability to find a DRI module and hence falling back to software rendering:

http://igloocommunity.org/pipermail/users/2012-March/000597.html