> Thanks, I will try to revert closer to the original logic where
> attributes were only used ifdef FT2_BUILD_LIBRARY. I thought it was
> sensible.
OK.
> On a related note, is there interest in HP C/HP aC++ support of
> hidden symbols? I have nuts and bolts for that. Or is there anything
> else n
I've finished the core of the regression tester. You can now run it and
generate a html report but you will need a few tools installed: imagick,
xwd, npm, pretty-diff and xvfb. This should all be listed in
ft-regression.sh's comments.If you want to run it locally make sure you
have a ~/test-fonts w
Hi Dominik and others
On Fri, Jul 10, 2020 at 7:17 AM Dominik Röttsches wrote:
> I've made some progress with the COLR v1 extension implementation in
> FreeType and would be happy to hear initial feedback on the general
> approach and API style.
Let me repeat myself by saying that I am not parti
Hi Werner,
> Please improve his patch (now in git) if necessary!
Thanks, I will try to revert closer to the original logic where
attributes were only used ifdef FT2_BUILD_LIBRARY. I thought it was
sensible.
On a related note, is there interest in HP C/HP aC++ support of hidden
symbols? I have nu
>> The warning is because of the ` FT_INTERNAL_FUNCTION_ATTRIBUTE'
>> macro which is defined to . So defining it to nothing fixes all the
>> warnings.
>
> That's the thing on win32: you are not supposed to even get to
> __attribute__((visibility("hidden")). You must use
> __declspec(dllexport),
> That doesn't seem to work on windows.
>
> The warning is because of the ` FT_INTERNAL_FUNCTION_ATTRIBUTE'
> macro which is defined to __attribute__((visibility("hidden")). So
> defining it to nothing fixes all the warnings.
Thanks for patch, now applied to git.
Werner
> The warning is because of the ` FT_INTERNAL_FUNCTION_ATTRIBUTE'
> macro which is defined to . So defining
> it to nothing fixes all the warnings.
That's the thing on win32: you are not supposed to even get to
__attribute__((visibility("hidden")).
You must use __declspec(dllexport), __declspec(dl
> Hm. Can't really say, but I have recently encountered a bug in InDesign which
> subsets a VF for embedding into a document and turns it into a static font...
> without removing overlaps or setting the overlap flags, leading to even-odd
> rendering errors in macOS Preview. So I plan on modifyin
i have forgotten my meson command :
meson .. \
--prefix=/opt/freetype \
--libdir=lib \
--buildtype=release \
--cross-file ../cross_toolchain.txt \
--default-library shared \
-Dzlib=system \
-Dbzip2=enabled\
-Dpng=enabled \
-Dharfbuzz=enabled
