Re: meson build system

[Vincent Torri]

On Tue, Jan 5, 2021 at 3:59 PM Werner LEMBERG <wl@gnu.org> wrote:
>
> > rm -rf builddir && mkdir builddir && cd builddir
> > meson .. \
> >       --prefix=$3 \
> >       --libdir=lib \
> >       --buildtype=release \
> >       --strip \
> >       --cross-file ../cross_toolchain.txt \
> >       --default-library shared \
> >       -Dharfbuzz=disabled > ../../config.log 2>&1
>
> I tried that, omitting the `--prefix` and `--cross-file` lines.
>
> > ninja $verbninja install > ../../make.log 2>&1
>
> I tried that, too, and for me everything works as expected.
>
> > In ftopion.h :
> >
> > #define FT_CONFIG_OPTION_USE_HARFBUZZ
> >
> > which seems wrong
>
> I don't get this.  For me, the generated file `builddir/ftoption.h`
> has HarfBuzz properly commented out.

ok, there is something odd, indeed :

with a freetype tarball, without launching meson, ' find . -name
ftoption.h' gives :

./devel/ftoption.h
./include/freetype/config/ftoption.h

first one : hb not commented
second one, hb commented

but when I launch meson out of tree (in builddir/) there is a third
(!) ftoption.h, the one generated by meson


> Is it possible that another `ftoption.h` file is present in your
> include path that takes precedence for whatever reason (e.g.,
> cross-compiling)?  Admittedly, I have never tried cross compilation
> with meson, so there might be bugs lurking around...

So I think you are right. ftoption.h in my builddir/ sub dir is taking
precedence

Vincent Torri



>
>     Werner