Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Message-ID: <000701bf2cca$48c5c600$7b0681d4@ziggy> From: "vincent penne" To: Subject: Building C++ library DLL Date: Fri, 12 Nov 1999 05:56:29 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0004_01BF2CD2.A9E3DBE0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 ------=_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 ... ------=_NextPart_000_0004_01BF2CD2.A9E3DBE0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi all,
maybe it's not the correct list = where to ask for=20 since my problem is GCC related, but I try anyway.
 
With Microst Visual C++ it is = possible to write=20 something like
 
class __declspec(dllexport) foo = {
    static int=20 foo_var;
 
    void=20 foo_function();
}
 
This will export the function and = the static=20 variable without need to put the __declspec(dllexport) on every line of = the=20 class definition.
 
When using the library, one can=20 write
 
class __declspec(dllimport) foo = {
 ...
 
My question : Is it supposed to work = with GCC=20 too ? If not, are there any plans to implement such a nice feature ? = This make=20 porting of C++ library to windows a lot more easy, since there is a lot = less=20 __declspec directive to put in the header files ...
 
------=_NextPart_000_0004_01BF2CD2.A9E3DBE0--