How about "libhabackersimagehelp.a" etc? -- Gary R. Van Sickle Brewer. Patriot.
> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Ralf Habacker > Sent: Thursday, January 02, 2003 3:50 AM > To: Robert Collins > Cc: Jason Tishler; [EMAIL PROTECTED] > 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 >
