2009/7/18 Charles Wilson <cygwin@xxxxxxxxxxxxxxxxxxx>:
> Dave Korn wrote:
>> Charles Wilson wrote:
>>> For mingw, we (will) have
>>> libstdc++ (shared or static)
>>> libgcc (shared or static)
>>> MSVC (runtime) (shared or static)
>>> Now, because MinGW gcc always links against msvcrt.dll (unless you play
>>> games with the spec file; let's not worry about that right now), THEN
>> Then in MinGW they should use something other than _DLL. It is used in one
>> place only, the cygwin target-specific version of os_defines.h where it
>> controls how to set _GLIBCXX_IMPORT. MinGW's os_defines.h can simply use
>> whatever other macro they prefer. There is no problem.
> Ack. As I said further on in my most recent message, I don't think _DLL
> matters on mingw either, EXCEPT insofar as certain users may currently
> be in the (bad) habit of leaving it defined. IF mingw wants to
> accommodate those users, then mingw can do as you suggest, and use a
> different controlling symbol in their os_defines.h.
Well, my concerns here are more in a general way of users using gcc
for compiling source code written for windows. Believe me there are
many projects (like mozilla, reactos, boehm-gc, ...) which want to
compile their sources with VS and gcc. For those users the mis-use (in
their opinion) of the _DLL macro is very annoying. This was the reason
why I have the strong opinion here, that gcc shouldn't use this macro
for win32 targets.
But I would like to see Danny's opinion about this, before final
decision about this is made.
| (\_/) This is Bunny. Copy and paste
| (='.'=) Bunny into your signature to help
| (")_(") him gain world domination