From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/3] gvfs: fix installation of gsettings schemas
Date: Wed, 13 Jul 2011 19:11:35 +0200 [thread overview]
Message-ID: <20110713191135.25b4454b@skate> (raw)
In-Reply-To: <1310576089-9207-3-git-send-email-s.neumann@raumfeld.com>
Le Wed, 13 Jul 2011 18:54:49 +0200,
Sven Neumann <s.neumann@raumfeld.com> a ?crit :
> -GVFS_POST_INSTALL_TARGET_HOOKS += GVFS_REMOVE_USELESS_BINARY
> +define GVFS_REMOVE_TARGET_SCHEMAS
> + rm $(TARGET_DIR)/usr/share/glib-2.0/schemas/*.xml
> +endef
> +
> +define GVFS_COMPILE_SCHEMAS
> + $(HOST_DIR)/usr/bin/glib-compile-schemas --targetdir=$(TARGET_DIR)/usr/share/glib-2.0/schemas $(STAGING_DIR)/usr/share/glib-2.0/schemas
> +endef
> +
> +GVFS_POST_INSTALL_TARGET_HOOKS += \
> + GVFS_REMOVE_USELESS_BINARY \
> + GVFS_REMOVE_TARGET_SCHEMAS \
> + GVFS_COMPILE_SCHEMAS
I have no idea what those schemas are, but why do you remove them in
GVFS_REMOVE_TARGET_SCHEMAS to generate them again in
GVFS_COMPILE_SCHEMAS ?
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2011-07-13 17:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-13 16:54 [Buildroot] [PATCH 1/3] gvfs: update to latest upstream version (1.8.2) Sven Neumann
2011-07-13 16:54 ` [Buildroot] [PATCH 2/3] gvfs: drop dbus-glib dependency Sven Neumann
2011-07-18 21:14 ` Peter Korsgaard
2011-07-13 16:54 ` [Buildroot] [PATCH 3/3] gvfs: fix installation of gsettings schemas Sven Neumann
2011-07-13 17:11 ` Thomas Petazzoni [this message]
2011-07-13 19:11 ` Sven Neumann
2011-07-18 21:18 ` Peter Korsgaard
2011-07-18 21:12 ` [Buildroot] [PATCH 1/3] gvfs: update to latest upstream version (1.8.2) Peter Korsgaard
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=20110713191135.25b4454b@skate \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.