From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: 37850@debbugs.gnu.org
Subject: bug#37850: Glib documentation is missing
Date: Tue, 12 Nov 2019 13:32:33 +0100 [thread overview]
Message-ID: <20191112123233.jkcevtpkz5i2yut5@pelzflorian.localdomain> (raw)
In-Reply-To: <87woc6kbhc.fsf@ambrevar.xyz>
On Mon, Nov 11, 2019 at 10:29:03AM +0100, Pierre Neidhardt wrote:
> Sadly the above does not build the doc.
>
> Looking at the source, it seems that no provision is taken for building
> the doc with Meson. I wonder if this is an upstream mistake, but my
> knowledge of Meson is very limited and I could be wrong.
>
> Any idea, anyone?
>
I have not checked, but
https://mesonbuild.com/Gnome-module.html
says about gtkdoc
> This creates a $module-doc target that can be ran to build docs and
> normally these are only built on install.
Since GNOME is a big supporter of Meson, I believe they make no
mistakes in GLib’s meson files.
Regards,
Florian
next prev parent reply other threads:[~2019-11-12 12:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-21 10:45 bug#37850: Glib documentation is missing Pierre Neidhardt
2019-10-23 18:22 ` Marius Bakke
2019-10-23 18:38 ` Pierre Neidhardt
2019-10-25 21:23 ` Ludovic Courtès
2019-10-26 9:04 ` Pierre Neidhardt
2019-10-29 10:36 ` Pierre Neidhardt
2019-11-03 16:39 ` Pierre Neidhardt
2019-11-03 19:04 ` Marius Bakke
2019-11-04 9:46 ` Pierre Neidhardt
2019-11-09 23:20 ` Marius Bakke
2019-11-11 9:29 ` Pierre Neidhardt
2019-11-12 12:32 ` pelzflorian (Florian Pelz) [this message]
2019-11-12 13:22 ` pelzflorian (Florian Pelz)
2019-11-12 16:00 ` Pierre Neidhardt
2019-11-12 18:34 ` pelzflorian (Florian Pelz)
2019-11-15 11:17 ` Pierre Neidhardt
2019-11-15 12:14 ` pelzflorian (Florian Pelz)
2019-11-15 14:10 ` Marius Bakke
2019-11-15 15:06 ` Pierre Neidhardt
2019-11-21 19:50 ` Marius Bakke
2019-11-27 12:37 ` Pierre Neidhardt
2019-11-09 2:03 ` Alexandros Theodotou
2019-11-09 2:10 ` Alexandros Theodotou
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191112123233.jkcevtpkz5i2yut5@pelzflorian.localdomain \
--to=pelzflorian@pelzflorian.de \
--cc=37850@debbugs.gnu.org \
--cc=mail@ambrevar.xyz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.