Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Jack Mitchell <ml@communistcode.co.uk>
To: openembedded-core@lists.openembedded.org
Subject: Re: Why is "bitbake core-image-minimal" building gtk docs?
Date: Wed, 21 Aug 2013 09:40:34 +0100	[thread overview]
Message-ID: <52147D02.10106@communistcode.co.uk> (raw)
In-Reply-To: <CAOMwXhMD5FE2jK-R+5SCYRCtpS0S_Nk-6HhbsiUJt9i63-kHUQ@mail.gmail.com>

On 21/08/13 08:55, Laszlo Papp wrote:
> Ping?
> 
> 
> On Fri, Aug 16, 2013 at 1:15 PM, Jack Mitchell <ml@communistcode.co.uk
> <mailto:ml@communistcode.co.uk>> wrote:
> 
>     On 16/08/13 12:40, Laszlo Papp wrote:
>     > Hi,
>     >
>     > alternatively: is there an option to turn gtk, especially the docs
>     off?
>     >
>     > Cheers,
>     > Laszlo
>     >
>     >
> 
>     I don't know how to properly stop it building, or turn it off but I can
>     tell you the cause.
> 
>     Running bitbake -g core-image-minimal outputs the dependency graphs, and
>     by examining that it seems as though the following packages pull in
>     gtk-doc related packages.
> 
>     "connman" -> "gtk-doc-stub-native"
>     "kmod-native" -> "gtk-doc-stub-native"
>     "kmod" -> "gtk-doc-stub-native"
>     "glib-2.0" -> "gtk-doc-stub-native"
>     "glib-2.0-native" -> "gtk-doc-stub-native"
> 
>     Now, all these packages are gtk-doc-stub[-native], which is
>     described as:
> 
>     DESCRIPTION = "Stub implementation of gtk-doc, as we don't want to build
>     the API documentation"
> 
>     So it sounds like gtk-docs aren't actually being built, but the stubs
>     provide enough to make the package think they're being built...
> 
>     That's all I know, someone with more gtk knowledge than me can probably
>     fill in the reason for why it's required to build those packages.
> 
>     Cheers,
> 

Having a quick look around it seems as though glib can be built with
docs disabled:

--disable-gtk-doc and --enable-gtk-doc.  By default the configure script
will try to auto-detect whether the gtk-doc package is installed. If it
is, then it will use it to extract and build the documentation for the
GLib library. These options can be used to explicitly control whether
gtk-doc should be used or not. If it is not used, the distributed,
pre-generated HTML files will be installed instead of building them on
your machine.

the glib-2.0 recipe inherits gtk-doc, but doesn't disable it anywhere. I
imagine that you could add --disable-gtk-doc and remove the gtk-doc
inherit to stop glib-2.0 requiring the stub.

It seems here: http://patches.openembedded.org/patch/32567/

gtk-doc was specifically added back into the connman build.

kmod also has a --disable-gtk-doc configure option.

Here is the patch which kicks it all off:

http://lists.linuxtogo.org/pipermail/openembedded-core/2012-July/026077.html

So, make of this what you will. I've cc'd Ross in to see if he has a
specific reason for re-enabling gkt-doc in some packages. Maybe we
should turn it into an image feature...?

Regardless of all this though, it seems the packages will ship with docs
anyway, just pre-built HTML ones, so is it worth it?

-- 
  Jack Mitchell (jack@embed.me.uk)
  Embedded Systems Engineer
  Cambrideshire, UK
  http://www.embed.me.uk
--


  reply	other threads:[~2013-08-21  8:40 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-16 11:40 Why is "bitbake core-image-minimal" building gtk docs? Laszlo Papp
2013-08-16 12:15 ` Jack Mitchell
2013-08-21  7:55   ` Laszlo Papp
2013-08-21  8:40     ` Jack Mitchell [this message]
2013-08-21 10:04       ` Burton, Ross
2013-08-21 10:16         ` Laszlo Papp
2013-08-21 10:21           ` Burton, Ross
2013-08-21 10:24             ` Laszlo Papp
2013-08-21 10:26               ` Burton, Ross
2013-08-21 10:31                 ` Laszlo Papp
2013-08-21 11:04                   ` Martin Jansa
2013-08-21 11:10                     ` Laszlo Papp
2013-08-21 14:59                       ` Richard Purdie
2013-08-21 15:01                         ` Laszlo Papp
2013-08-29 16:19                         ` Laszlo Papp
2013-08-29 17:15                           ` Laszlo Papp
2013-08-30 13:42                             ` Laszlo Papp
2013-08-29 15:01                     ` Laszlo Papp
2013-08-29 15:10                       ` Martin Jansa

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=52147D02.10106@communistcode.co.uk \
    --to=ml@communistcode.co.uk \
    --cc=openembedded-core@lists.openembedded.org \
    /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