I have inserted the Poky image in the front matter again because the
book is a Poky Guide.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
The image file was in the same directory as the main reference manual
files. So I moved the file into subdirectory "Figures" with other
figures.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
I could not get the Yocto Project logo to appear correctly in the book
after the title. I also decided that since Poky is by no means
going away that this book should have that image associated with it
as it is the Poky Reference Manual.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
When scaled to fit the page the picture had a black vertical line
artifact to the right. I snipped out the image a little tigher to
eliminate this line.
I also incorporated Dirk's comments tightening up the sequence of
example commands to do the build. I incorporated Fedora 14 note
and addition of the BB_NUMBER_THREADS and PARALLEL_MAKE variables.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
The fetcher has special handling for file:// mirror urls, being efficient and
just providing an updated path. Unfortunately the sstate fetching code wasn't
able to handle this. This patch detects this and injects a symlink to ensure
everything works. It also fixes some datastore references to be correct and
ensures the sstate download directory exists if it doesn't already.
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
If sstate was used to accelerate a build, the pseudo directory might not have
been created leading to subsequent task failures.
Also, sstate packages were not being installed under pseudo context meaning
file permissions could have been lost.
Fix these problems by creating a FAKEROOTDIRS variable which bitbake ensures
exists before running tasks and running the appropriate setscene tasks under
fakeroot context.
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
If a sstate package exists for the package task but not for the rpm packaging
task, the output from the package task will be used. The directory pointed
to by dvar will not exist under this scenario.
Since the directory is never used by the packaging process remove the
check, substituting the pkgd variable which is always present and used.
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
The message "WARNING: Function do_build doesn't exist" doesn't look professional,
so fix the underlying problem even if this warning is harmless.
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
When installing a sstate package, directories tracked by plaindirs were being installed
to the incorrect location. With the current implementation this was limited to
the do_package task.
This patch ensures plaindirs tracked files are created in the correct location, fixing
the bug where these files would go missing.
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
This is used to fix the following build failure:
checking for oggpackB_read... no
| configure: error: newer libogg version (1.1 or later) required
Signed-off-by: Dexuan Cui <dexuan.cui@intel.com>
The link to openembedded was used to reference Linux distributions supporting
Yocto Project. The link has been removed and replaced with more generic
text so as to not have to link to openembedded. Text used is
"A Host system running a supported Linux distribution (i.e. recent releases
of Fedora, OpenSUSE, Debian, and Ubuntu)."
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
The example commands that build an image were updated to reflect the
real 4.0 release. I updated the paragraph after the example commands
to refer to the new release used in the command examples.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
1) Wording change based on Darren's input of making Linux kernel sound like the only open source part of YL
2) Removal of the "v" option for the tar command example.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Fixes [BUGID #500]
While the tuning for the mpc8315e is 603e, the PACKAGE_EXTRA_ARCHES
was ppce300. This created a mismatch and resulted in rootfs assembly
issues due to missing locales.
We align both at 603 and can revist a better tuning in the future.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
1. Added Richard Purdie's general editing feedback to the "Welcome" and
"Introducing the Yocto Project Development Environment" sections.
2. Added Kevin Tian's feedback: 1) changed "Sudo" to "sudo", 2) reversed
the order of the sample "cd" and "source" commands since the "source" command
builds the directory structure first so changing to the directory before running
"source" made no sense, 3) removed the "bitbake qemu-native" command.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Feedback from Kevin Tian suggested that the outer box be labeled "QEMU" rather
than "Target." Also that the two inner boxes be "Set of Emulated Devices" and
"Target CPU." Final change was the use of "Yocto Project Scripts" rather than
"Yocto Linux Scripts."
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Feedback from Kevin Tian suggested "OPKG" should be lower-case.
Also, use of "zypper" instead of "YUM." I also lower-cased
"apt-get."
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
The "Using OprofileUI" section had a description of how to use a
pre-built UI and how to download and build one. Feedback from Jessica
Zhang suggested removing the instruction for using a pre-built UI.
All that remains in the first paragraph now is instruction on how
to download and build the UI.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Added section 5.1.2.2 "The Anjuta Plug-in" into the Poky Reference Manual.
This section consists of sub-sections 5.1.2.2.1 "Setting Up the Anjuta
Plug-in", 5.1.2.2.2 "Configuring the Anjuta Plug-in", and 5.1.2.2.3 "Using
the Anjuta Plug-in". This information was in the original Poky Handbook
but had been removed by me since I thought it was not going to be supported
for the 0.9 Yocto Release. It has now been restored with a note indicating
that Anjuta will not be supported post 0.9 release.
I did some general text editing in each section for readability.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
The git fetcher was failing to pull in new branches into a git
repository mirror tarball as the git fetch command being used didn't
add new remote branches.
This patch uses "git fetch --all" for fullclones to ensure any
new remote branches are cloned correctly.
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
The more we try and patch up the fetcher code, the more things break. The
code blocks in question are practically unreadable and are full of corner
cases where fetching could fail. In summary the issues noticed included:
a) Always fetching strange broken urls from the premirror for "noclone"
git repositories
b) Not creating or rewriting .md5 stamp files inconsistently
c) Always fetching git source mirror tarballs from the premirror even
if they already exist but the checkout directory does now
d) Passing "None" values to os.access() and os.path.extsts() checks under
certain circumstances
e) Not using fetched git mirror tarballs if the preexist and always
try and fetch them.
This patch rewrites the sections of code in question to be simpler and
more readable, fixing the above problems and most likely other odd
corner cases.
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
update-alternatives.bbclass assumes /usr/bin/sed if ALTERNATIVE_LINK is not
specified, however sed has changed its default installation directory to
/bin/sed. This causes below errors at the first boot of lsb image:
update-alternatives: Error: cannot register alternative sed to /usr/bin/sed
since it is already registered to /bin/sed
This fixes [BUGID #478]
Signed-off-by: Kevin Tian <kevin.tian@intel.com>
Fixes [BUGID #199]
Updating the SRCREV for wrs_meta to import a set of default
netfilter options, which can then be applied to any BSP. This
keeps the default BSP configs small, while allowing the
functionality to be available.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Fixes [BUGID #199]
To allow optional features to be enabled for a given BSP, we
need to re-enable this functionality in the kernel tools. The
following commit in that repo fixes a problem when passing
feature names:
[
commit 140693a6b0d81b7ba7175b6cfce11c6c22f81e24
Author: Bruce Ashfield <bruce.ashfield@windriver.com>
Date: Sun Oct 17 01:22:00 2010 -0400
updateme: do not expand directories
If a directory is passed to updateme, do NOT expand it to a
full path, the compilation phase will search and do this
while applying some special logic to find properly named
features.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
]
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Fixes [BUGID #199]
Although an optional feature to a base BSP, most of the machines
currently supported want/need the netfilter options. To enforce
this configuration, it is temporarily forced in the kernel
recipe itself, but can move to machine configurations in the
future.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Fixes [BUGID #199]
Reinstate the ability to specify optional/additional kernel features
when updating the tree.
This is done via the variable KERNEL_FEATURES which specifies
a list of features to be appended to the current branch and
config. These features are part of the wrs_meta branch in the
kernel repository and hence are self contained within the
kernel tree waiting to be activated. This saves multiple
branches simply to allow a machine to have many profiles.
The kernel patching/configuration phases will locate these
features and add them to the meta_series, which in turn
modifies the tree.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
