Re: Logging Library-GSOC

2020-06-24 Thread Priyesh kumar
Hi Werner, *> Well, you say 'most'. Is this, say, 70% or 90% suitability in your> opinion? If it's the former, how much additional code must be added> to fit the needs? There might be a point that you have to add so much> code that it might be easier to avoid the library altogether.* Accord

Re: [Freetype-devel] Re: GSOC - Distance Fields

2020-06-24 Thread Anuj Verma
Hello Werner, > It's not clear to me what you want to achieve. Please elaborate. For example If the user wants to enable multi-channel rendering which gets rid of smooth corners, or to enable SIMD optimization. The simplest example would be to enable overlapping contour support. Anuj

Re: Logging Library-GSOC

2020-06-24 Thread Werner LEMBERG
> > The recent discussion with Behdad reminded me to ask you whether you > > have also investigated the case where you modify the existing > > debugging and tracing code of FreeType without using an external > > library. For example, such new code might be based on the code from > > 'dlg' but st

Re: [Freetype-devel] Re: GSOC - Distance Fields

2020-06-24 Thread Werner LEMBERG
> I added functionality to set renderer properties (namely the > `spread' parameter). So, there is API for this `FT_Property_Set' > and `FT_Property_Get'. Is there any similar API for setting the > renderer specific modes which is defined by the > `FT_Renderer_SetModeFunc' function, or do I get

Re: GSOC Build tests

2020-06-24 Thread Werner LEMBERG
Hello Greg, > Over the past couple weeks I've converted the build tests to use > autotools for the three desktop OSes. I've managed to leave the > cmake tests intact too. I also now have demos building against the > freetype version pulled in the CI. Thanks! > I wasted quite a bit of time tr

Re: [PATCH] [freetype2-demos] * Makefile (COMPILE): Use same order of flags as freetype2

2020-06-24 Thread Alexei Podtelezhnikov
On Wed, Jun 24, 2020 at 12:22 PM Jan Alexander Steffens (heftig) wrote: > > This ensures the includedir for the built FreeType comes first, before > any flags for a system FreeType which was pulled in through pkg-config > for harfbuzz. Committed. Thanks!

[PATCH] [freetype2-demos] * Makefile (COMPILE): Use same order of flags as freetype2

2020-06-24 Thread Jan Alexander Steffens (heftig)
This ensures the includedir for the built FreeType comes first, before any flags for a system FreeType which was pulled in through pkg-config for harfbuzz. --- Makefile | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/Makefile b/Makefile index 8e4ca56..e6ad0af 100644 ---

Re: [patch] Simplify ftconfig.h

2020-06-24 Thread Alexei Podtelezhnikov
Hello David, > create mode 100644 include/freetype/config/compiler_macros.h > create mode 100644 include/freetype/config/integer_types.h > create mode 100644 include/freetype/config/mac_support.h > create mode 100644 include/freetype/internal/compiler_macros.h The same filename albeit in diff

Re: [patch] Simplify ftconfig.h

2020-06-24 Thread David Turner
And the previous patch didn't handle CMakeLists.txt properly, so here's a third version that fixes the issue. Le mar. 23 juin 2020 à 22:25, David Turner a écrit : > Good catch, here's the updated patch that also modifies > builds/vms/ftconfig.h > > We might remove support for __BORLANDC__ et al

Re: Logging Library-GSOC

2020-06-24 Thread Priyesh kumar
Hi Werner, > *Thanks! The recent discussion with Behdad reminded me to ask you> whether you have also investigated the case where you modify the> existing debugging and tracing code of FreeType without using an> external library. For example, such new code might be based on the> code from 'd