public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Claudius Heine <claudius.heine.ext@siemens.com>,
	Harald Seiler <hws@denx.de>,
	isar-users@googlegroups.com
Subject: Re: [PATCH 1/2] meta: Only use isar's own bitbake.conf
Date: Mon, 10 Dec 2018 10:32:33 +0100	[thread overview]
Message-ID: <83c53385-6ca0-06db-d0df-f3768b81d2c7@siemens.com> (raw)
In-Reply-To: <4cec2b2b-a568-baf8-a152-c7acf3697812@siemens.com>

On 10.12.18 10:31, Claudius Heine wrote:
> Hi Jan,
> 
> On 07/12/2018 15.30, [ext] Jan Kiszka wrote:
>> On 27.11.18 10:53, Harald Seiler wrote:
>>> Similarly to yocto, this commit makes isar only
>>> use its own bitbake.conf.  It also adds necessary
>>> variables from bitbake's config so everything still
>>> works.
>>>
>>> Signed-off-by: Harald Seiler <hws@denx.de>
>>> ---
>>>   meta/conf/isar-bitbake.conf | 28 ++++++++++++++++++++++++++++
>>>   scripts/isar-setup-builddir | 21 ---------------------
>>>   2 files changed, 28 insertions(+), 21 deletions(-)
>>>
>>> diff --git a/meta/conf/isar-bitbake.conf b/meta/conf/isar-bitbake.conf
>>> index bc52d08..f23bf6e 100644
>>> --- a/meta/conf/isar-bitbake.conf
>>> +++ b/meta/conf/isar-bitbake.conf
>>> @@ -18,6 +18,34 @@
>>>   # ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
>>>   # OTHER DEALINGS IN THE SOFTWARE.
>>> +# Variables from bitbake/conf/bitbake.conf
>>> +B = "${S}"
>>> +CVSDIR = "${DL_DIR}/cvs"
>>> +DEPENDS = ""
>>> +DEPLOY_DIR = "${TMPDIR}/deploy"
>>> +FILESPATH = 
>>> "${FILE_DIRNAME}/${PF}:${FILE_DIRNAME}/${P}:${FILE_DIRNAME}/${PN}:${FILE_DIRNAME}/files:${FILE_DIRNAME}" 
>>>
>>> +FILE_DIRNAME = "${@os.path.dirname(d.getVar('FILE', False))}"
>>> +GITDIR = "${DL_DIR}/git"
>>> +IMAGE_CMD = "_NO_DEFINED_IMAGE_TYPES_"
>>> +IMAGE_ROOTFS = "${TMPDIR}/rootfs"
>>> +OVERRIDES = "local:${MACHINE}:${TARGET_OS}:${TARGET_ARCH}"
>>> +P = "${PN}-${PV}"
>>> +PF = "${PN}-${PV}-${PR}"
>>> +PN = "${@bb.parse.BBHandler.vars_from_file(d.getVar('FILE', False),d)[0] or 
>>> 'defaultpkgname'}"
>>> +PR = "${@bb.parse.BBHandler.vars_from_file(d.getVar('FILE', False),d)[2] or 
>>> 'r0'}"
>>> +PROVIDES = ""
>>> +PV = "${@bb.parse.BBHandler.vars_from_file(d.getVar('FILE', False),d)[1] or 
>>> '1.0'}"
>>> +S = "${WORKDIR}/${P}"
>>> +SRC_URI = "file://${FILE}"
>>> +STAMP = "${TMPDIR}/stamps/${PF}"
>>> +SVNDIR = "${DL_DIR}/svn"
>>> +T = "${WORKDIR}/temp"
>>> +TARGET_ARCH = "${BUILD_ARCH}"
>>> +TMPDIR = "${TOPDIR}/tmp"
>>> +PERSISTENT_DIR = "${TMPDIR}/cache"
>>> +GITPKGV = "${@bb.fetch2.get_srcrev(d, 'gitpkgv_revision')}"
>>> +
>>> +# isar specific config
>>>   WORKDIR = "${TMPDIR}/work/${DISTRO}-${DISTRO_ARCH}/${PF}"
>>>   DEPLOY_DIR_BOOTSTRAP = "${DEPLOY_DIR}/bootstrap"
>>>   DEPLOY_DIR_IMAGE = "${DEPLOY_DIR}/images/${MACHINE}"
>>> diff --git a/scripts/isar-setup-builddir b/scripts/isar-setup-builddir
>>> index cabe732..d344148 100755
>>> --- a/scripts/isar-setup-builddir
>>> +++ b/scripts/isar-setup-builddir
>>> @@ -110,30 +110,9 @@ cat <<EOF > $BUILDDIR/conf/bitbake.conf
>>>   # THIS FILE IS GENERATED! DO NOT MESS WITH IT!
>>>   # ********************************************
>>> -# ---------
>>> -# begin original bitbake.conf
>>> -# ---------
>>> -
>>> -EOF
>>> -cat "$ISARROOT/bitbake/conf/bitbake.conf" >> \
>>> -  "$BUILDDIR/conf/bitbake.conf"
>>> -cat <<EOF >> $BUILDDIR/conf/bitbake.conf
>>> -# ---------
>>> -# end original bitbake.conf
>>> -# ---------
>>> -
>>> -# ---------
>>> -# begin isar-bitbake.conf
>>> -# ---------
>>> -
>>>   EOF
>>>   cat "$ISARROOT/meta/conf/isar-bitbake.conf" >> \
>>>     "$BUILDDIR/conf/bitbake.conf"
>>> -cat <<EOF >> $BUILDDIR/conf/bitbake.conf
>>> -# ---------
>>> -# end isar-bitbake.conf
>>> -# ---------
>>> -EOF
>>>   # Ending the first-time run message. Show the no documentation banner.
>>>   if [ ! -z "$SHOWYPDOC" ]; then
>>>
>>
>> This series is still pending, I just realized (while writing "all 
>> configuration starts with bitbake.conf").
>>
>> Looks good, I just think we should simply rename isar-bitbake.conf to 
>> bitbake.conf and copy that in during setup.
> 
> Why? That is not how it is done in current versions of OE.
> 
> The copying process implemented here is a relic from an older bitbake version, 
> where it didn't support loading the bitbake.conf from a layer.

Ah, you mean, we do not need to copy at all? That would be even better!

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

  reply	other threads:[~2018-12-10  9:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-27  9:52 [PATCH 0/2] Clean bitbake.conf and allow DL_DIR from env Harald Seiler
2018-11-27  9:53 ` [PATCH 1/2] meta: Only use isar's own bitbake.conf Harald Seiler
2018-12-07 14:30   ` Jan Kiszka
2018-12-10  9:31     ` Claudius Heine
2018-12-10  9:32       ` Jan Kiszka [this message]
2018-11-27  9:54 ` [PATCH 2/2] meta: Allow setting DL_DIR from environment Harald Seiler
2018-12-10 10:22 ` [PATCH v2 0/3] Clean bitbake.conf and allow DL_DIR from env claudius.heine.ext
2018-12-10 10:22   ` [PATCH v2 1/3] meta: Only use isar's own bitbake.conf claudius.heine.ext
2018-12-10 10:25     ` Harald Seiler
2018-12-10 10:22   ` [PATCH v2 2/3] meta: Allow setting DL_DIR from environment claudius.heine.ext
2018-12-10 10:22   ` [PATCH v2 3/3] meta: rename isar-bitbake.conf to bitbake.conf claudius.heine.ext
2018-12-10 12:05   ` [PATCH v2 0/3] Clean bitbake.conf and allow DL_DIR from env Maxim Yu. Osipov

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=83c53385-6ca0-06db-d0df-f3768b81d2c7@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=claudius.heine.ext@siemens.com \
    --cc=hws@denx.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