From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: recipe simplification questions
Date: Wed, 08 Sep 2010 11:40:20 -0700 [thread overview]
Message-ID: <4C87D894.9050609@mentor.com> (raw)
In-Reply-To: <AANLkTi=YqpnwM52LoTsVSb6wZJaGEXfyxrQiV_tMjwSH@mail.gmail.com>
Khem Raj wrote:
> On Wed, Sep 8, 2010 at 10:41 AM, Frans Meulenbroeks
> <fransmeulenbroeks@gmail.com> wrote:
>> Hi
>>
>> While browsing through a recipe I stumbled upon the following two functions:
[snip]
>> do_install() {
>> make install DESTDIR=${D}
>> }
>>
>
> this if used in a recipe which inherits autotools could be for getting
> parallelism out of context during install but not during compile.
> again this kind of stuff should be avoided.
Not true (but I had to double check just now, so it's quite possible
some others have assumed this behavior). If we look at bitbake.conf:
EXTRA_OEMAKE_prepend_task_do_compile = "${PARALLEL_MAKE} "
EXTRA_OEMAKE_prepend_task-compile = "${PARALLEL_MAKE} "
So in the case of literally having DESTDIR=${D}, these can just go away.
There are some annoying cases however where it's not DESTDIR but some
other variable. IMHO, it's questionable if it'd be cleaner to do a
custom one line do_install vs EXTRA_OEMAKE_append_task-do_install =
"PREFIX=${D}"
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2010-09-08 18:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-08 17:41 recipe simplification questions Frans Meulenbroeks
2010-09-08 17:49 ` Khem Raj
2010-09-08 18:40 ` Tom Rini [this message]
2010-09-08 18:48 ` Frans Meulenbroeks
2010-09-08 19:08 ` Tom Rini
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=4C87D894.9050609@mentor.com \
--to=tom_rini@mentor.com \
--cc=openembedded-devel@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 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.