From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Randy MacLeod <randy.macleod@windriver.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 00/28] Enable gtk-doc
Date: Fri, 2 Sep 2016 18:06:11 +0300 [thread overview]
Message-ID: <e83ab03a-ae9f-cf9a-2838-1b16b15a4e16@linux.intel.com> (raw)
In-Reply-To: <075b7a5f-14d8-5999-2fda-da8bae3d893e@windriver.com>
On 09/02/2016 12:59 AM, Randy MacLeod wrote:
>> Gtk-doc generation happens if 'api-documentation' distro feature is
>> enabled
>> (it is by default), and 'qemu-usermode' is in machine features.
>
> Should this really be enabled by default?
> What does it do to a typical build wrt time and space?
The default distro feature list also includes all of the available
communication stacks, full x11 stack, pulseaudio etc. It seems to me
that the aim is to enable as many various features as possible by
default. Distros can and should trim the list to their specific needs.
Space isn't affected much on build host, and if you don't install -doc
packages it's not affected on the target at all. Build time is somewhat
longer for specific packages (those which have gtk-doc support), but
whether the overall, parallelized build is affected I don't know - I
think RP asked someone to do a test for master-next vs. master now (with
all the other stuff that went in recently).
Alex
next prev parent reply other threads:[~2016-09-02 15:07 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-26 14:28 [PATCH 00/28] Enable gtk-doc Alexander Kanavin
2016-08-26 14:28 ` [PATCH 01/28] source-highlight: add a recipe Alexander Kanavin
2016-08-26 14:28 ` [PATCH 02/28] gtk-doc: add a recipe, remove gtk-doc-stub Alexander Kanavin
2016-08-26 14:28 ` [PATCH 03/28] bitbake.conf: add "api-documentation" to default distro features Alexander Kanavin
2016-08-26 14:28 ` [PATCH 04/28] gtk-doc.bbclass: enable building gtk-doc based documentation Alexander Kanavin
2016-08-26 14:28 ` [PATCH 05/28] kmod: do not let gtkdocize fail Alexander Kanavin
2016-08-26 14:28 ` [PATCH 06/28] systemd: drop unused gtkdoc-related variable Alexander Kanavin
2016-08-26 14:28 ` [PATCH 07/28] libglade: remove the recipe Alexander Kanavin
2016-08-26 14:28 ` [PATCH 08/28] gstreamer1.0: enable gtk-doc support Alexander Kanavin
2016-08-26 14:28 ` [PATCH 09/28] webkitgtk: " Alexander Kanavin
2016-08-26 14:28 ` [PATCH 10/28] gcr: disable gtk-doc on x86_64 Alexander Kanavin
2016-08-26 14:28 ` [PATCH 11/28] gcr, libsecret, webkitgtk: disable gtk-doc on mips64 Alexander Kanavin
2016-08-26 14:28 ` [PATCH 12/28] webkitgtk: re-enable introspection on powerpc Alexander Kanavin
2016-08-26 14:28 ` [PATCH 13/28] dbus-glib: enable gtk-doc Alexander Kanavin
2016-08-26 14:28 ` [PATCH 14/28] orc: " Alexander Kanavin
2016-08-26 14:28 ` [PATCH 15/28] libidn: " Alexander Kanavin
2016-08-26 14:28 ` [PATCH 16/28] libuser: " Alexander Kanavin
2016-08-26 14:28 ` [PATCH 17/28] gdk-pixbuf: " Alexander Kanavin
2016-08-26 14:28 ` [PATCH 18/28] gnome-desktop3: " Alexander Kanavin
2016-08-26 14:28 ` [PATCH 19/28] json-glib: " Alexander Kanavin
2016-08-26 14:28 ` [PATCH 20/28] libgudev: " Alexander Kanavin
2016-08-26 14:28 ` [PATCH 21/28] libenck3: " Alexander Kanavin
2016-08-26 14:28 ` [PATCH 22/28] cairo: " Alexander Kanavin
2016-08-26 14:28 ` [PATCH 23/28] harfbuzz: " Alexander Kanavin
2016-08-26 14:28 ` [PATCH 24/28] gnutls: " Alexander Kanavin
2016-08-26 14:28 ` [PATCH 25/28] libtasn1: " Alexander Kanavin
2016-08-26 14:28 ` [PATCH 26/28] libsoup-2.4: " Alexander Kanavin
2016-08-26 14:28 ` [PATCH 27/28] p11-kit: " Alexander Kanavin
2016-08-26 14:28 ` [PATCH 28/28] util-linux: do not enable gtk-doc and explain why Alexander Kanavin
2016-08-31 7:48 ` [PATCH 00/28] Enable gtk-doc Richard Purdie
2016-09-01 21:59 ` Randy MacLeod
2016-09-02 15:06 ` Alexander Kanavin [this message]
2016-09-05 6:58 ` Anders Darander
2016-09-09 13:42 ` Richard Purdie
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=e83ab03a-ae9f-cf9a-2838-1b16b15a4e16@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=randy.macleod@windriver.com \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox