From: Claudius Heine <ch@denx.de>
To: Alexander Smirnov <asmirnov@ilbers.de>,
Henning Schild <henning.schild@siemens.com>
Cc: isar-users@googlegroups.com
Subject: Re: [PATCH 1/2] isar: Change build folders tree
Date: Sat, 09 Sep 2017 11:39:20 +0200 [thread overview]
Message-ID: <1504949960.1769.6.camel@denx.de> (raw)
In-Reply-To: <06b45946-1011-4bc4-8eff-e0ef1a242dfe@ilbers.de>
[-- Attachment #1: Type: text/plain, Size: 2497 bytes --]
Hi,
On Fri, 2017-09-08 at 15:36 +0300, Alexander Smirnov wrote:
> > >
> > > BUILDCHROOT_PREINSTALL ?= "gcc \
> > > make \
> > > @@ -21,8 +22,6 @@ BUILDCHROOT_PREINSTALL ?= "gcc \
> > > apt \
> > > automake"
> > >
> > > -WORKDIR = "${TMPDIR}/work/${PF}/${DISTRO}"
> > > -
> > > do_build[stamp-extra-info] = "${DISTRO}-${DISTRO_ARCH}"
> > >
> > > do_build() {
> > > @@ -40,9 +39,9 @@ do_build() {
> > > sed -i 's|##DISTRO_APT_SOURCE##|${DISTRO_APT_SOURCE}|'
> > > ${WORKDIR}/multistrap.conf sed -i
> > > 's|##DISTRO_SUITE##|${DISTRO_SUITE}|' ${WORKDIR}/multistrap.conf
> > > sed
> > > -i 's|##DISTRO_COMPONENTS##|${DISTRO_COMPONENTS}|'
> > > ${WORKDIR}/multistrap.conf
> > > - sed -i
> > > 's|##CONFIG_SCRIPT##|./tmp/work/${PF}/${DISTRO}/configscript.sh|'
> > > ${WORKDIR}/multistrap.conf
> > > - sed -i
> > > 's|##SETUP_SCRIPT##|./tmp/work/${PF}/${DISTRO}/setup.sh|'
> > > ${WORKDIR}/multistrap.conf
> > > - sed -i
> > > 's|##DIR_HOOKS##|./tmp/work/${PF}/${DISTRO}/hooks_multistrap|'
> > > ${WORKDIR}/multistrap.conf
> > > + sed -i
> > > 's|##CONFIG_SCRIPT##|./tmp/work/${DISTRO}-
> > > ${DISTRO_ARCH}/${PF}/configscript.sh|'
> > > ${WORKDIR}/multistrap.conf
> > > + sed -i
> > > 's|##SETUP_SCRIPT##|./tmp/work/${DISTRO}-
> > > ${DISTRO_ARCH}/${PF}/setup.sh|'
> > > ${WORKDIR}/multistrap.conf
> > > + sed -i
> > > 's|##DIR_HOOKS##|./tmp/work/${DISTRO}-
> > > ${DISTRO_ARCH}/${PF}/hooks_multistrap|'
> > > ${WORKDIR}/multistrap.conf
> >
> > The pattern tmp/work/${DISTRO}-${DISTRO_ARCH}/${PF}/ shows up all
> > the
> > time, can that be derived from $WORKDIR instead of writing it down
> > again and again?
>
> That's mad, but mulstistrap understands relative paths only. Any
> attempt
> to replace it by absolute path lead to errors. That's why it was done
> in
> this way, because WORKDIR is absolute path. :-(
If only multistrap cannot deal with absolute paths, why not use
`os.path.relpath` in these instances?
Cheers,
Claudius
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: ch@denx.de
PGP key: 6FF2 E59F 00C6 BC28 31D8 64C1 1173 CB19 9808 B153
Keyserver: hkp://pool.sks-keyservers.net
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-09-09 9:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-08 9:48 [PATCH 0/2] Unify work space for packages Alexander Smirnov
2017-09-08 9:48 ` [PATCH 1/2] isar: Change build folders tree Alexander Smirnov
2017-09-08 11:47 ` Henning Schild
2017-09-08 12:36 ` Alexander Smirnov
2017-09-08 12:59 ` Henning Schild
2017-09-08 13:07 ` Henning Schild
2017-09-08 13:20 ` Alexander Smirnov
2017-09-08 13:36 ` Henning Schild
2017-09-09 9:39 ` Claudius Heine [this message]
2017-09-11 7:28 ` Alexander Smirnov
2017-09-11 8:27 ` Claudius Heine
2017-09-11 8:41 ` Alexander Smirnov
2017-09-08 9:48 ` [PATCH 2/2] class/dpkg: Unify workplace for packages Alexander Smirnov
2017-09-08 11:29 ` Henning Schild
2017-09-08 10:01 ` [PATCH 0/2] Unify work space " Alexander Smirnov
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=1504949960.1769.6.camel@denx.de \
--to=ch@denx.de \
--cc=asmirnov@ilbers.de \
--cc=henning.schild@siemens.com \
--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