Among the devs possibilities

mouha
Hi,

I think I'm not the only one who would like to know among all the Angstrom,
OPenEmbedded, BuildRoot, etc.... 
what is the way to develop console and Qt apps. 

As it's for "regular" devs, i.e. : I would like to do drivers, console and
Qt softwares so directly have a uboot+kernel+gcc as explained in the docs
doesn't appear to be the best solution.

bob
on a separate work station.

If you are very lucky then with an "emulator" but if you are not so lucky:

1. get your  board.
2. get a suitable RELIABLE & STABLE connection  between your workstation
and your board.
3. get your board working and back it up.

4. start developing  your "applications" via a cross compiler , only a
madman or sadomasochist attempts to compile and link the software on the
target board.

That is to say , yes you CAN find a compiler that works within the memory
of  your arm board , but why would you compile on a single processor system
running at a few hundred MHZ , when you can cross compile on a multi core/
multiprocessor  Intel machine.

5.  USE a NFS where possible, do not attempt to continually "flash" your
board Nand/Nor ram.
If you really must, then use SD cards to transfer between systems.

6. Golden rule....... use GIT or some other development warehouse
(Subversion, CVS, whatever)

7. for long term sanity don't "hack" , any moron or kindergardener can
hack, only a true pro writes software for the future (that is not to say
you cannot hack as a quick test, but long term it is usually a bad idea)
8.  what ever you do, document correctly, if you "hack" the kernel use a
standard searchable term to identify your hacks.

mouha
[Quote]
only a madman or sadomasochist attempts to compile and link the software on
the target board [/Quote]

Oh yes ! There is not much advantages to do that.

What I understand is : doing it via cross compiling and not OpendEmbedded /
BuildRoot tools 


Thanks for answering Bob.