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 compiled features. It has a lot of important documentation to
keep in sync too. Would you please use 'sed' directly?
An excellent point, thanks for pointing this out. Here's a new version of the patch that does just that with a helper script.
I'd like to extend this scheme to more configuration variables in the future, but after we complete this build transition.
- David
Thank you,
Alexei
On Mon, Aug 24, 2020 at 10:55 AM David Turner <david@freetype.org> wrote:
>
> 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 (number computed from the version_info in build/unix/configure.raw).
> - Auto-generation of ftmodule.h and list of base extensions, based on modules.cfg
> - Generation of reference documentation (with "docs" target, but only inside the build directory).
>
> The last remaining todo is the ability to create a distribution package, though that might be handled by an independent script as well, since it needs to run "autogen.sh" in a temporary directory.
>
> Can you tell me about the Windows compilation failure? mmap() should not be an issue due to the checks in the build.meson file which should use src/base/ftsystem.c for Windows.
> I've setup a Window virtual machine and will start testing with it soon.
>
> Regards
>
> - David
>
>
> Le mar. 18 août 2020 à 21:11, Vincent Torri <vincent.torri@gmail.com> a écrit :
>>
>> Hello David
>>
>> any news on the meson build system ?
>>
>> regards
>>
>> Vincent Torri
--
Alexei A. Podtelezhnikov, PhD