GNOME Bugzilla – Bug 783617
build: Add meson support
Last modified: 2018-03-26 14:35:24 UTC
To try this out once the jhbuild patch is applied, you can run jhbuild buildone gnome-user-docs assuming you have an up-to-date jhbuild. Or you could run something like meson builddir ninja -C builddir ninja -C builddir install
Created attachment 353501 [details] [review] build: Add meson support https://wiki.gnome.org/Initiatives/GnomeGoals/MesonPorting
Created attachment 353502 [details] [review] 3.26: Switch gnome-user-docs to meson The jhbuild patch
To make a release tarball after switching to meson and dropping autotools support, you can use this script (change the name from epiphany): https://git.gnome.org/browse/epiphany/tree/make_release.sh meson 0.41 will be released soon with a built-in way to make tarballs.
Thanks for the patches, Jeremy. Now that is a GNOME Goal, I guess it makes sense to switch everything. Would you be able to provide patches for other -docs modules as well?
(In reply to Petr Kovar from comment #4) > Thanks for the patches, Jeremy. Now that is a GNOME Goal, I guess it makes > sense to switch everything. Would you be able to provide patches for other > -docs modules as well? I think it's an optional GNOME goal, but it looks like most GNOME maintainers like meson or don't mind the change too much. Are you thinking of any other modules besides gnome-devel-docs? That one is a bit more complicated because it has some build tests in platform-demos, but I or someone could probably figure it out.
(In reply to Jeremy Bicha from comment #5) > Are you thinking of any other modules besides gnome-devel-docs? That one is > a bit more complicated because it has some build tests in platform-demos, > but I or someone could probably figure it out. https://git.gnome.org/browse/gnome-getting-started-docs/
(In reply to Petr Kovar from comment #6) > https://git.gnome.org/browse/gnome-getting-started-docs/ I think that's going to increase the size of the tarballs a bit because I think the tarball will include the animation/ directory. But technically, I believe distros prefer that source tarballs include all the source files.
(In reply to Jeremy Bicha from comment #7) > (In reply to Petr Kovar from comment #6) > > https://git.gnome.org/browse/gnome-getting-started-docs/ > > I think that's going to increase the size of the tarballs a bit because I > think the tarball will include the animation/ directory. But technically, I > believe distros prefer that source tarballs include all the source files. Not really a Meson user, but is there no way to exclude source directories? Distributing contents in animation/ is not very useful. Anyway, this should probably go into a separate bug.
Yes, I can open additional bugs, but I'd like to wait for the conversion of this module to happen first in case there any concerns or issues.
meson 0.41 was just released with support for creating tarballs. You can use it like this: meson builddir ninja -C builddir dist The tarball will then be in the builddir/meson-dist/ directory. http://mesonbuild.com/Creating-releases.html It does not support excluding files but I think theanimation/ directory really ought to be included in the release tarballs anyway since it is indeed part of the source code.
It seems like we need to wait until Damned Lies actually supports Meson.
For now, I pushed the buildsystem change to the wip/switch-to-meson branch so that it can be more easily tested.
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome-user-docs/issues/18.