All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Joshua Lock <josh@linux.intel.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH 00/10] Hob - BitBake GUI
Date: Fri, 01 Jul 2011 16:47:47 +0100	[thread overview]
Message-ID: <1309535267.20015.523.camel@rex> (raw)
In-Reply-To: <cover.1309499227.git.josh@linux.intel.com>

On Thu, 2011-06-30 at 23:02 -0700, Joshua Lock wrote:
> Of course, before sending this pull request I ran some final tests and
> encountered a significant problem with the implementation approach.
> Images are built by first using the buildTargets command to build all of the
> target dependencies then creating a recipe file and using the buildFile
> command to handle the build.
> The problem is that if you have a clean build directory, perfectly reasonable
> with such a tool, the buildFile command does not handle the native
> dependencies added by the image class.
> 
> The alternative I have is to save the image files somewhere within BBPATH,
> and perhaps suggest the user create a "workspace" layer, and build them with
> buildTargets. I didn't do this because I'd rather not pollute the users file
> system without good cause. It may be the only tenable approach though.
> 
> Any suggestions here?

I think you should be able to modify the base configuration data and
just add a local directory that the image creator uses to BBPATH
yourself?

That way you should always be able to use buildTargets...

Cheers,

Richard




  parent reply	other threads:[~2011-07-01 16:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-01  6:02 [PATCH 00/10] Hob - BitBake GUI Joshua Lock
2011-07-01  6:02 ` [PATCH 01/10] ui/hob: Fixed the "build again" hang Joshua Lock
2011-07-01 15:56   ` Richard Purdie
2011-07-01  6:02 ` [PATCH 02/10] bitbake: Make bitbake server type configurable Joshua Lock
2011-07-01  6:02 ` [PATCH 03/10] command|cooker: allow generating targets tree for specified pkgs Joshua Lock
2011-07-01  6:02 ` [PATCH 04/10] cooker: add generic method to locate configuration files Joshua Lock
2011-07-01  6:02 ` [PATCH 05/10] command|cooker|event: add findConfigFilePath command Joshua Lock
2011-07-01  6:02 ` [PATCH 06/10] cooker|command|event: add new command findFilesMatchingInDir Joshua Lock
2011-07-01  6:02 ` [PATCH 07/10] bitbake: add -R option for loading configuration files after bitbake.conf Joshua Lock
2011-07-01  6:02 ` [PATCH 08/10] cooker: switch to new universe target rather than world Joshua Lock
2011-07-01  6:02 ` [PATCH 09/10] cooker: remove code duplication in non trivial functions Joshua Lock
2011-07-01  6:02 ` [PATCH 10/10] hob: re-designed interaction and implementation Joshua Lock
2011-07-01 15:47 ` Richard Purdie [this message]
2011-07-01 15:53   ` [PATCH 00/10] Hob - BitBake GUI Joshua Lock
2011-07-01 16:04 ` Richard Purdie

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=1309535267.20015.523.camel@rex \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=josh@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.