From: Alexander Smirnov <asmirnov@ilbers.de>
To: isar-users@googlegroups.com
Cc: Alexander Smirnov <asmirnov@ilbers.de>
Subject: [PATCH] doc: Update technical overview
Date: Tue, 12 Sep 2017 17:26:05 +0300 [thread overview]
Message-ID: <20170912142605.16253-1-asmirnov@ilbers.de> (raw)
In-Reply-To: <20170911192738.1323-1-asmirnov@ilbers.de>
BUILDCHROOT is no more used for storing sources to build custom package.
This patch updates the respective topic in technical overview.
Signed-off-by: Alexander Smirnov <asmirnov@ilbers.de>
---
doc/technical_overview.md | 11 +++++------
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git a/doc/technical_overview.md b/doc/technical_overview.md
index a4563b3..0c86577 100644
--- a/doc/technical_overview.md
+++ b/doc/technical_overview.md
@@ -160,11 +160,11 @@ contain debian folder. The build process is implemented in
1. Task `do_fetch`: fetch source code from external link
-2. Task `do_unpack`: unpack source code to
- `${BUILDCHROOT_DIR}/home/build/${PN}`
+2. Task `do_unpack`: unpack source code to `${WORKDIR}`
-3. Task `do_build`: switch to buildchroot using chroot command and run
- `build.sh` script. The `build.sh` script performs the following:
+3. Task `do_build`: mount folder with source code to buildchroot, switch
+ to buildchroot using chroot command and run `build.sh` script. The
+ `build.sh` script performs the following:
1. Go to `/home/build/${PN}`
@@ -173,8 +173,7 @@ contain debian folder. The build process is implemented in
3. Run dpkg-buildpackage
4. Task `do_install`: install successfully built packages
- `${BUILDCHROOT_DIR}/home/build/${PN}/*.deb` to deploy directory
- `${DEPLOY_DIR_DEB}`
+ `${WORKDIR}/*.deb` to deploy directory `${DEPLOY_DIR_DEB}`
## 3.5 Populate Target Filesystem
--
2.1.4
prev parent reply other threads:[~2017-09-12 14:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-11 19:27 [PATCH v3 0/5] Unify work space for packages Alexander Smirnov
2017-09-11 19:27 ` [PATCH v3 1/5] image: Unify path to image rootfs Alexander Smirnov
2017-09-11 19:27 ` [PATCH v3 2/5] isar: Change build folders tree Alexander Smirnov
2017-09-12 7:23 ` Claudius Heine
2017-09-12 7:57 ` Alexander Smirnov
2017-09-12 12:52 ` Henning Schild
2017-09-12 13:02 ` Alexander Smirnov
2017-09-11 19:27 ` [PATCH v3 3/5] stamps: Name stamps canonicaly and unified Alexander Smirnov
2017-09-11 19:27 ` [PATCH v3 4/5] image: Name image " Alexander Smirnov
2017-09-11 19:27 ` [PATCH v3 5/5] class/dpkg: Unify workplace for packages Alexander Smirnov
2017-09-12 14:26 ` Alexander Smirnov [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=20170912142605.16253-1-asmirnov@ilbers.de \
--to=asmirnov@ilbers.de \
--cc=isar-users@googlegroups.com \
/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