enembedded, so if my
contribution doesn't meet OE expectations, I won't object to any criticism
:)
Best regards,
Marcus
On Wed, Sep 23, 2015 at 11:06 AM, Marcus Müller
wrote:
> Hello Lee,
>
> wow, thanks for clearing testing this; actually, to trigger my personal
> need for a patch,
Hello Lee,
wow, thanks for clearing testing this; actually, to trigger my personal
need for a patch, variant # A was used.
Cheers,
Marcus
On 22.09.2015 22:25, Lee Nipper wrote:
> On Tue, Sep 22, 2015 at 1:45 PM, Marcus Müller
> mailto:marcus.muel...@ettus.com>> wrote:
>
>
Hello,
> If I understand correctly it allows a user prepared $TEMPLATECONF
> directory
> to be used by oe-setup-builddir.
Indeed; the point is that oe-setup-builddir was definitely meant to be
used with a TEMPLATECONF set by the user; in bash, the TEMPLATECONF
local variable is automatically passed
---
oe-init-build-env | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/oe-init-build-env b/oe-init-build-env
index 6fee5f7..b7e2918 100755
--- a/oe-init-build-env
+++ b/oe-init-build-env
@@ -45,7 +45,7 @@ fi
OEROOT=`readlink -f "$OEROOT"`
export OEROOT
. $OEROOT/scripts/oe-bu
