Happy new year to everyone!
> Here I attach revised patch.
Looks great.
> Now I think, the next step to improve multilib support would be
> modification of freetype2/configure, instead of
> freetype2/builds/unix/configure. It's like gcc config-ml.in. By
> executing configure in separated directories, we can collect
> ftconfig.h files for each configuration easily, and exactly.
This sounds like a nice idea.
> But, freetype2/configure has not been autoconfized, so I'm afraid I
> should not use macros in ft-uniconf.m4...?
Laziness. The top-level configure script is so small
(currently) that a manually written version is sufficient.
> Werner, could you tell me about the restriction to modify that?
No restrictions. Do whatever you think is appropriate.
Werner
_______________________________________________
Freetype-devel mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/freetype-devel
