This is the mail archive of the
ecos-patches@sourceware.org
mailing list for the eCos project.
Re: [PATCH] add ftok() and getenv() functions to the synthetic target
- From: Alexander Neundorf <neundorf at kde dot org>
- To: Andrew Lunn <andrew at lunn dot ch>,ecos-patches at ecos dot sourceware dot org
- Date: Fri, 4 Nov 2005 17:38:32 +0100
- Subject: Re: [PATCH] add ftok() and getenv() functions to the synthetic target
- References: <200510191920.25132.neundorf@kde.org> <200510271918.25271.neundorf@kde.org> <20051027185349.GG4266@lunn.ch>
- Reply-to: neundorf at kde dot org
On Thursday 27 October 2005 20:53, you wrote:
> On Thu, Oct 27, 2005 at 07:18:24PM +0200, Alexander Neundorf wrote:
> > On Thursday 27 October 2005 11:55, Andrew Lunn wrote:
> >
> > ...
> >
> > > So i see no reason why you should not include the packages you need
> > > for synth into the build for your target application as well. It will
> > > not affect the size of your target application.
> >
> > Yes, but there will be other headers available under the synthetic
> > target than under the real target, so I'll have a different
> > environment and won't be able to check whether my software will work
> > without CYGPKG_LIBC_STDLIB (which my application might not need). I
> > think the functions for accessing resources from the host under the
> > synthetic target should be independent from the actual configuration
> > for the target.
>
> You are missing the point. It does not matter if your application
> needs CYGPKG_LIBC_STDLIB or not. Having the package makes no
> difference to the size of the target image. So you might as well have
> it in the target build so that the target and the synth system are the
> same.
Ok.
So how about cyg_hal_sys_ftok() ?
I can't create a "reengineered" version of the patch anymore.
Bye
Alex
--
Work: alexander.neundorf@jenoptik.com - http://www.jenoptik-los.de
Home: neundorf@kde.org - http://www.kde.org
alex@neundorf.net - http://www.neundorf.net