From: "Ulrich Müller" <ulm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: general-concepts/dependencies/
Date: Wed, 29 Jan 2020 07:59:56 +0000 (UTC) [thread overview]
Message-ID: <1580284706.d25e172b16fa3c59f6868dc164bc6dcc801c4fc2.ulm@gentoo> (raw)
commit: d25e172b16fa3c59f6868dc164bc6dcc801c4fc2
Author: Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Sun Dec 29 07:59:28 2019 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Wed Jan 29 07:58:26 2020 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=d25e172b
general-concepts/dependencies: Document BDEPEND
Signed-off-by: Michał Górny <mgorny <AT> gentoo.org>
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
general-concepts/dependencies/text.xml | 48 ++++++++++++++++++++++++++++++++--
1 file changed, 46 insertions(+), 2 deletions(-)
diff --git a/general-concepts/dependencies/text.xml b/general-concepts/dependencies/text.xml
index 32feff1..8deca1f 100644
--- a/general-concepts/dependencies/text.xml
+++ b/general-concepts/dependencies/text.xml
@@ -11,17 +11,61 @@ provided by <c>emerge</c>.
</p>
</body>
+<section>
+<title>CHOST vs CBUILD</title>
+<body>
+
+<p>
+In order to avoid ambiguity, we use the following terms to indicate different
+systems when cross-compiling:
+</p>
+
+<dl>
+ <dt>CBUILD</dt>
+ <dd>
+ The system on which the build is performed. Dependencies that apply
+ to the CBUILD system can be executed during build time. When
+ cross-compiling, they are not installed into the system being built.
+ </dd>
+
+ <dt>CHOST</dt>
+ <dd>
+ The system on which the package is going to be executed. When
+ cross-compiling, dependencies applying to CHOST can not be executed.
+ </dd>
+</dl>
+
+<p>
+When not cross-compiling, CBUILD and CHOST have the same value and both classes
+of dependencies are merged.
+</p>
+
+</body>
+</section>
+
<section>
<title>Build Dependencies</title>
<body>
<p>
-The <c>DEPEND</c> ebuild variable should specify any dependencies which are
-required to unpack, patch, compile or install the package (but see
+Build dependencies are used to specify any dependencies that are required
+to unpack, patch, compile, test or install the package (but see
<uri link="::general-concepts/dependencies#Implicit System Dependency"/> for
exemptions).
</p>
+<p>
+Starting with EAPI 7, build dependencies are split into two variables:
+<c>BDEPEND</c> and <c>DEPEND</c>. <c>BDEPEND</c> specifies dependencies
+applicable to CBUILD, i.e. programs that need to be executed during the build,
+e.g. <c>virtual/pkgconfig</c>. <c>DEPEND</c> specifies dependencies for CHOST,
+i.e. packages that need to be found on built system, e.g. libraries and headers.
+</p>
+
+<p>
+In earlier EAPIs, all build dependencies are placed in <c>DEPEND</c>.
+</p>
+
</body>
</section>
next reply other threads:[~2020-01-29 7:59 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-29 7:59 Ulrich Müller [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-28 19:36 [gentoo-commits] proj/devmanual:master commit in: general-concepts/dependencies/ Ulrich Müller
2023-09-27 8:30 Ulrich Müller
2022-06-24 9:14 Ulrich Müller
2022-05-27 9:00 Ulrich Müller
2022-05-22 6:37 Joonas Niilola
2022-05-22 6:37 Joonas Niilola
2022-02-21 5:22 Sam James
2022-02-21 5:22 Sam James
2021-10-19 9:27 Mike Frysinger
2021-10-13 13:42 Ulrich Müller
2021-03-29 20:44 Ulrich Müller
2021-03-29 20:44 Ulrich Müller
2021-03-29 20:44 Ulrich Müller
2021-03-11 12:44 Ulrich Müller
2021-03-11 12:44 Ulrich Müller
2021-03-11 12:44 Ulrich Müller
2020-05-25 15:43 Ulrich Müller
2020-05-25 15:43 Ulrich Müller
2020-01-29 7:59 Ulrich Müller
2020-01-29 7:59 Ulrich Müller
2020-01-23 7:47 Ulrich Müller
2019-12-21 5:19 Ulrich Müller
2019-10-16 18:49 Göktürk Yüksek
2018-09-10 15:20 Mike Gilbert
2017-09-25 4:31 Göktürk Yüksek
2017-09-25 4:31 Göktürk Yüksek
2017-09-25 4:31 Göktürk Yüksek
2014-10-18 17:40 Markos Chandras
2013-07-29 21:53 Julian Ospald
2013-07-29 21:53 Julian Ospald
2011-02-17 21:08 Jeremy Olexa
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=1580284706.d25e172b16fa3c59f6868dc164bc6dcc801c4fc2.ulm@gentoo \
--to=ulm@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox