Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/7] bitbake.conf: use weak assignment for BB_CONSOLELOG
Date: Fri, 24 Feb 2012 01:47:51 +0100	[thread overview]
Message-ID: <20120224004751.GD3769@jama.jama.net> (raw)
In-Reply-To: <1330044007.25226.16.camel@ted>

[-- Attachment #1: Type: text/plain, Size: 1741 bytes --]

On Fri, Feb 24, 2012 at 12:40:07AM +0000, Richard Purdie wrote:
> On Thu, 2012-02-23 at 11:43 +0100, Martin Jansa wrote:
> > * some people prefer subdirectory like /cooker/.log
> 
> I think we should probably change that to the default actually...

But that would need to implement that directory creation if it doesn't
exist. (I have to create it manually for each build from scratch). And
because it's in bitbake then we can make this default only after
increasing required bitbake version (which we should anyway for latest
sstate changes..).

Cheers,

> Cheers,
> 
> Richard
> 
> > Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
> > ---
> >  meta/conf/bitbake.conf |    3 ++-
> >  1 files changed, 2 insertions(+), 1 deletions(-)
> > 
> > diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
> > index 90e5f7a..869b409 100644
> > --- a/meta/conf/bitbake.conf
> > +++ b/meta/conf/bitbake.conf
> > @@ -723,7 +723,8 @@ DISTRO[unexport] = "1"
> >  # Used by canadian-cross to handle string conversions on TARGET_ARCH where needed
> >  TRANSLATED_TARGET_ARCH ??= "${@d.getVar('TARGET_ARCH', True).replace("_", "-")}"
> >  
> > -BB_CONSOLELOG = "${TMPDIR}/cooker.log.${DATETIME}"
> > +# Complete output from bitbake, if you're changing it, make sure to use existing directory
> > +BB_CONSOLELOG ?= "${TMPDIR}/cooker.log.${DATETIME}"
> >  
> >  # Setup our default hash policy
> >  BB_SIGNATURE_HANDLER ?= "OEBasic"
> 
> 
> 
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

  reply	other threads:[~2012-02-24  0:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-23 10:42 [PATCH 0/7] Pending patches Martin Jansa
2012-02-23 10:43 ` [PATCH 1/7] wireless-tools: remove ldconfig call from install-libs Martin Jansa
2012-02-23 10:43 ` [PATCH 2/7] bitbake.conf: use weak assignment for BB_CONSOLELOG Martin Jansa
2012-02-24  0:40   ` Richard Purdie
2012-02-24  0:47     ` Martin Jansa [this message]
2012-02-23 10:43 ` [PATCH 3/7] sstatesig: add pointercal-xinput to excluded machine specific configs Martin Jansa
2012-02-24  0:36   ` Saul Wold
2012-02-24  0:49     ` Martin Jansa
2012-02-23 10:43 ` [PATCH 4/7] python: add Makefile to SSTATE_SCAN_FILES Martin Jansa
2012-02-23 10:43 ` [PATCH 5/7] bitbake.conf: introduce SDK_NAME_PREFIX and NATIVESDK_* variables Martin Jansa
2012-02-23 10:43 ` [PATCH 6/7] gdb-cross-canadian: build gdb with python support Martin Jansa
2012-02-23 10:43 ` [PATCH 7/7] gdb-cross-canadian: use NATIVESDK paths as it happens to be here Martin Jansa

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=20120224004751.GD3769@jama.jama.net \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-core@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