From: "wangwei" <wangw@start.com.cn>
To: <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] Microwindows on eCos
Date: Fri, 02 Mar 2001 01:53:00 -0000 [thread overview]
Message-ID: <006c01c0a2fd$98aa5820$592da8c0@start.com.cn> (raw)
In-Reply-To: <F238YORZfbsyI6tuA5300002951@hotmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1590 bytes --]
Now I have turn off the compile option and got a success in runing win32 api
in ecos.
Thank you very much .
I have another problem in microwindows:
I found the tcp/ip stack in ecos can't support nanox .The union
sockaddr_un in file "client.c" can't be found in ecos . So I can't get the
nano-x library .
Are there anybody had resolve this problem ?
Help me , thanks
----- Original Message -----
From: "Rosimildo daSilva" <rosimildo@hotmail.com>
To: <wangw@start.com.cn>; <sehyeong@hanmail.net>;
<ecos-discuss@sources.redhat.com>
Sent: Friday, March 02, 2001 6:34 AM
Subject: Re: [ECOS] Microwindows on eCos
> e this
>
>
> >From: "wangwei" To: ö¼¼Ãü , Subject: Re: [ECOS] Microwindows on eCos
Date:
> >Thu, 1 Mar 2001 09:43:18 +0800
> >
> >Hi, Now I'm also port microwindows to ecos. but I met a problem: I can't
> >success to compile the file mwobjects.cc in directory ./mwin/mwobject/,
> >because the file is include a linux c++ file which can't be found in
ecos.
> >You said you can run it in synthetic linux ,can you tell me how can you
> >resolve this problem.
>
> You cannot. mwobject is a C++ wrapper for Microwindows ( Win32 API ). It
> uses STL, and STL is supported by Ecos at this time.
>
> The good news is that you *do not need it*, unless you are a
> C++ guru, and are sick and tired of the *boring* C based
> Win32 API. MwObject only used by the Win32 API, and the NanoX
> API does not use it.
>
> Rosimildo.
>
>
> _________________________________________________________________
> Get your FREE download of MSN Explorer at http://explorer.msn.com
>
next prev parent reply other threads:[~2001-03-02 1:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-01 14:34 Rosimildo daSilva
2001-03-02 1:53 ` wangwei [this message]
2001-03-02 2:42 ` Rafael RodrÃguez Velilla
2001-03-02 2:57 ` Martin van Veen
2001-03-02 3:48 ` Christian Plessl
-- strict thread matches above, loose matches on Subject: below --
2008-02-27 17:05 Antoine.Amirault
2003-07-17 15:59 [ECOS] MicroWindows " Chris Garry
2003-07-17 16:17 ` Bob Koninckx
2003-07-17 16:43 ` Chris Garry
2003-07-18 4:40 ` Jonathan Larmour
2003-07-18 15:51 ` Chris Garry
2003-04-06 8:05 [ECOS] Microwindows " fairy
2003-04-07 22:17 ` Jonathan Larmour
2001-04-12 14:36 宋宜叡
2001-04-13 6:55 ` Gary Thomas
2001-03-02 6:05 Rosimildo daSilva
2001-01-16 2:46 ö¼¼Ãü
2001-02-28 17:47 ` wangwei
2001-03-01 4:01 ` Robin Farine
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='006c01c0a2fd$98aa5820$592da8c0@start.com.cn' \
--to=wangw@start.com.cn \
--cc=ecos-discuss@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).