delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin-developers/1999/01/19/22:28:32

From: khan AT xraylith DOT wisc DOT edu (Mumit Khan)
Subject: Re: B21 != B20
19 Jan 1999 22:28:32 -0800 :
Message-ID: <199901200607.AAA23606.cygnus.cygwin32.developers@modi.xraylith.wisc.edu>
References: <19990119221046 DOT C30557 AT cygnus DOT com>
To: Christopher Faylor <cgf AT cygnus DOT com>
Cc: cygwin32-developers AT cygnus DOT com

Christopher Faylor <cgf AT cygnus DOT com> writes:
> 
> 
> I'd like to use dllimport and dllexport but for that to be feasible it
> means that we'll have to still conditionalize the code for older revs of
> the compiler -- at least for a few months.  Is there any way to detect
> if the gcc being used understands dllimport/dllexport?

#ifdef declspec
# ...
#endif

Of course, folks using installed compilers may run into trouble if they've
played with specs etc (eg., by defining declspec to be something else). I'll 
cook up an autoconf macro if the check above is not acceptable.

> >  - We can also now add an extra parameter to support Cygwin DLLs from
> >    non-Cygwin apps without having to maintain two different entry
> >    points. DJ's last patch had something like that, and so did one of
> >    my original changes that I had sent just after b20 (but not the
> >    final one that's in b20.1).
> 
> Is this ok, then?

I believe so. I haven't much time to test it, but looking at the code, it
looks correct. Someone should rebuild X libs, especially, xterm to see if
it works (xterm is a pathological case of exposing bugs ;-). Sergey has
probably already checked.

Regards,
Mumit

- Raw text -


  webmaster     delorie software   privacy  
  Copyright 2019   by DJ Delorie     Updated Jul 2019