Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sourceware.cygnus.com
Message-Id: <199911121712.LAA27146@mercury.xraylith.wisc.edu>
To: "vincent penne" <vincent.penne@freesbee.fr>
cc: cygwin@sourceware.cygnus.com
Subject: Re: Building C++ library DLL 
In-Reply-To: Your message of "Fri, 12 Nov 1999 05:56:29 +0100."
             <000701bf2cca$48c5c600$7b0681d4@ziggy> 
Date: Fri, 12 Nov 1999 11:12:17 -0600
From: Mumit Khan <khan@thor.xraylith.wisc.edu>

"vincent penne" <vincent.penne@freesbee.fr> writes:
> ------=_NextPart_000_0004_01BF2CD2.A9E3DBE0
> Content-Type: text/plain;
> 	charset="iso-8859-1"
> Content-Transfer-Encoding: quoted-printable
> 
> Hi all,
> maybe it's not the correct list where to ask for since my problem is GCC =
> related, but I try anyway.
> 
> With Microst Visual C++ it is possible to write something like
> 
> class __declspec(dllexport) foo {
>     static int foo_var;
> 
>     void foo_function();
> }
> 
> This will export the function and the static variable without need to =
> put the __declspec(dllexport) on every line of the class definition.
> 
> When using the library, one can write
> 
> class __declspec(dllimport) foo {
>  ...
> 
> My question : Is it supposed to work with GCC too ? If not, are there =
> any plans to implement such a nice feature ? This make porting of C++ =
> library to windows a lot more easy, since there is a lot less __declspec =
> directive to put in the header files ...

It should work. Why not just try it out?

Regards,
Mumit


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com