From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: patches@linaro.org
Subject: Re: [meta-gnome][PATCH] abiword: force build order
Date: Sun, 20 Apr 2014 11:29:21 +0200 [thread overview]
Message-ID: <20140420092921.GG2486@jama> (raw)
In-Reply-To: <1397095971-17039-2-git-send-email-trevor.woerner@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 1297 bytes --]
On Wed, Apr 09, 2014 at 10:12:51PM -0400, Trevor Woerner wrote:
> There is a race condition whereby "libgoffice.la" must be built (and exist)
> before the rest of the code in "src" is built.
Merged, thanks
>
> Signed-off-by: Trevor Woerner <trevor.woerner@linaro.org>
> ---
> meta-gnome/recipes-gnome/abiword/abiword_3.0.0.bb | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/meta-gnome/recipes-gnome/abiword/abiword_3.0.0.bb b/meta-gnome/recipes-gnome/abiword/abiword_3.0.0.bb
> index 69d62ef..073622a 100644
> --- a/meta-gnome/recipes-gnome/abiword/abiword_3.0.0.bb
> +++ b/meta-gnome/recipes-gnome/abiword/abiword_3.0.0.bb
> @@ -50,6 +50,14 @@ do_configure() {
> autotools_do_configure
> }
>
> +do_compile() {
> + cd ${S}/goffice-bits2
> + make goffice-paths.h
> + make libgoffice.la
> + cd ${S}
> + oe_runmake
> +}
> +
> PACKAGES += " ${PN}-clipart ${PN}-strings ${PN}-systemprofiles ${PN}-templates "
>
> FILES_${PN} += " \
> --
> 1.9.0
>
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
prev parent reply other threads:[~2014-04-20 9:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-10 2:12 [meta-gnome][PATCH] abiword: force build order Trevor Woerner
2014-04-10 2:12 ` Trevor Woerner
2014-04-20 9:29 ` Martin Jansa [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=20140420092921.GG2486@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=patches@linaro.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 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.