From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3089 invoked by alias); 20 Sep 2003 12:25:10 -0000 Mailing-List: contact ecos-maintainers-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: ecos-maintainers-owner@sources.redhat.com Received: (qmail 3081 invoked from network); 20 Sep 2003 12:25:10 -0000 Subject: Re: a question about the microwindows API of microwindows From: Gary Thomas To: b8944004 Cc: eCos Maintainers In-Reply-To: <20030920054928.M57930@stmail.cgu.edu.tw> References: <20030920054928.M57930@stmail.cgu.edu.tw> Content-Type: text/plain Organization: MLB Associates Message-Id: <1064060708.8284.385.camel@hermes> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-4) Date: Sat, 20 Sep 2003 12:25:00 -0000 Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=-4.4 required=5.0 tests=AWL,EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT, REFERENCES,REPLY_WITH_QUOTES,USER_AGENT_XIMIAN autolearn=ham version=2.55 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) X-SW-Source: 2003-09/txt/msg00022.txt.bz2 On Fri, 2003-09-19 at 23:50, b8944004 wrote: > Hi: > I write a application with the microwindows API(like Win32 API) for > the Microwindows. When I compile it ,the gcc show a lot of errers such as > "undefined reference to xxxx" (xxxx is some function of microwindows API). > I find the installation directory has no library of the microwindows API and > the CDL file of the microwindows doesn't include anything about microwindows > API. > > > the step I make install directory: > > > ecosconfig new ipaq net > ecosconfig add mw > ecosconfig tree > make > > > some information as fallow: > > > /work2/services/gfx/mw/v2_0/src: > demos drivers ecos engine fonts nanox > ^^^^^^ > no mwin??? > How could I solve the problem ? > Does the microwindows on the eCos not support the microwindows API? It looks like we've never tried to build the mwin part of MicroWindows. AFAIK, only the nano-X layer and associated applications, like the nanowm (window manager), have been ported. Of course you are free to improve this situation. If you choose to port the code, it would be nice if you could share the results as well. Thanks & good luck to you. n.b. If you have questions or problems, I'm sure that someone on this list will try to help. However, good answers come from good questions, so be sure and provide sufficient detail. -- Gary Thomas MLB Associates