From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Remove gtk-doc documentations from target
Date: Wed, 05 May 2010 12:17:55 +0200 [thread overview]
Message-ID: <87ocgubqjw.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20100505100936.6123.58539.stgit@pauliusz> (Paulius Zaleckas's message of "Wed, 05 May 2010 13:09:36 +0300")
>>>>> "Paulius" == Paulius Zaleckas <paulius.zaleckas@gmail.com> writes:
Paulius> On my target rootfs it is installed documentation for:
Paulius> atk, cairo, gdk, gdk-pixbuf, gio, glib, gobject, gtk, pango
Paulius> It ocupies 34M of space. Configure option --disable-gtk-doc doesn't
Paulius> prevent installation of it. So we should remove them manually if
Paulius> documentation is disabled.
I was thinking the exact same thing yesterday - Committed, thanks.
I'll get rid of the manual cleanups we do in some places as well:
git grep usr/share/gtk-doc
hal/hal.mk: rm -rf $(TARGET_DIR)/usr/share/gtk-doc
libglade/libglade.mk: rm -rf $(TARGET_DIR)/usr/share/gtk-doc \
libxml2/libxml2.mk: $(TARGET_DIR)/usr/share/gtk-doc
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2010-05-05 10:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-05 10:09 [Buildroot] [PATCH] Remove gtk-doc documentations from target Paulius Zaleckas
2010-05-05 10:17 ` Peter Korsgaard [this message]
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=87ocgubqjw.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/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