diff options
| author | Ryan Lucia <ryan@luciaonline.net> | 2019-02-02 01:32:43 -0500 |
|---|---|---|
| committer | Oneric <oneric@oneric.stub> | 2024-04-20 03:21:57 +0200 |
| commit | 342a0d2e767c33ff28a39794813294c67c9e7312 (patch) | |
| tree | b49bada328f1afa7132e5a584f28999cca4a8f02 /README.md | |
| parent | 2cea926568f0a06c2ec38b30bfb83714a6e259f1 (diff) | |
| download | libass-342a0d2e767c33ff28a39794813294c67c9e7312.tar.bz2 libass-342a0d2e767c33ff28a39794813294c67c9e7312.tar.xz | |
Add meson as a secondary build system
This will bring back a first-party buildsystem for MSVC
after the previous solution https://github.com/libass/libass-msvc
was retired and make it easier to use libass as a subproject
in other meson projects.
It does not currently support all of our utilities nor testing
and fuzzing infrastructure and x86_32 assembly is always built in
PIC mode.
Due to meson deficiencies shared libraries lack symbol export control
and it is not possible to build x32 assembly.
However, for packaging and downstream use it is feature complete on
Windows and static-only builds are sufficient for subproject use on any
platform, so it brings a net positive and keeping this level of support
up alongside autotools is expected to be barely any effort.
And ofc future meson versions and patches
to this build setup might improve it further.
The port was initially brought up by Ryan Lucia (CoffeeFlux)
and later further adapted and polished for merge
by arch1t3cht and torque, but several more people
contributed bits and pieces. They are listed in the following.
Reviewed-by: Eli Schwartz <eschwartz93@gmail.com>
Reviewed-by: Oneric <oneric@oneric.stub>
Co-authored-by: arch1t3cht <arch1t3cht@gmail.com>
Co-authored-by: torque <torque@users.noreply.github.com>
Co-authored-by: Luni-4 <luni-4@hotmail.it>
Co-authored-by: Funami580 <Funami580@users.noreply.github.com>
Co-authored-by: woclass <5158738+inkydragon@users.noreply.github.com>
Co-authored-by: line0 <line0@inbox.lv>
Co-authored-by: Myaamori <myaamori1993@gmail.com>
Co-authored-by: Xavier Claessens <xavier.claessens@collabora.com>
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 15 |
1 files changed, 15 insertions, 0 deletions
@@ -19,6 +19,21 @@ Please use the [issue tracker](https://github.com/libass/libass/issues?state=ope We have an IRC channel, too. Talk to us on [irc.libera.chat/#libass](https://web.libera.chat/#libass). Note that we cannot be online all the time and we cannot answer IRC questions if you leave the channel. Even if you do not get an immediate response, keep your IRC client open, and we will eventually get back to you. +Building +======== + +libass offers two build systems to choose from: Autotools and Meson. + +Autotools is preferred for development since it integrates with our testing +infrastructure and is feature-complete on all platforms supported by Autotools. +If you are packaging libass for distribution, Autotools is recommended; +when packaging for Windows Meson should work equally well. + +Meson lacks integration with testing infrastructure, but works otherwise well on +Windows. It is suited for static-only builds on any platform well supported by +Meson and as a Meson subproject. +Notably, Meson supports MSVC and generation of VS project files. + Related Links ============= The following projects/companies use libass: |