>> But Visual C is a front-end to a command line compiler, isn't it?
>
> it is.
Thanks for confirmation.
>> In that it makes sense to have this stuff in FreeType's header
>> file also; for example, people want to call nmake manually...
>
> also it is necessary for applications or libraries using freetype
> that FT_EXPORT be defined to dllimport (which is currently the
> case).
>
> I would like also to mention in the case of UNIX using gcc, that the
> visibility of symbols can be changes by a compiler flags [...]
Yep, FreeType does that.
> [...] so if, on UNIX, one passes -fvisibility=hidden to gcc,
> FT_EXPORT should be defined as __attribute__
> ((visibility("default")))
FreeType's current solution works differently, as you certainly know.
Inspite of needing a separate program (src/tools/apinames.c) it works
well and is quite generic.
Werner
_______________________________________________
Freetype-devel mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/freetype-devel
