From: Andre McCurdy <armccurdy@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: [meta-browser][PATCH 2/2] chromium: use PARALLEL_MAKE to control build parallelism
Date: Tue, 10 Nov 2015 20:48:16 -0800 [thread overview]
Message-ID: <1447217296-7145-2-git-send-email-armccurdy@gmail.com> (raw)
In-Reply-To: <1447217296-7145-1-git-send-email-armccurdy@gmail.com>
Signed-off-by: Andre McCurdy <armccurdy@gmail.com>
---
recipes-browser/chromium/chromium_40.0.2214.91.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/recipes-browser/chromium/chromium_40.0.2214.91.bb b/recipes-browser/chromium/chromium_40.0.2214.91.bb
index a9635cd..f20610c 100644
--- a/recipes-browser/chromium/chromium_40.0.2214.91.bb
+++ b/recipes-browser/chromium/chromium_40.0.2214.91.bb
@@ -196,7 +196,7 @@ do_configure_append() {
do_compile() {
# build with ninja
- ninja -C ${S}/out/${CHROMIUM_BUILD_TYPE} -j${BB_NUMBER_THREADS} chrome chrome_sandbox
+ ninja -C ${S}/out/${CHROMIUM_BUILD_TYPE} ${PARALLEL_MAKE} chrome chrome_sandbox
}
--
1.9.1
next prev parent reply other threads:[~2015-11-11 4:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-11 4:48 [meta-browser][PATCH 1/2] cef3: use PARALLEL_MAKE to control build parallelism Andre McCurdy
2015-11-11 4:48 ` Andre McCurdy [this message]
2015-11-11 4:55 ` [meta-browser][PATCH 2/2] chromium: " Khem Raj
2015-11-14 14:04 ` Nikolay Dimitrov
2015-11-16 18:15 ` Andre McCurdy
2015-11-17 12:32 ` Nikolay Dimitrov
2015-11-11 4:54 ` [meta-browser][PATCH 1/2] cef3: " Khem Raj
2015-11-11 5:48 ` Zoltan Kuscsik
2015-11-11 6:32 ` Khem Raj
2015-11-11 7:22 ` Andre McCurdy
2015-11-12 6:07 ` Zoltan Kuscsik
2015-11-12 9:26 ` Julien Brianceau (jbriance)
2015-11-12 9:34 ` Andreas Müller
2015-11-12 9:44 ` Julien Brianceau (jbriance)
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=1447217296-7145-2-git-send-email-armccurdy@gmail.com \
--to=armccurdy@gmail.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.