Getting Qt onto the BeagleBoard????

My name's Scott Bonner and I'm trying to get Qt on to the BeagleBoard.
I've been searching the internet trying to find instructions on how to
do this but I'm very new to this and am needing a step by step
instruction on how to do this. I was wondering if anyone could help me
out with this and just remember that I am quite new to embedded linux
and the BeagleBoard itself. Thanks

My name's Scott Bonner and I'm trying to get Qt on to the BeagleBoard.
I've been searching the internet trying to find instructions on how to
do this but I'm very new to this and am needing a step by step
instruction on how to do this. I was wondering if anyone could help me
out with this and just remember that I am quite new to embedded linux
and the BeagleBoard itself. Thanks

OpenEmbedded has qt4-embedded and qt4-x11-free recipes that will bring
you the needed software. Though there is still a problem of getting
toolchain capable to cross-compile qmake based stuff (I'm working
currently on putting the needed fixes to OE). For now, you can build
qt toolchain by yourself from sources with the help of toolchain that
OE can also build for you.

Thanks Ihar, I will have to try that. This might seem like a foolish
question but do you know of any cross-compilier for taking a completed
GUI from Qt developed in Ubuntu to compile it for the arm processor?

In addition I have started to document the Qt porting process for OMAP
on the wiki:
http://wiki.davincidsp.com/index.php/Building_Qt

It is not 100% complete yet so let me know if you run into issues. We
have just done it for BeagleBoard.

In addition I have started to document the Qt porting process for OMAP
on the wiki:
http://wiki.davincidsp.com/index.php/Building_Qt

It is not 100% complete yet so let me know if you run into issues. We
have just done it for BeagleBoard.

Where can we find linux-omap3-g++ mentioned in your link?

The other thing is that I am using Rev B BeagleBoard not Rev C

It is just a new mkspec/qws folder that I created. I updated the wiki
link with some info on that. But obviously this step depends a lot on
your environment. Qt is so modular and flexible that I can only give a
basic example. I might add more to the new Qt Tips page I opened
yesterday. Maybe the community will add there too.

If you think your issues are due to insufficient memory (128MB on
RevB) then I don't think so.
I am running Qt on OMAP3 EVMs with 128MB and on the OMAP-L1 platform
where we have only 64MB RAM at the moment (32MB often used for a
RAMDISK). So generally I haven't seen out-of-memory errors with any of
the examples/demos or my programs (but they are comparably small). The
browser demo using webkit is really huge...

I could be off here but Debian has been having packages compiled for
arm processors for a long time. In fact, they even have a
cross-compiler toolchain an aptitude install away. Check out the arm
port for debian or www.emdebian.org.

I have some good news in that following your directions I have been
able to compile and install Qt for Embedded. However now my problem
seems to be that when I compile a GUI on my laptop for the Beagle
Board, its not compiling the GUI properly. The compiled version still
runs on my desktop which I find odd. The name of the GUI is beasy.
When I run it on my Beagle Board by typing "./beasy" I receive the
error of "./beasy: line 1: syntax error: "&" unexpected
(expecting")")". Can anyone interpret what this error means or have a
solution or suggestion? Thanks for taking your time for reading this

Sounds like the program is compiled for x86 not cross compiled for ARM.

Here is a list of information on getting that going.
http://www.elinux.org/ARMCompilers

Your program is compiled with wrong tools and cross-toolchain.

You can use meta-toolchain-qte recipe and some fixes for qt4 for
OpenEmbedded to get beagleboard toolchain with Qt4/Embedded and qt4
tools properly set up for cross-compilation (moc, uic, qmake) from:
http://github.com/booxter/oedev/tree/org.openembedded.dev
The needed patches are already sent to OpenEmbedded mailing list so I
think you can see them in OE upstream .dev tree after few days.