Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Delivered-To: fixup-cygwin AT cygwin DOT com@fixme
From: "Paul Garceau" <pgarceau AT qwest DOT net>
Organization: New Dawn Productions
To: cygwin AT cygwin DOT com
Date: Mon, 26 Feb 2001 14:52:02 -0800
Subject: Re: Windows Resource Files and DLLs
Reply-to: Paul Garceau <pgarceau AT qwest DOT net>
Message-ID: <3A9A6D92.14751.47EF8A@localhost>
In-reply-to: <20010225213759.A902@redhat.com>
References: <000001c09f9b$0ffa8f00$a300a8c0 AT nhv>; from nhv AT cape DOT com on Sun, Feb 25, 2001 at 09:23:08PM -0500
X-mailer: Pegasus Mail for Win32 (v3.12c)



On 25 Feb 2001, at 21:37, the Illustrious Christopher Faylor wrote:

> On Sun, Feb 25, 2001 at 09:23:08PM -0500, Norman Vine wrote:
> >I have managed with a fair bit of 'coercion' to build a working
> >wxPython 2.2.5 DLL for Cygwin.
> >
> >One of the stumbling blocks I still have in coming up with a suitable
> >install script is that I apparently need to link the wxWindows resource
> >file with the Python.exe stub in order for it to be 'seen' by Python
> >scripts.
> >
> >IMO this is not an ideal solution.
> >
> >I would like to keep the resource file in the DLL
> >
> >Is there an equivalent for a DLLEXPORT for windows resources in a
> >compiled .rc file ??

	Not really.  But there is a possible workaround.
> 
> This seems like a reasonable thing to want to do...  which probably
> means that it isn't possible in Windows.

	The workaround is to compile the .rc file using windres, output as .o 
file.

	windres my.rc -omy.o

	And then to use dllwrap to add my.o to your .dll file.

	(this is the first time I've tested this -- the output .dll, according 
to "Quickview" seems to have valid headers.  Next question is can the 
.dll file be loaded via win32 api?...this I am not sure of.  Logic 
indicates that if the .dll is a "valid cygwin .dll" then it should be 
an easy matter to simply load the .dll like you normally would, thus 
adding the resources you require).

	Anyone else have a better sense of this?

	Thanks,

		Paul G.


Nothing real can be threatened.
    Nothing unreal exists.

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple