Talk:Raspberry Pi Beginners Guide

From Qt Wiki
Jump to navigation Jump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

openSSL Hint

I just want to add some additional hint. Raspbian doesn't come with the development libraries for openSSL (libssl-dev), so you won't have support for this functionality.

What does it mean in practice? You won't be able to use classes like QSslSocket, QSslConfiguration, etc..

To correct this problem, you just have to follow the procedure explained below to update your Raspbian OS image:

Copy Raspbian image to your FAT32 formatted SD card:

sudo dd bs=1M if=2015-02-16-raspbian-wheezy.img of=/dev/sdb (sdb might be different in your case)

Start up your Raspberry Pi, upgrade Raspbian and install OpenSSL-dev:

pi$ sudo apt-get update
pi$ sudo apt-get upgrade
pi$ sudo apt-get install libssl-dev

Turn off your RPi, remove the SD card and mount it in your computer. Then create the new image:

~/opt$ dd bs=1M if=/dev/sdb of=raspbian-openssl.img
~/opt$ sync

From now you will need to use: raspbian-openssl.img instead of the original 2015-02-16-raspbian-wheezy.img

Going over page

It looks like this page hasn't been properly updated in about two years. Dead links all round etc. I'm currently trying to set up a cross compiler so that I can compile an application on my PC and then ssh it over to the Raspberry Pi. I'll try and get it working following these steps and try editing the article where things don't seem to be working. Jonnax (talk) 15:02, 12 June 2015 (UTC)

Method for renaming extracted .img file?

There's a bit of an issue with keeping the page up to date because the zip file that we wget will have the file inside named something like: 2015-05-05-raspbian-wheezy.img Since the date is the date of the image this will change when raspbian decides to update. Is there a command to change the name of the extracted file to something like "raspbian-image.img" that way the instructions can be more permanent. Jonnax (talk) 16:47, 12 June 2015 (UTC)

Bash Script Section

I removed the following part of the main article:

  •  $ ./bakeqtpi.bash help

Since the script here uses dead links that redirect to phishing sites. Perhaps someone could fix and change the script? Jonnax (talk) 17:32, 12 June 2015 (UTC)

It works!

Managed to follow the instructions and with a bit of work got it to work correctly. That's cross compilation and auto transfer of project to the raspberry pi. I'll try and do a bit more cleaning up and make things a bit more concise Jonnax (talk) 23:39, 14 June 2015 (UTC)

fixQualifiedLibraryPaths - incorrect usage

Has the person who has added the usage of `sudo ./fixQualifiedLibraryPaths /MOUNT_ROOTFS_PATH /PATH_TO_ARM_COMPILER` even tested it???

At the very beginning of the script you can see (do mind the amazing comment at the top...):

   #This script is ugly, feel free to fix it
   if [ "$#" -ne 1 ]; then
       echo "usage ./cmd target-rootfs"
       exit -1

Given the example how to use this script it will ALWAYS fail since it passes 2 arguments instead of one so it fall into this IF statement and exits the script without doing anything useful.Red Baron (talk) 17:23, 24 July 2016 (UTC)

fix this thing, or let someone else!!!

This entire process is utterly broken.. Bad links, code that wont compile, scripts that don't work.. did you even try any of it?????

Ive added changes to the wiki that have not been moderated yet..

If you provide a "how to" consider the following...

1) keep it updated or 2) step aside and let someone else do it..

Its the official QT wiki at least this one should be right...

I tried 17 different tutorials now, took me about 3 Weeks and non of that worked due to bad links, code that won't compile ... =

This is really shining a bad light on the glorious qt framework...

code to clone one rev back

This line in the details forces a complete replication, however if you do the instructions as they read you could end up with an unstable version that wont compile, (especially when doing a cross compile..)

git clone git://

instead consider going one rev back... in my case 5.8 refused to compile, so i tried 5.7 with the following command..

git clone -b '5.7' --single-branch --depth 1 git://