This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
RE: Re: MicroWindows, network stack, framebuffer API
- From: "Lecordier, Guy" <Guy dot Lecordier at paclp dot fr>
- To: Gábor Török <tgabor84 at gmail dot com>, <ecos-discuss at ecos dot sourceware dot org>
- Date: Wed, 5 Nov 2008 14:30:48 +0100
- Subject: RE: [ECOS] Re: MicroWindows, network stack, framebuffer API
>> I posted some proposals in the nano-X mailing list to have the nano-X
>> cvs working in the linked mode. I did also some proposals to update the
>> client server code. I tested only the landmine demo on a NIOSII platform
>> and ecos 2.0 .
>Does it mean, that you have the directly linked in server working,
>that I mentioned to Alex in my answer?
The modification was to work directly with the server functions like it is documented in the config file and I did some test with the landmine demo code.
####################################################################
#
# NanoX: Put Y to the following line to link the nano-X application
# with the server. This is required for ELKS, if no network is present,
# or for speed or debugging. This affects the nano-X server only.
#
####################################################################
LINK_APP_INTO_SERVER = Y
>> It is not yet finalized. The compilation of the nano-X library was done
>> in standalone using the standard config file and makefile of nano-X.
>If the answer is yes to the previous question, can it be merged into
>the version on eCosForge?
I used the latest code from nano-X and the modifications are well localized.
Guy
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss