From: Tom Zanussi <tom.zanussi@...>

This is a fix for Yocto bug #1235.

The following changes since commit 92fc07a5f1b98779806cdcc2341487ff5ea5a238:
Dexuan Cui (1):
emenlow: fix some .bbappend files' name: poky -> core, etc.

are available in the git repository at:

git://git.yoctoproject.org/meta-intel.git tzanussi/bug-1235
http://git.yoctoproject.org/cgit.cgi/meta-intel/log/?h=tzanussi/bug-1235

Tom Zanussi (1):
meta-emenlow: fix glx bug

.../libdrm-poulsbo/libdrm-poulsbo_2.3.0.bb | 6 +++++-
.../recipes-graphics/xpsb-glx/xpsb-glx_0.18.bb | 3 ++-
2 files changed, 7 insertions(+), 2 deletions(-)

Robert,

I know that and will work towards that end as well. There are a lot of holdover things in our docs.

Thanks,
Scott

On Thu, 14 Jul 2011, Rifenbark, Scott M wrote:

Agreed that BitBake is the correct spelling. I will be sure to make
a sweep through our Yocto manuals and make sure that when we are
referring to the tool and not indicating the command they say
"BitBake".

and while you're at it, i was once lectured sternly that the proper
spelling is "Git" when talking about the tool and "git" when referring
to the actual command. never "GIT". at least that what i was told.
do with that what you wish.

rday

p.s. since i am, at this very moment, immersed in an XML publishing
toolchain, i will probably have some thoughts on docbook markup in the
near future. stay tuned ...

On Wed, 2011-07-13 at 07:43 -0400, Robert P. J. Day wrote:

Signed-off-by: Robert P. J. Day <rpjday@...>

---

i'm hoping the following is correct -- it's just user help output so
it's not fatal but it should still be correct.

diff --git a/scripts/oe-setup-builddir b/scripts/oe-setup-builddir
index bc4962a..d278c24 100755
--- a/scripts/oe-setup-builddir
+++ b/scripts/oe-setup-builddir
@@ -118,7 +118,7 @@ Common targets are:
core-image-sato
meta-toolchain
meta-toolchain-sdk
- adt-install
+ adt-installer
meta-ide-support

You can also run generated qemu images with a command like 'runqemu qemux86'

Merged to master, thanks.

Richard

Agreed that BitBake is the correct spelling. I will be sure to make a sweep through our Yocto manuals and make sure that when we are referring to the tool and not indicating the command they say "BitBake".

Thanks,
ScottR

On 07/14/11 09:40, Koen Kooi wrote:

Op 14 jul 2011, om 15:13 heeft Bruce Ashfield het volgende geschreven:

On 07/14/11 09:05, Kumar Gala wrote:

Is there a list of which IMAGE_FSTYPES are supported. I didn't see anything in the docs. Looking to see if a u-boot 'mkimage' wrapped set of images is supported or not.

I'm not 100% where the list is, but I can confirm that
uImages are supported and work nicely. Assuming that
you are talking about the common use case, and not something
more exotic :)

I think he means partitioned uimages where you have a kernel + initrd in a single uimage. We don't support that *yet*, but all the needed blocks are there. And we finally get a usecase for having the loadadresses in the machine.conf files :)

Yah, that's what I wondered as well. I've done this locally,
but nothing out of the box .. so I had nagging doubts!

Cheers,

Bruce

On Thu, 2011-07-14 at 08:06 -0500, Kumar Gala wrote:

On Jul 12, 2011, at 3:43 AM, Richard Purdie wrote:

On Mon, 2011-07-11 at 10:00 -0700, Turner Randy wrote:

Hello list,

Is there a interactive menu-based configuration for yocto/poky builds
similar to that provided in Buildroot? Or is someone working on this?

At present there is not any interactive menu based configuration but
there is work ongoing on a UI called hob which allows you to select
packages and construct images of those packages so its a graphical front
end to the system.

We're also in the process of starting to better markup configuration
variables in the metadata so that writing some kind of menu based
configuration system would be easier in the future.

We're certainly open to any help in those areas too!

Cheers,

Richard

Are there any docs for hob at this point?

Not specifically. "bitbake -u hob" should let you see where things are
at. Please keep in mind that its under active development at the moment
and can be considered "alpha" quality but feedback is welcome.

Cheers,

Richard

Op 14 jul 2011, om 15:13 heeft Bruce Ashfield het volgende geschreven:

On 07/14/11 09:05, Kumar Gala wrote:

Is there a list of which IMAGE_FSTYPES are supported. I didn't see anything in the docs. Looking to see if a u-boot 'mkimage' wrapped set of images is supported or not.

I'm not 100% where the list is, but I can confirm that
uImages are supported and work nicely. Assuming that
you are talking about the common use case, and not something
more exotic :)

I think he means partitioned uimages where you have a kernel + initrd in a single uimage. We don't support that *yet*, but all the needed blocks are there. And we finally get a usecase for having the loadadresses in the machine.conf files :)

On 07/14/11 09:05, Kumar Gala wrote:

Is there a list of which IMAGE_FSTYPES are supported. I didn't see anything in the docs. Looking to see if a u-boot 'mkimage' wrapped set of images is supported or not.

I'm not 100% where the list is, but I can confirm that
uImages are supported and work nicely. Assuming that
you are talking about the common use case, and not something
more exotic :)

Cheers,

Bruce

- k
_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto

On Jul 12, 2011, at 3:43 AM, Richard Purdie wrote:

On Mon, 2011-07-11 at 10:00 -0700, Turner Randy wrote:

Hello list,

Is there a interactive menu-based configuration for yocto/poky builds
similar to that provided in Buildroot? Or is someone working on this?

At present there is not any interactive menu based configuration but
there is work ongoing on a UI called hob which allows you to select
packages and construct images of those packages so its a graphical front
end to the system.

We're also in the process of starting to better markup configuration
variables in the metadata so that writing some kind of menu based
configuration system would be easier in the future.

We're certainly open to any help in those areas too!

Cheers,

Richard

Are there any docs for hob at this point?

- k

Is there a list of which IMAGE_FSTYPES are supported. I didn't see anything in the docs. Looking to see if a u-boot 'mkimage' wrapped set of images is supported or not.

- k

On Thu, 2011-07-14 at 05:46 -0400, Robert P. J. Day wrote:

On Wed, 13 Jul 2011, Darren Hart wrote:

On 07/13/2011 03:48 PM, Joshua Lock wrote:

On Wed, 2011-07-13 at 06:57 -0400, Robert P. J. Day wrote:

just perusing the documentation in my typically pedantic fashion and
a couple questions about style. first, is the proper spelling
"Bitbake" or "BitBake" since the doc source seems to bounce back and
forth and it really should be consistent.

I believe it's the latter, at least that's what I've always use.

Agreed:

The man page:
BitBake - simple tool for the execution of tasks

The user manual:
BitBake User Manual

Those seem like the two lines of documentation that are most likely to
be correct :-) So unless Richard or Chris pipe up, I'd go with BitBake.

i thought as much, i'm going with that. not high on any list of
priorities but while i'm perusing the docs, i might as well make notes
of what can change, and submit patches for the more obvious stuff.

are the small changes i've posted here in acceptable format? do
they get ACKed at some point so i can verify they were accepted?

The pieces in poky's documentation directory are part of the yocto-docs
repo which is maintained by Scott (cc'd). Scott is a tech writer rather
than a developer and loves git, er, I mean we might need to help him get
the patches in ;-). Please do send them and we'll figure that bit out
though and will send an acknowledgement when they're merged.

Cheers,

Richard

On Wed, 13 Jul 2011, Darren Hart wrote:

On 07/13/2011 03:48 PM, Joshua Lock wrote:

On Wed, 2011-07-13 at 06:57 -0400, Robert P. J. Day wrote:

just perusing the documentation in my typically pedantic fashion and
a couple questions about style. first, is the proper spelling
"Bitbake" or "BitBake" since the doc source seems to bounce back and
forth and it really should be consistent.

I believe it's the latter, at least that's what I've always use.

Agreed:

The man page:
BitBake - simple tool for the execution of tasks

The user manual:
BitBake User Manual

Those seem like the two lines of documentation that are most likely to
be correct :-) So unless Richard or Chris pipe up, I'd go with BitBake.

i thought as much, i'm going with that. not high on any list of
priorities but while i'm perusing the docs, i might as well make notes
of what can change, and submit patches for the more obvious stuff.

are the small changes i've posted here in acceptable format? do
they get ACKed at some point so i can verify they were accepted?

rday

--

========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================

On Wed, 2011-07-13 at 06:57 -0400, Robert P. J. Day wrote:

just perusing the documentation in my typically pedantic fashion and
a couple questions about style. first, is the proper spelling
"Bitbake" or "BitBake" since the doc source seems to bounce back and
forth and it really should be consistent.

and second, this just doesn't seem right as semantic docbook markup:

"When the <filename>bitbake</filename> command completes ..."

in that context, bitbake is not a filename, it's "userinput". is
there a reason all user input like that is marked up as "filename"?

I guess it could have been so certain parts appeared in bold but I
suspect there isn't a good reason.

Cheers,

Richard

On Wed, 2011-07-13 at 20:28 -0700, Darren Hart wrote:

On 07/13/2011 03:48 PM, Joshua Lock wrote:

On Wed, 2011-07-13 at 06:57 -0400, Robert P. J. Day wrote:

just perusing the documentation in my typically pedantic fashion and
a couple questions about style. first, is the proper spelling
"Bitbake" or "BitBake" since the doc source seems to bounce back and
forth and it really should be consistent.

I believe it's the latter, at least that's what I've always use.

Agreed:

The man page:
BitBake - simple tool for the execution of tasks

The user manual:
BitBake User Manual

Those seem like the two lines of documentation that are most likely to
be correct :-) So unless Richard or Chris pipe up, I'd go with BitBake.

I think we've been leaning towards BitBake for a while.

Cheers,

Richard

On 07/13/2011 03:48 PM, Joshua Lock wrote:

On Wed, 2011-07-13 at 06:57 -0400, Robert P. J. Day wrote:

just perusing the documentation in my typically pedantic fashion and
a couple questions about style. first, is the proper spelling
"Bitbake" or "BitBake" since the doc source seems to bounce back and
forth and it really should be consistent.

I believe it's the latter, at least that's what I've always use.

Agreed:

The man page:
BitBake - simple tool for the execution of tasks

The user manual:
BitBake User Manual

Those seem like the two lines of documentation that are most likely to
be correct :-) So unless Richard or Chris pipe up, I'd go with BitBake.

--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel

new version

diff --git a/oe-init-build-env b/oe-init-build-env
index 77332a7..0fe1b5e 100755
--- a/oe-init-build-env
+++ b/oe-init-build-env
@@ -39,6 +39,35 @@ else
$OEROOT/scripts/oe-setup-builddir
unset OEROOT
unset BBPATH
+
+ # find the python 2.x, if the default python is not.
+ # NOTE:
+ # the 'python -V' need redirect to stdout
+ # once we can ensure every distribution has 'python2' (currently,
except
+ # ubuntu), we should change bitbake's shebang to '/usr/bin/env
python2',
+ # and remove this patch.
+ # precondition:
+ # $BUILDDIR is not NULL, but I doubt when it will be NULL.
+ # user have not made the file $BUILDDIR/python by himself.
+ if [ -z "`/usr/bin/env python -V 2>&1|grep '^Python 2\.'`" ]; then
+ echo "WARNING: your default python is not 2.x, so autodetect..."
+ PYTHON2_BIN=""
+ for PY_BIN in `find /{usr/,}bin -regex '.*/python\(\|2\|2\.[0-9]*
\)'`; do
+ if [ -n "`$PY_BIN -V 2>&1|grep '^Python 2\.'`" ]; then
+ PYTHON2_BIN=$PY_BIN
+ break
+ fi
+ done
+ if [ -n "$PYTHON2_BIN" ]; then
+ ln -sf $PY_BIN $BUILDDIR/python
+ export PATH="$BUILDDIR:$PATH"
+ echo "WARNING: poky will use '$PY_BIN' to execute python
code."
+ else
+ echo "ERROR: poky can't find python 2.x."
+ fi
+ unset PYTHON2_BIN
+ fi
+
[ -n "$BUILDDIR" ] && cd $BUILDDIR
fi

--
倪庆亮
TEL: 13588371863
E-MAIL: niqingliang@...
BLOG: http://niqingliang2003.wordpress.com

You are right, I will fix it.

--
倪庆亮
TEL: 13588371863
E-MAIL: niqingliang@...
BLOG: http://niqingliang2003.wordpress.com

On Wed, 2011-07-13 at 06:57 -0400, Robert P. J. Day wrote:

just perusing the documentation in my typically pedantic fashion and
a couple questions about style. first, is the proper spelling
"Bitbake" or "BitBake" since the doc source seems to bounce back and
forth and it really should be consistent.

I believe it's the latter, at least that's what I've always use.

Joshua
--
Joshua Lock
Yocto Project "Johannes factotum"
Intel Open Source Technology Centre