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: Fri, 16 Aug 2013 13:15:50 +0100	[thread overview]
Message-ID: <520E17F6.4030500@communistcode.co.uk> (raw)
In-Reply-To: <CAOMwXhNaMEvSfi-J=EPOXfSAfjWUJeq8pGAGE3_5Hix1Sw9mKg@mail.gmail.com>

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,

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


  reply	other threads:[~2013-08-16 12:15 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 [this message]
2013-08-21  7:55   ` Laszlo Papp
2013-08-21  8:40     ` Jack Mitchell
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=520E17F6.4030500@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