From: Denys Dmytriyenko <denis@denix.org>
To: meta-arago@arago-project.org
Subject: [oe-layersetup][PATCH] local-arago*.conf: set DEPLOY_DIR explicitly, deprecate custom parallel settings
Date: Sun, 26 Apr 2020 17:01:14 -0400 [thread overview]
Message-ID: <1587934874-44923-1-git-send-email-denis@denix.org> (raw)
From: Denys Dmytriyenko <denys@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
---
sample-files/local-arago.conf.sample | 9 ++++++---
sample-files/local-arago64.conf.sample | 9 ++++++---
2 files changed, 12 insertions(+), 6 deletions(-)
diff --git a/sample-files/local-arago.conf.sample b/sample-files/local-arago.conf.sample
index ea37da9..7c7a336 100644
--- a/sample-files/local-arago.conf.sample
+++ b/sample-files/local-arago.conf.sample
@@ -48,7 +48,8 @@ SSTATE_DIR = "${OEBASE}/build/sstate-cache"
# where BitBake should place its temporary files and output. Keep in mind that
# this includes the extraction and compilation of many applications and the toolchain
# which can use Gigabytes of hard disk space.
-TMPDIR = "${OEBASE}/build/arago-tmp"
+TMPDIR = "${TOPDIR}/arago-tmp"
+DEPLOY_DIR = "${TOPDIR}/deploy"
#
# Machine Selection
@@ -135,15 +136,17 @@ ENABLE_BINARY_LOCALE_GENERATION = "0"
# These two options control how much parallelism BitBake should use. The first
# option determines how many tasks bitbake should run in parallel:
#
-BB_NUMBER_THREADS = "1"
+#BB_NUMBER_THREADS = "1"
#
# The second option controls how many processes make should run in parallel when
# running compile tasks:
#
-PARALLEL_MAKE = "-j 1"
+#PARALLEL_MAKE = "-j 1"
#
# For a quad-core machine, BB_NUMBER_THREADS = "4", PARALLEL_MAKE = "-j 4" would
# be appropriate for example
+# These options don't need to be set manually, as OE will determine them automatically,
+# unless need to override that default.
DISTRO = "arago"
diff --git a/sample-files/local-arago64.conf.sample b/sample-files/local-arago64.conf.sample
index e5113fe..1e21185 100644
--- a/sample-files/local-arago64.conf.sample
+++ b/sample-files/local-arago64.conf.sample
@@ -48,7 +48,8 @@ SSTATE_DIR = "${OEBASE}/build/sstate-cache"
# where BitBake should place its temporary files and output. Keep in mind that
# this includes the extraction and compilation of many applications and the toolchain
# which can use Gigabytes of hard disk space.
-TMPDIR = "${OEBASE}/build/arago-tmp"
+TMPDIR = "${TOPDIR}/arago-tmp"
+DEPLOY_DIR = "${TOPDIR}/deploy"
#
# Machine Selection
@@ -135,15 +136,17 @@ ENABLE_BINARY_LOCALE_GENERATION = "0"
# These two options control how much parallelism BitBake should use. The first
# option determines how many tasks bitbake should run in parallel:
#
-BB_NUMBER_THREADS = "1"
+#BB_NUMBER_THREADS = "1"
#
# The second option controls how many processes make should run in parallel when
# running compile tasks:
#
-PARALLEL_MAKE = "-j 1"
+#PARALLEL_MAKE = "-j 1"
#
# For a quad-core machine, BB_NUMBER_THREADS = "4", PARALLEL_MAKE = "-j 4" would
# be appropriate for example
+# These options don't need to be set manually, as OE will determine them automatically,
+# unless need to override that default.
DISTRO = "arago"
--
2.7.4
reply other threads:[~2020-04-26 21:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1587934874-44923-1-git-send-email-denis@denix.org \
--to=denis@denix.org \
--cc=meta-arago@arago-project.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.