This is the mail archive of the cygwin@sourceware.cygnus.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Rép.: Re: Building C++ library DLL



>
>Date: Fri, 12 Nov 1999 11:12:17 -0600
>Cc: cygwin@sourceware.cygnus.com
>
>"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?
>

Actually I tried, but it did not seem to work, and more seriously, when *using* the library (that is when there are some __declspec(dllimport)), the compiler often report internal errors ...

I was trying on a complete library, but to track down the problem I'm now going to try on simple examples ...

Thanks for the help !




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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]