Op 21 jul. 2011, om 07:50 heeft Ke Liping het volgende geschreven:
> From: Liping Ke
>
> Since Hob only needes package dependency information, we can
> create a new version of package information retrieving methods,
> remove task dependency information, so that we can greatly
> reduce data load
Richard,
I'm working on getting a ppc64 build going and looking close to having that
done. I was wondering what the state of multilib support was as I'd really
like to have that functional for the ppc64 system.
Think this will also be useful to flush out any multilib issues by having
another
On 07/20/2011 10:10 PM, Kumar Gala wrote:
For a new bsp/target what's the best config choice to try and build all of
yocto? Is it core-image-sato?
- k
bitbake world should build all of the available packages that aren't
explicitly excluded due to machine incompatibilities. It doesn't
gener
ignore not just build/* but any build*/* cases.
Signed-off-by: Kumar Gala
---
.gitignore | 12 ++--
1 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/.gitignore b/.gitignore
index b13086d..d44e729 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,11 +1,11 @@
*.pyc
*.pyo
-bu
On Thu, Jul 21, 2011 at 8:29 AM, Scott Garman wrote:
> bitbake world should build all of the available packages that aren't
> explicitly excluded due to machine incompatibilities. It doesn't generate a
> final image though, just all of the output packages.
Is there an easy way to remove a specifi
On Thu, 21 Jul 2011, McClintock Matthew-B29882 wrote:
> On Thu, Jul 21, 2011 at 8:29 AM, Scott Garman
> wrote:
> > bitbake world should build all of the available packages that aren't
> > explicitly excluded due to machine incompatibilities. It doesn't generate a
> > final image though, just all
On Thu, 2011-07-21 at 16:32 +, McClintock Matthew-B29882 wrote:
> On Thu, Jul 21, 2011 at 8:29 AM, Scott Garman
> wrote:
> > bitbake world should build all of the available packages that aren't
> > explicitly excluded due to machine incompatibilities. It doesn't generate a
> > final image tho
On 07/21/2011 09:32 AM, McClintock Matthew-B29882 wrote:
On Thu, Jul 21, 2011 at 8:29 AM, Scott Garman wrote:
bitbake world should build all of the available packages that aren't
explicitly excluded due to machine incompatibilities. It doesn't generate a
final image though, just all of the outp
On Thu, 21 Jul 2011, Scott Garman wrote:
> On 07/21/2011 09:32 AM, McClintock Matthew-B29882 wrote:
> > On Thu, Jul 21, 2011 at 8:29 AM, Scott Garman
> > wrote:
> > > bitbake world should build all of the available packages that aren't
> > > explicitly excluded due to machine incompatibilities. It
On 07/21/2011 10:08 AM, Robert P. J. Day wrote:
On Thu, 21 Jul 2011, Scott Garman wrote:
On 07/21/2011 09:32 AM, McClintock Matthew-B29882 wrote:
On Thu, Jul 21, 2011 at 8:29 AM, Scott Garman
wrote:
bitbake world should build all of the available packages that aren't
explicitly excluded due t
On Thu, 2011-07-21 at 11:04 +0200, Koen Kooi wrote:
> Op 21 jul. 2011, om 07:50 heeft Ke Liping het volgende geschreven:
>
> > From: Liping Ke
> >
> > Since Hob only needes package dependency information, we can
> > create a new version of package information retrieving methods,
> > remove task
Op 21 jul. 2011, om 18:43 heeft Scott Garman het volgende geschreven:
> On 07/21/2011 09:32 AM, McClintock Matthew-B29882 wrote:
>> On Thu, Jul 21, 2011 at 8:29 AM, Scott Garman
>> wrote:
>>> bitbake world should build all of the available packages that aren't
>>> explicitly excluded due to mac
On Thu, 2011-07-21 at 13:39 +0800, Ke, Liping wrote:
> Hi, Josh
>
> Yes, definitely this patch's importance is much less than the previous one.
> But if more users are using hob, the cache would be very useful.
> Because when using UI, users tend to switch between all combination of menu
> frequ
On Tue, 2011-07-19 at 03:15 -0700, Andre Haupt wrote:
> Hi all,
>
> I am new to Yocto and to Distro work in general.
>
> I want to use Yocto on the Kontron nanoETXexpressTT boards.
> (http://de.kontron.com/products/computeronmodules/com+express/com+express+ultra/nanoetxexpresstt.html)
>
> These
Hi All,
In today's bug triage meeting, we noticed there're total 564 bugs that are in
"Resolved" status. The process is once a bug is in Resolved status, the
original reporter of the bug should verify the resolution, either a valid fix
or acceptable reason and mark the bug as "Verified". So
15 matches
Mail list logo