freetype-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [ft-devel] FreeType DLL support (Re: Freetype-devel Digest, Vol 156,


From: Martin Gieseking
Subject: Re: [ft-devel] FreeType DLL support (Re: Freetype-devel Digest, Vol 156, Issue 12)
Date: Fri, 12 Jan 2018 19:30:20 +0100
User-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2

Am 12.01.2018 um 18:30 schrieb Hin-Tak Leung:
> 
> 
>  Message: 3
>  Date: Fri, 12 Jan 2018 09:32:59 +0100
>  From: Martin Gieseking <address@hidden>
>  To: freetype-devel <address@hidden>
>  Subject: Re: [ft-devel] FreeType DLL
>  support
>   
>> I would also suggest to replace
>>    #ifdef _MSC_VER
>>  with
>>    #ifdef _WIN32
>> in order to support other Windows
>> compilers too.
>  
>> Instead of _DLL it might be better to
>> use DLL_EXPORT because it's 
>> automatically defined when configuring
>> the build of a shared library on 
>> Windows with MinGW or Cygwin.
>  
> No need. The dllexport mechanism is entirely Microsoft compiler-specific - 
> gcc on mingw/Cygwin uses a different symbol scanning and look-up mechanism 
> and does not need those DLL_EXPORT/DLL_IMPORT hacks.


Not really. dllexport/dllimport is platform- and not compiler-specific.
GCC and Clang on MinGW also support them to declare the symbols that are
supposed to be exported by the DLL and adapt the symbol names
accordingly. In order to create/access DLLs through this mechanism
across compilers, the declarations should be added independently from
the compiler.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]