Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] libglib2 copies unwanted things to target
Date: Sat, 6 Feb 2010 17:12:56 +0100	[thread overview]
Message-ID: <20100206171256.771ec5f2@surf> (raw)
In-Reply-To: <4B684D2F.5090404@carallon.com>

Hi William,

On Tue, 02 Feb 2010 16:05:03 +0000
William Wagner <will_wagner@carallon.com> wrote:

> Have added the libglib2 package to my target and it seems to copy
> over a load of unwanted things into the target filesystem. In
> particular it copies a load of help files to target/usr/share/gtk-doc
> 
> The package uses the autotools framework which I'm not expert on so
> not sure the best way to tackle this. Should there just be a post
> target install step to go round and delete the unwanted files? I
> guess better would be to change the glib2 install target to one that
> does not copy over the help but I'm not familiar with the package so
> not sure if that is possible.
> 
> What does anyone suggest?

There are typically two approaches in Buildroot packages :

 * Either the .mk file does not use the "make install" target the
   package makefile to install the package to the target/ directory and
   manually installs only what's needed for runtime usage of the package
   software ;

 * Or the .mk file does use the "make install" target of the package
   makefile to install the package to the target/ directory and then
   cleans up the files that are not really needed for runtime usage of
   the package.

In the case of the libglib2 package, manually doing the package
installation to the target is maybe too complicated, so the second
solution is probably the easiest one. It would be something like:

define LIBGLIB2_REMOVE_DOCUMENTATION
 rm -rf $(TARGET_DIR)/usr/share/gtk-doc
endef

LIBGLIB2_POST_INSTALL_TARGET_HOOKS += LIBGLIB2_REMOVE_DOCUMENTATION

Cheers,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

      reply	other threads:[~2010-02-06 16:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-02 16:05 [Buildroot] libglib2 copies unwanted things to target William Wagner
2010-02-06 16:12 ` Thomas Petazzoni [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=20100206171256.771ec5f2@surf \
    --to=thomas.petazzoni@free-electrons.com \
    --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