nanogui: Nano-X as a component of eCos? (Was: Re: [nanogui] eCos support in CVS)
Subject:
Nano-X as a component of eCos? (Was: Re: [nanogui] eCos support in CVS)
From:
"???" ####@####.####
Date:
4 Apr 2002 20:54:59 -0000
Message-Id: <01f101c1dc19$d2cb3370$0d8c718c@biou>
Hi,
After some work about porting Nano-X to eCos (I've done some work about
porting Nano-X to Linux synthetic target last year),
I think it may be more elegant to incorporate the (CVS Version of )
Microwincows/Nano-X as a component of eCos,
in some sort of eCos package since the nature of Nano-X is, in my opinion,
closer to a library, not to an application.
Making Nano-X an eCos component may also eliminate some unnecessary
configuration in the Nano-X side
if we adapt the eCos CDL mechanism to the Nano-X configuration mechanism
(which is using makefile flags).
Any comment for this idea?
Regards,
I-Jui Sung
--
mailto: ####@####.####
Department of Computer Science & Information Enginerring,
National Chiao-Tung University,
Hsin-Chu, Taiwan
----- Original Message -----
From: "Julian Smart" ####@####.####
To: "Daniel Fandrich" ####@####.#### ####@####.####
Sent: Thursday, March 21, 2002 4:28 PM
Subject: Re: [nanogui] eCos support in CVS
> At 09:41 20/03/2002 -0800, Daniel Fandrich wrote:
> >Is someone actively maintaining the eCos support code? Is anyone
interested
> >in diffs if not?
>
> If you don't hear anything from the eCos team it's certainly not for
> lack of interest -- Nano-X is part of their long term graphics strategy.
> So I'm very sure work in this area will be appreciated (I have an interest
> in it too for future projects).
>
> Thanks!
>
> Julian
> ========================================================================
> Julian Smart ####@####.####
> 3 Water Street http://www.anthemion.co.uk
> Stamford, Lincs +44 (0)1780 765976
> U.K. PE9 2NJ
> ========================================================================
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####
>
