This is the mail archive of the
mailing list for the Cygwin project.
Re: DLL naming conventions
On Sun, Sep 03, 2000 at 12:30:18PM -0400, Chris Faylor wrote:
> On Sun, Sep 03, 2000 at 01:27:12PM +0100, Gary V. Vaughan wrote:
> >Why not just statically link all of our applications? Then we
> >wouldn't have any problems with wrong dlls being loaded at all!
> Are you ranting at me? Don't bother.
No offence was intended. I was mostly ranting on the capacity of
Microsoft to remove all the advantages of a system (shared libraries)
but still retain all the loops you have to jump through to use them.
> My major concern was naming every cygwin DLL "cygsomething.dll". I
> really don't like that idea, especially since it will mean work for
> people at Red Hat to accomodate.
Chuck has talked sense into me here... I no longer think that this
buys us anything.
> I did see the AppPath registry key being mentioned. I'm not sure how
> libtool could make use of that since that is something that is set on
> installation of a package. libtool may be out of the picture at that
> point unless you're doing 'make install'.
Bummer =(O| Does that mean binary packages would need to run a
post-install script to set the AppPath correctly then? If it was a
boiler plate script, perhaps libtool could generate it if it notices
that the `make install' is moving things to a staging area (for
packaging) as opposed to moving things directly to the live
> This could be a solution for cygwin but I don't know if it addresses the
> problem of other packages or not.
Paul has shown willing to provide suitable patches for his system, and
I use only cygwin myself. If I can improve the build system on just
cygwin I will be more than happy.
___ _ ___ __ _ mailto: firstname.lastname@example.org
/ __|__ _ _ ___ _| | / / | / /_ _ _ _ __ _| |_ __ _ ___ email@example.com
| (_ / _` | '_|// / |/ /| |/ / _` | || / _` | ' \/ _` | _ \
\___\__,_|_|\_, /|___(_)___/\__,_|\_,_\__, |_||_\__,_|//_/
home page: /___/ /___/ gpg public key:
Want to unsubscribe from this list?
Send a message to firstname.lastname@example.org