Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
MIME-Version:	1.0
Subject:	RE: Unresolved parent class constructors in DLLs
X-MimeOLE:	Produced By Microsoft Exchange V6.0.5762.3
content-class:	urn:content-classes:message
Date:	Thu, 23 May 2002 07:20:04 +1000
Message-ID:	<FC169E059D1A0442A04C40F86D9BA7600C613E@itdomain003.itdomain.net.au>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
From:	"Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To:	"Jason Spence" <jspence AT lightconsulting DOT com>, <cygwin AT cygwin DOT com>
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id g4MLLQp24988

> -----Original Message-----
> From: Jason Spence [mailto:jspence AT lightconsulting DOT com] 
> Sent: Thursday, May 23, 2002 5:20 AM

> Can you even do stuff like this with PE DLLs?

Yes. But you've got to resolve all symbols at link time. Dynamically
registering classes aren't the proble here - the problem is your parent
class needs to be available to the linker for the child (as you've
stated in your title).

My 2c: put the parent in a .dll of it's own, and link against that from
the children and the program.

Rob

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -