This is the mail archive of the
cygwin-apps@cygwin.com
mailing list for the Cygwin project.
RE: Integrating Ralf's rebase into setup.exe
- From: "Gary R. Van Sickle" <g dot r dot vansickle at worldnet dot att dot net>
- To: <cygwin-apps at cygwin dot com>
- Date: Fri, 3 Jan 2003 00:20:51 -0600
- Subject: RE: Integrating Ralf's rebase into setup.exe
How about "libhabackersimagehelp.a" etc?
--
Gary R. Van Sickle
Brewer. Patriot.
> -----Original Message-----
> From: cygwin-apps-owner@cygwin.com
> [mailto:cygwin-apps-owner@cygwin.com]On Behalf Of Ralf Habacker
> Sent: Thursday, January 02, 2003 3:50 AM
> To: Robert Collins
> Cc: Jason Tishler; cygwin-apps@cygwin.com
> Subject: RE: Integrating Ralf's rebase into setup.exe
>
>
> > > If I remember right, this lib will be used for a cygwin based
> > rebase and later
> > > in the cygwin's setup application which is mingw based. So this
> lib must be
> > > buildable for cygwin and mingw, isn't it ?
> >
> > Yes. And the library should use the appropriate naming convention for
> > the target platform.
> > I *don't* think it should be named libimagehlp.a,
> > because it's *not* a 100% replacement for libimagehlp.
>
> You have already stated
>
> - libcygimagehlp (for cygwin applications like rebase)
>
> Do you mean
>
> - libmingwimagehlp
>
> for setup.exe ?
>
> What about the header ? It could be the same in both variants.
> Symbolic linking
> ?
>
> cygimagehlp.h
> mingwimagehlp.h -> cygimagehlp.h
>
> I think that's bad. The bfd library is named libbfd.xx on every platform, so
> this library should be named in another way.
>
> What about imagehelper.a and imagehelper.h and using autoconf stuff ?
>
> Ralf
>