[QtonPi] Recommendations for getting productive using Qt5 on Raspberry Pi

[Chris Griffiths]

Jonathan,

This page is your best start: http://qt-project.org/wiki/RaspberryPi
It details cross compiling QT5 for the Raspberry pi.

If you're new to cross compiling the overall process is:
1) Save a copy of the Raspberry Pi ARM file system to a folder on your
desktop. (will need some links corrected)
2) Obtain the correct toolchain - thats a compiler, linker, libraries etc
required to produce an ARM executable
3) Download the QT5 source for the modules you need
4) Build with a statement like the following:

   1. $ cd <qtbase>
   2. $ ./configure -prefix <your prefix> -release \
   3.   -device linux-rasp-pi-g++ -make libs \
   4.   -device-option CROSS_COMPILE=<your toolchain path>/bin/arm-none-
   linux-gnueabi-
   5.   -sysroot <your sysroot path>
   6. $ make install

Where:
  -sysroot = The raspberry Pi filesystem root folder
  -prefix = the location the build components will be placed.

Note: The build will be spit between your desktop filesystem and the
raspberry pi filesystem. Qmake and other required build binaries will be
placed in -prefix folder in your desktop filesystem. The ARM build of QT
will be put in <sysroot>/<prefix>.
You need to run make install with an account which has permissions to both
of these locations.

5) After QT is built copy <sysroot>/<prefix> to your Raspberry Pi.
6) To cross compile your own project just make sure you use the qmake at
<prefix>/bin/qmake. The cross compile environment will then be used
automatically.

There is far more required detail on the wiki, but I hope this overview of
the process helps.

Chris

On Sat, Aug 4, 2012 at 2:40 PM, Jonathan Greig <redteam316 at gmail.com> wrote:

> Alex,
> Any idea on when the next release will be?
> Otherwise, I'm wondering how long does it take to build qt5 for the pi? I
> thought I read somewhere you could cross compile on a desktop for the pi.
> What configure options should we use or other hints?
>
> I just loaded the Raspbian Wheezy armhf on my pi. After finding out the
> debs in the repo were for armel, I just installed other dev stuff I'll need
> like git and svn until I proceed further with Qt.
>
>  On Tue, Jul 24, 2012 at 3:35 PM, Alysse Martyn <alysse.martyn at gmail.com>wrote:
>
>>  Thank you Alex. Door 2) it is. Off to unravel the mysteries therein
>>
>>
>>
>>
>> On Tue, Jul 24, 2012 at 6:35 AM, Alex Bradbury <asb at asbradbury.org>wrote:
>>
>>> On 24 July 2012 13:36, Alysse Martyn <alysse.martyn at gmail.com> wrote:
>>> > New to Raspberry Pi, and picking up Qt again after about a 4 year
>>> hiatus.
>>> >
>>> > Where do you recommend I get started?
>>> >
>>> > 1) QtOnPi distro 0.2 from raspberrypi.org/downloads?  Is this the
>>> active
>>> > development "head" going forward? I have the hello-qtonpi going.
>>> > 2) Wheezy Beta from the blog post at raspberrypi.org?  Not sure I
>>> understand
>>> > the comments about "first class citizen" found here:
>>> > http://qt-project.org/wiki/RaspberryPi -- do I start by trying to
>>> shoehorn
>>> > the referenced Linaro toolchain into a Debian dev box?
>>>
>>> The wheezy beta is the best place to get started. The QtOnPi has not
>>> seen any active development for some time, and will likely be removed
>>> from the download page in the near future. The armel wheezy beta
>>> contains a recent qt5 build. This is currently missing in the new
>>> Raspbian-based armhf image, but hopefully this will be rectified in
>>> the next release.
>>>
>>> Alex
>>>
>>
>>
>> _______________________________________________
>> QtonPi mailing list
>> QtonPi at qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/qtonpi
>>
>>
>
> _______________________________________________
> QtonPi mailing list
> QtonPi at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/qtonpi
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.qt-project.org/pipermail/qtonpi/attachments/20120807/e467cb88/attachment.html