public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Robin Farine <acnrf@dial.eunet.ch>
To: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Microwindows on eCos
Date: Thu, 01 Mar 2001 04:01:00 -0000	[thread overview]
Message-ID: <86hf1dd7mc.fsf@halftrack.hq.acn-group.ch> (raw)
In-Reply-To: <002d01c0a1f1$00ee9580$592da8c0@start.com.cn>

Hi,

"wangwei" <wangw@start.com.cn> writes:

> 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 <algorithm> 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.
>     think you very much .

I think that this "algorithm" header file belongs to the STL, no link at all
with the Linux kernel but part of the standard C++ library. You could try
STLPort, a portable version of the STL but I do not know whether someone already
used it with eCos.

Robin

  reply	other threads:[~2001-03-01  4:01 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-16  2:46 Á¶¼¼Çü
2001-02-28 17:47 ` wangwei
2001-03-01  4:01   ` Robin Farine [this message]
2001-03-01 14:34 Rosimildo daSilva
2001-03-02  1:53 ` wangwei
2001-03-02  2:42   ` Rafael Rodríguez Velilla
2001-03-02  2:57     ` Martin van Veen
2001-03-02  3:48     ` Christian Plessl
2001-03-02  6:05 Rosimildo daSilva
2001-04-12 14:36 宋宜叡
2001-04-13  6:55 ` Gary Thomas
2003-04-06  8:05 fairy
2003-04-07 22:17 ` Jonathan Larmour
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
2008-02-27 17:05 [ECOS] Microwindows " Antoine.Amirault

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=86hf1dd7mc.fsf@halftrack.hq.acn-group.ch \
    --to=acnrf@dial.eunet.ch \
    --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).