public inbox for bitbake-devel@lists.openembedded.org
 help / color / mirror / Atom feed
From: Alexander Kanavin <alex.kanavin@gmail.com>
To: bitbake-devel@lists.openembedded.org
Cc: Alexander Kanavin <alex@linutronix.de>
Subject: [PATCH 1/2] bitbake-setup: ensure that relative local path given on 'init' command line is recorded as an absolute path
Date: Thu,  5 Mar 2026 21:09:36 +0100	[thread overview]
Message-ID: <20260305200937.221484-1-alex.kanavin@gmail.com> (raw)

From: Alexander Kanavin <alex@linutronix.de>

Otherwise status/update operations will fail if executed from a different
directory that the template file was in, as they won't be able to find
the file.

Signed-off-by: Alexander Kanavin <alex@linutronix.de>
---
 bin/bitbake-setup | 1 +
 1 file changed, 1 insertion(+)

diff --git a/bin/bitbake-setup b/bin/bitbake-setup
index bdf134aea..1a42aaa51 100755
--- a/bin/bitbake-setup
+++ b/bin/bitbake-setup
@@ -600,6 +600,7 @@ def obtain_config(top_dir, registry, args, source_overrides, d):
         config_id = args.config[0]
         config_parameters = args.config[1:]
         if os.path.exists(config_id):
+            config_id = os.path.abspath(config_id)
             logger.info("Reading configuration from local file\n    {}".format(config_id))
             upstream_config = {'type':'local',
                                'path':os.path.abspath(config_id),
-- 
2.47.3



             reply	other threads:[~2026-03-05 20:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-05 20:09 Alexander Kanavin [this message]
2026-03-05 20:09 ` [PATCH 2/2] bitbake-setup: correctly determine latest revision in status/update when it is fixed to a commit id Alexander Kanavin
     [not found] ` <189A0AE65037F048.1967085@lists.openembedded.org>
2026-03-08 14:16   ` [bitbake-devel] " Alexander Kanavin

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=20260305200937.221484-1-alex.kanavin@gmail.com \
    --to=alex.kanavin@gmail.com \
    --cc=alex@linutronix.de \
    --cc=bitbake-devel@lists.openembedded.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