This is the mail archive of the
mailing list for the Cygwin project.
Re: gcc -shared under 2.95.3-5, unable to convert .o to .dll via -shared flag
- From: "Robert Collins" <robert dot collins at itdomain dot com dot au>
- To: "Gregory Lampshire" <gregory_lampshire at hotmail dot com>
- Cc: <cygwin at cygwin dot com>
- Date: Mon, 31 Dec 2001 08:52:12 +1100
- Subject: Re: gcc -shared under 2.95.3-5, unable to convert .o to .dll via -shared flag
- References: <OE46C2Dhd9FdIbHvh2d000072d9@hotmail.com> <06f301c19136$d89772b0$0200a8c0@lifelesswks> <OE33Su9uSsDZfGGdDIi0000743d@hotmail.com>
Please keep the conversation on the list.
----- Original Message -----
From: "Gregory Lampshire" <firstname.lastname@example.org>
To: "Robert Collins" <email@example.com>
Sent: Monday, December 31, 2001 2:33 AM
Subject: Re: gcc -shared under 2.95.3-5, unable to convert .o to .dll
via -shared flag
> Many thanks for the clarification. I did run a gcc with all the
> libs that are needed to resolve the symbols. This resulted in huge
> (.dll) files for many .so files that are individually compiled then
> The static libs are bound together to make an ecl executable which is
> image file that loads the .so files once they are cerated. Is there
> to get the .so files without the link pulling in *everything* to
> symbols? I am curious if I went to dll libraries for everything
> issues be solved.
I'll repeat myself. WIN32 *DOES NOT PERMIT UNRESOLVED SYMBOLS*. There is
NO WAY to get .dll's without pulling in everything.
And yes, more .dll's = mor shared code = smaller objects.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html