This is the mail archive of the
ecos-patches@sources.redhat.com
mailing list for the eCos project.
Re: Object File Loader
- From: Anthony Tonizzo <atonizzo at gmail dot com>
- To: ecos-patches at ecos dot sourceware dot org
- Cc: Nick Garnett <nickg at ecoscentric dot com>, andrew at lunn dot ch
- Date: Wed, 29 Jun 2005 08:52:31 -0700
- Subject: Re: Object File Loader
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=FFckBNV70sIdfPv1vyhjgTktK92+damf8YAt4lVtQnvRAM0Pp2u4Unv89Hhhr5AvCSPxtO1NpTnzEKKCN8zG0FRN7yRoq14917oRSHCHJGrVzVQnOdXPulz4UNRcGnOviPeEb5zXHLXxPEzorkPjhJ1j/uoghjz5d7gq22CVOkY=
- References: <b437ec69050629071950b47ed6@mail.gmail.com> <m3wtodusbv.fsf@xl5.calivar.com>
- Reply-to: Anthony Tonizzo <atonizzo at gmail dot com>
Nick:
> There are two sets of labels here. The loader API routines should have
> cyg_ldr prefixes, and they all currently do. However, the
> library_open() and library_close() functions are a different
> case. These are visible as labels only in the loaded object, and are
> really part of the application. So I'm not sure that they should have
> cyg_ldr prefixes.
Actually, I have debated myself on whether a library_open() and a
library_close()
functions are even necessary, since the user can call his own init function just
as easily. I guess it is a matter of convenience to have them there. And if we
do, I agree we should strip the cyg_ldr from these.
> Perhaps a middle way is to define a set of super-macros that include
> blocks of functionality and are defined only when the equivalent
> packages are present.
I like the idea. I will try it out today and send you a patch in case
you want to
include it.
Tony
P.S.
Apparently the solution to my posting woes was to switch to gmail and
ditch lycos...