On Tue, 11 Jul 2023 at 19:26, suzuki toshiya wrote:

> Hi,
>
> In the conventional workflow, the source tree of the FreeType2 library
> has "./configure", but freetype-demos does not have. Just starting
> "make" with existing Makefile under "freetype-demos" carries the
> configured values from freetype directory.


If we are going to overhaul the build system, I’ve long wanted to have
FreeType demos build as a separate package that links against a
system-installed FreeType library (not the source directory).

I know the demos are intended to be used with the same version of FreeType,
so it could be a build dependency requirement to link against the same
version. This would avoid users linking against older versions.

The meson for the ftinspect
> wants to confirm additional libraries, like Qt5 (you can find the
> declaration of the dependency in src/ftinspect/meson.build).
>
> If somebody wants to try to make autotools to support the building
> of Qt5-based ftinspect, new configure should be added to freetype-demos,
> to check the availability of the extra libraries for ftinspect?



> Or, such check should be added to existing freetype/configure, even
> if libfreetype itself has no dependency with them?
>

That’s how we detect python3 and librsvg (although I wish there were a
lighter library available). That said, there’s certainly an argument for
alternative approaches.


> Regards,
> mpsuzuki
>

Reply via email to