> However, the source structure of FreeType2 is related with the
> modularization of each features and binary compatibilities, so the
> official support of the concatenated C source can be slightly
> difficult (sorry!).
It's fine with me to improve that.
> BTW, during the overhaul of PIC mode building, I found there are
> several macros that would not work if all sources are concatenated.
> Werner, should we care the inter-module namespace separation of cpp
> macros?
This is OK with me.
> At present, we care only the intra-module namespace separation. The
> easiest way would be the insertion of "#undef" to unsafe macros...
Can you give an example? Perhaps we can rename macros if it is not
too cumbersome.
Werner
_______________________________________________
Freetype-devel mailing list
Freetype-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/freetype-devel
