From: Fredrik Hederstierna <fredrik@wespot.com>
To: Grant Edwards <grante@visi.com>
Cc: "Lewin A.R.W. Edwards" <larwe@larwe.com>,
james chen <james_ch1@sina.com>,
ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] eCos API
Date: Thu, 19 Apr 2001 23:50:00 -0000 [thread overview]
Message-ID: <3ADFDBE3.CA841E20@wespot.com> (raw)
In-Reply-To: <20010419094458.A27256@visi.com>
We have developed a dynamical loader for applications in the ELF file format. It
works very well I think!
Best Regards,
Fredrik Hederstierna
WeSpot AB
SWEDEN
Grant Edwards wrote:
> > > Hi, many RTOS e.g. WinCE, Paml, etc. allow user to use it's API to
> > >develop applications and download it to it's system. Now I want to support
> >
> > eCos does not support user-installable applications. It is a
> > monolithic, statically-linked OS+application.
>
> Exactly. If you need to support the dynamic loading of
> applications, then eCos is probably not a good choice for OS.
> You might want to look at uCLinux -- I presume it does dynamic
> loading of applications.
>
> Developing a dynamic linker/loader for eCos would take a fair
> amount of work -- especially if you wanted applications to
> share run-time libraries. If all you wanted was a
> position-independant way to make system calls, that wouldn't be
> quite as bad.
>
> --
> Grant Edwards
> grante@visi.com
next prev parent reply other threads:[~2001-04-19 23:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-18 21:00 james chen
2001-04-18 21:37 ` Lewin A.R.W. Edwards
2001-04-19 7:43 ` Grant Edwards
2001-04-19 23:50 ` Fredrik Hederstierna [this message]
2001-04-19 23:57 ` Chris Gray
2001-04-20 0:06 ` Jonathan Larmour
2001-04-20 6:22 ` Lewin A.R.W. Edwards
2001-04-19 1:01 Nielsen Linus
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=3ADFDBE3.CA841E20@wespot.com \
--to=fredrik@wespot.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=grante@visi.com \
--cc=james_ch1@sina.com \
--cc=larwe@larwe.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).