Does anyone know how to use QT to make application for arm board ?
 

Hello,

I am asking this because i am kind of lost.
I tried following tutorials online but none of them seems to work and i am losing hope on how to do this.

All depends on the board. I have a Beagleboard Black Rev C running Debian and have installed the Qt package. Qt applications compile on the board and also run.

I'm not experienced in application programming but the person who is will need much more detailed information.

What is the end goal you are trying to achieve? What type of system are you using it on? What steps have you tried if any?

Please give details and elaborate further so someone can better assist you.

It is a sbc6000x, with a at91sam9261 micro running on a linux 2.6.24. An armv5 board.

Right now i have qt creator, a compiler toolchain working (i was able to make a little hello world executable when using a simple text editor to create a .c file) and the board.

Kernel 2.6 is old, as is this board. I'd recommend Qt 4.6 or no greater than Qt 4.8, see if you can download the opensource distribution and build it for cross compilation.

Although you're description saying you got a hello world compiled and running causes confusion. Does this work already?

The hello world is simply a .c i did with gedit and compiled using in the terminal :
I have qt creator 3.0.1 with qt 5.2.1 installed right now but i will try to download qt 4.6 here ( http://download.qt.io/archive/qt/4.6...c-4.6.0.tar.gz ).

To cross compile it i was thinking about following this http://www.qtfr.org/viewtopic.php?id=16417 (in french but you really only need to understand the code)

If this work, do i only need to move/chmod the executable to my /bin folder or do i have to copy things like libraries and stuff on the board ?

Little unclear on how that ultimately works, if I recall they allow you to specify an install path and a good idea is to mount a representation of your RFS for your target and then specify the install path to be on there so that the libraries (when you configure and build Qt) end up within that RFS. And another reason why they do that is because the real path as far as Qt is concerned is something like /usr/local/Trolltech/Qt-4.6.0/bin, and so forth. But obviously while you configure and install it, it's really something like /media/mount-name/..., and that's what the install process is supposed to recognize, the fact that the path at time of build is de-referenced somehow and when you go to use the libraries on the target, they are in a path which makes sense for Qt. You need to check out the documentation on configure for that. What I usually do is ./configure --help > config.hlp to put all the output of the help data into a log file.