>> Using `size_t' makes sense, yes.
>
> I applied the change but decided to stay away from ftdbgmem.c.
Thanks.
> What is its purpose anyway in the World of valgrind and other tools?
Embedded systems, I guess.
Werner
___
Freetype-devel mailing
> > In addition I wonder if the entire ftdbgmem.c should be reworked
> > with size_t instead of FT_Long.
>
> Using `size_t' makes sense, yes.
I applied the change but decided to stay away from ftdbgmem.c. What is
its purpose anyway in the World of valgrind and other tools?
Hin-Tak,
If you use
>
> > Not yet, thanks. I'll first try to update the `rules.mk'.
>
> I've now updated the description of `X11_PATH' in this file to be as
> concise as possible.
>
Thanks :-)
Parth
___
Freetype-devel mailing list
Freetype-devel@nongnu.org
>
> > I installed ubutnu 18.04 in a virtualbox and tested this there too,
> > initially it returned error with `make X11_PATH=/usr/include' then I
> > found out `libx11-dev' was missing, so I installed it and then when
> > I did `make X11_PATH=/usr/include' it allocated display surface and
> >
