Werner LEMBERG writes:
>>> BTW, how well does meson support cross compilation?
>>
>> it does support cross-compilation a lot better than cmake
>> on Windows (though compilation fails because of mmap) :
>
> Thanks for checking.
I've done some experimentation with 'picolibc', which uses meson
>> BTW, how well does meson support cross compilation?
>
> it does support cross-compilation a lot better than cmake
> on Windows (though compilation fails because of mmap) :
Thanks for checking.
Werner
On Tue, Aug 25, 2020 at 5:55 AM Werner LEMBERG wrote:
> BTW, how well does meson support cross compilation?
it does support cross-compilation a lot better than cmake
on Windows (though compilation fails because of mmap) :
$ ./configure.sh
The Meson build system
Version: 0.54.2
Source dir:
> I propose to get rid of this template entirely for Meson, by
> defining HAVE_UNISTD_H and HAVE_FCNTL_H as simple compiler arguments
> when building the library.
What exactly do you mean with 'compiler arguments'?
> For the builds/unix/ftconfig.h.in case, there is also
>
Le lun. 24 août 2020 à 22:34, Werner LEMBERG a écrit :
>
> Hello David,
>
>
> > - builds/meson/ftconfig.h.in: template versions of
> > ftconfig.h to be used by the Meson build. It is processed
> > by Meson, which will turn #mesondefine statements into
> > #define / #undef depending on
Hello David,
> - builds/meson/ftconfig.h.in: template versions of
> ftconfig.h to be used by the Meson build. It is processed
> by Meson, which will turn #mesondefine statements into
> #define / #undef depending on build configuration.
having a meson-specific `ftconfig.h.in` file is not
Hi Alexei,
Le lun. 24 août 2020 à 17:27, Alexei Podtelezhnikov a
écrit :
> Hi David,
>
> Other build systems 'sed' to the main copy of ftoption.h, which is
> then installed and provides a record of compiled features. Werner
> convinced me that it is a good thing to have. It will be a nightmare
Hi David,
Other build systems 'sed' to the main copy of ftoption.h, which is
then installed and provides a record of compiled features. Werner
convinced me that it is a good thing to have. It will be a nightmare
to maintain them if each build system has its own version while lose
track of
Hello Vincent,
Sorry, was on vacation and pretty busy, but back now. On the topic of the
Meson build, here's my latest update. This version has many improvements:
- Proper pkg-config freetype2.pc generation and installation.
- Fixed shared library install suffix to match libtool-generated one
Hello David
any news on the meson build system ?
regards
Vincent Torri
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
On Tue, Jul 28, 2020 at 7:18 AM Vincent Torri wrote:
>
> hello
>
> i've just tried. One thing : with bzip2 enabled, bz2.pc file is not
> found. Is there any reason why you check it ? Officially (bzip2 1.0.8
> here : https://sourceware.org/pub/bzip2/) there is no pc file
> distributed with it.
>
>
hello
i've just tried. One thing : with bzip2 enabled, bz2.pc file is not
found. Is there any reason why you check it ? Officially (bzip2 1.0.8
here : https://sourceware.org/pub/bzip2/) there is no pc file
distributed with it.
in the gitlab repo : https://gitlab.com/federicomenaquintero/bzip2,
Hello Vincent,
+cc freetype-devel
Yes, I'm working on a local branch and I've sent an experimental patch to
the mailing list some weeks ago. Here's a more recent version rebased on
top of latest changes.
There is a list of TODO() at the end of the meson.build file if you're
curious. Next step
14 matches
Mail list logo
