Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
To: Ross Burton <ross.burton@intel.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/2] build: don't use $B as the default cwd for functions
Date: Thu, 14 Jul 2016 13:52:33 -0500	[thread overview]
Message-ID: <12a9fa85-952e-eeed-81ee-3bda503225ce@linux.intel.com> (raw)
In-Reply-To: <1468514381-6587-2-git-send-email-ross.burton@intel.com>

this is a bitbake change so it was sent to the wrong list.

On 07/14/2016 11:39 AM, Ross Burton wrote:
> When bitbake executes a shell or Python function it can cd/chdir() into a
> directory before executing the task. If no directory is specified then the
> default of $B is used.  However $B is an OpenEmbedded variable and BitBake
> shouldn't be aware of it.
>
> To solve this change the semantics slightly so that if no directory is
> specified, the current working directory isn't changed.  There's also a sanity
> check that emits a warning if a Python task does os.chdir() without restoring
> the old path, and the previous working directory is restored.
>
> This does change semantics: whereas before a function in OE would have $B as the
> working directory unless specified, now the working directory is the top of the
> build tree.  Any breakage this causes can be solved by either adding
> do_some_task[dirs] = "${B}" or by using absolute paths in the task.
>
> [ YOCTO #4634 ]
>
> Signed-off-by: Ross Burton <ross.burton@intel.com>
> ---
>   bitbake/lib/bb/build.py | 23 +++++++++++++++++------
>   1 file changed, 17 insertions(+), 6 deletions(-)
>
> diff --git a/bitbake/lib/bb/build.py b/bitbake/lib/bb/build.py
> index 4fb2a77..4f01d66 100644
> --- a/bitbake/lib/bb/build.py
> +++ b/bitbake/lib/bb/build.py
> @@ -188,6 +188,11 @@ class LogTee(object):
>   def exec_func(func, d, dirs = None, pythonexception=False):
>       """Execute a BB 'function'"""
>   
> +    try:
> +        oldcwd = os.getcwd()
> +    except:
> +        oldcwd = None
> +
>       body = d.getVar(func, False)
>       if not body:
>           if body is None:
> @@ -211,9 +216,7 @@ def exec_func(func, d, dirs = None, pythonexception=False):
>               bb.utils.mkdirhier(adir)
>           adir = dirs[-1]
>       else:
> -        adir = d.getVar('B', True)
> -        bb.utils.mkdirhier(adir)
> -
> +        adir = None
>       ispython = flags.get('python')
>   
>       lockflag = flags.get('lockfiles')
> @@ -257,6 +260,13 @@ def exec_func(func, d, dirs = None, pythonexception=False):
>           else:
>               exec_func_shell(func, d, runfile, cwd=adir)
>   
> +    if oldcwd and os.getcwd() != oldcwd:
> +        try:
> +            bb.warn("Task %s changed cwd to %s" % (func, os.getcwd()))
> +            os.chdir(oldcwd)
> +        except:
> +            pass
> +
>   _functionfmt = """
>   {function}(d)
>   """
> @@ -272,7 +282,8 @@ def exec_func_python(func, d, runfile, cwd=None, pythonexception=False):
>       if cwd:
>           try:
>               olddir = os.getcwd()
> -        except OSError:
> +        except OSError as e:
> +            bb.warn("%s: Cannot get cwd: %s" % (func, e))
>               olddir = None
>           os.chdir(cwd)
>   
> @@ -298,8 +309,8 @@ def exec_func_python(func, d, runfile, cwd=None, pythonexception=False):
>           if cwd and olddir:
>               try:
>                   os.chdir(olddir)
> -            except OSError:
> -                pass
> +            except OSError as e:
> +                bb.warn("%s: Cannot restore cwd %s: %s" % (func, olddir, e))
>   
>   def shell_trap_code():
>       return '''#!/bin/sh\n



  reply	other threads:[~2016-07-14 18:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-14 16:39 [PATCH 1/2] classes/license.bbclass: don't set [dirs] and [cleandirs] Ross Burton
2016-07-14 16:39 ` [PATCH 2/2] build: don't use $B as the default cwd for functions Ross Burton
2016-07-14 18:52   ` Leonardo Sandoval [this message]
2016-07-14 18:56     ` Burton, Ross

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=12a9fa85-952e-eeed-81ee-3bda503225ce@linux.intel.com \
    --to=leonardo.sandoval.gonzalez@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.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