I took the native build route along with Mark.

Much of our software is not specific to Gumstix, the parts that are are in wrappers.  It is far easier to support a single "vanilla" Linux tool chain than to deal with OE on the Gumstix, Gnu tools everywhere else.

This does mean a development SD card, or cross compiling.  It is not a big deal.

On Sun, Mar 4, 2012 at 11:55 PM, Alex Gibson <alxx@alexthegeek.com> wrote:
On 3/03/2012 12:24 AM, Patrik Svensson wrote:
> Hi again, I am waiting for my first gumstix computer (a firestorm with
> gallop43 and a LCD screen).
> Thanks for the tips on accesspoints.
> What development system is the best (angstrom,android, embedded)?
> I was thinking of developing a simple logging system the uses WIFI (as
> access point) and serial ports and maybe a GUI on the LCD screen, it
> would be nice if the USB ports worked without too much trouble.
> Shall I use a cross environment in linux (any distr better suited for
> gumstix) or is it best to work on the target all the time?
> Regards
> Patrik

I'd suggest sticking with the gumstix provided version of angstrom open

Have a build box or vm to build customised images
and have the tools onboard the gumstix as well just in case you need to
make small changes out in the field.

I do most of my development in python so I usually log in remotely
and upload code or edit it on the command line with vim.
(vim doesn't work well via hyperminal)


Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
gumstix-users mailing list