[ECOS] Re: MicroWindows, network stack, framebuffer API

Gábor Török tgabor84@gmail.com
Mon Nov 17 18:24:00 GMT 2008

On Wed, Nov 5, 2008 at 11:23 PM, Alexander Neundorf wrote:
> On Wednesday 05 November 2008, Gábor Török wrote:
> > I wiil register on eCosForge and I can help developing it.
> That would be nice.
> > What are the differences between main eCos CVS and the eCosForge version of
> > MW?
> Compared to eCos cvs the version on eCosForge is:
> -much newer, i.e. I synced it with Microwindows cvs back then
> -modular, i.e.
> -it can use an external libjpeg (also on ecosforge)
> -an external libpng (also on ecosforge)
> -you can build just the graphic primitves library
> -you can add input support for that
> -you can choose which fonts you want to have
> -you can build the mwin API, with different options for threading (which
> doesn't require networking)
> -it supports the RTEMS key handling interface
> What's not done:
> -socket stuff ripped out
> -updated to work with the new framebuffer driver of eCos
> -synced with now current Microwindows

I'm just starting work on the last two (eCos FB support and sync with
current CVS). Later I may have a look at the socket stuff.


Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

More information about the Ecos-discuss mailing list