Changed the email address for Richard Purdie in the author title
page to richard.purdie@linuxfoundation.org.
(From OE-Core rev: 86e355f489437c4d20a717617d203a8a5aa1371a)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
[BUGID# 695] - I updated the title to use a less bold and intrusive
font and one that is still common for systems. Also removed the
"s" in the title so it now reads "Board Support Package (BSP)
Developer's Guide." I also put a better looking Yocto logo in.
Once this commit is merged bug #695 can be marked resolved.
(From OE-Core rev: f6d9338bf98f2f6791231a5ff74142833ae1363e)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
[BUGID# 553] - In the 'BSP Click-Through Licensing Procedure'
section, which is shared between the BSP Guide and the Poky
Reference Manual, there were three links to 'pokylinux.org'
sites. These links were intended to help a user get a license
for encumbered BSPs. However, the links never did work. The
section also had some wording that described a propsed naming
convention for BSP tarballs that were encumbered and non-encumbered.
The naming convention is a good idea but has not been followed
so far.
I removed the links and replaced them with general instructions
on how to get through the licensing situation. Also removed the
hard-line naming rules and replaces with a more general explanation
of how we are naming BSP (e.g. Crown Bay).
(From OE-Core rev: 4c2dcb376b4be0778cab97138fefdb8a27a0e708)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
[BUGID# 553] - In appendix I in the Contributions section (I.6) there is
mention of a Poky contributions tree and the URL
git://git.pokylinux.org/poky-contrib.git is given. I changed this
URL to git://git.yoctoproject.org/poky-contrib.git.
This is a partial fix for but 553.
(From OE-Core rev: 982ff35cad0276eb74eae170d21ead0edd3a1072)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I added text after the bulleted items "The Poky website" and "BitBake Uer Manual."
These were blank and it was not consistent with the rest of the list.
(From OE-Core rev: a820c07796dc478154b7e5ee4e590a425b981e8a)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
[BUGID# 553] - In the "Bugtracker" section (appendix I - I.2) there is
a reference to the bugtracker. The text shows just the string
"bug tracker" but the hidden URL was http://bugzilla.pokylinux.org.
I updated the text to say to report problems by using the Bugzilla
application and then gave the URL http://bugzilla.yoctoproject.org
as the reference.
This is a partial fix for bug 553.
(From OE-Core rev: 94f7132e56699c9f9f8dc43d6a1271294c5cbe26)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
[BUGID# 553] - In the FAQ appendix item H.12 there was a reference
to http://pokylinux.org/sources/* in the question portion. The
reference should really be http://autobuilder.yoctoproject.org/sources/*.
I made the change.
This is a partial fix for bug 553.
(From OE-Core rev: fb56ac6021fe09cb386c168f3fe0b11e04214972)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
[BUGID# 553] - In "The Anjuta Plug-in" section (5.1.2.2) there was
an URL to the source for the Anjuta Plug-in. The URL had the
pokylinux.org string in it and pointed to the old area. I changed
the URL to http://git.yoctoproject.org and directed the user to
look under IDE Plugins.
This is a partial fix to bug 553.
(From OE-Core rev: 0a1d8f48c8a2120ba57017e1fcf270c677486266)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
[BUGID# 553] - In "The Eclipse Plug-in" section (5.1.2.1) there were two
URLs referencing the place to get the Eclipse plug-in. One specified
the URL to put into the HTTP:// field in the Eclipse IDE when installing
the software. This URL was incorrect. I replaced it with the correct
URL, which was http://www.yoctoproject.org/downloads/eclipse-plugin/.
The second URL that was fixed was referencing the source code for the
plug-in. It had the old pokylinux.org string. I changed it to
http://git.yoctoproject.org.
These fixes partially address bug 553.
(From OE-Core rev: 6871c913e0dae338708f74dbbe94cfe2fc498018)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
[BUGID# 553] - In the Development Checkouts section (1.5.3) there was a
reference to our git repository located at git://git.pokylinux.org/poky.git.
I changed this to git://git.yoctoproject.org/poky.git. This is a
partial fix to Bug 553.
(From OE-Core rev: fe4ed51c121b8f1445a0999e411c54270321e025)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
[BUGID# 553] - In the Releases section (1.5.1) there was an URL to
http://pokylinux.org/releases. This URL was old and I replaced it
with http://yoctoproject.org/downloads/poky. This partially fixes
bug 553.
(From OE-Core rev: e66d4b53c773d76f2f05c574132796e2fdcf6ebd)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
[BUGID# 553] - In the Development Checkouts section (1.5.3)
there is a reference to
http://git.pokylinux.org/. This URL resolves to an older looking
source area. I determined that the URL
http://git.yoctoproject.org/ resolves to the newer Yocto source
web interface so I changed the URL to that.
This is a partial fix
to Bug 553.
(From OE-Core rev: 18f0124db5c10ea23698ca0c469d4dfde89adf43)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
[BUGID# 553] - In the nightly build section (1.5.2) there is a reference to
http://autobuilder.pokylinux.org/. This URL resolves to an autobuilder
page that has a bunch of pokylinux links. I determined that the URL
http://autobuilder.yoctoproject.org/ also resolves to the autobuilder
page so I updated the URL to use the YP link. This is a partial fix
to Bug 553.
(From OE-Core rev: b1c7055dead4badd14872105c49466cbf86d3b54)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added command 'ls meta*/recipes*/images/*.bb' as the command to see the
supported images. Also added poky-image-lsb as an image and noted
that poky-image-sdk has becom poky-image-sato-dev.
These fixes are in response to alpha testing for release 1.0 Yocto.
(From OE-Core rev: aa2bdf7c26486961e040c95f17789064968eb9c0)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added "Copyright 2010-2011 Linux Foundation" under the title. For
now this will have to do. Once we get the converted website up I
would like to see all manuals displayed as HTML files within the
context of the site layout. At that point we can have a copyright
and trademark stuff in a persistent footer.
[BUGID #696]
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
As part of the fix for #628 I added a new question to the FAQ for use
of Poky when you do not have Python 2.6.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Part of the fix for Bug 628 is to add a note that bitbake requires
python 2.6. I added this note before the example bitbake command
that builds an image. I also added a linked reference to the Poky
Reference Manual and mentioned the FAQ appendix. There will be more
information about the python requirement in the FAQ.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
I made some updates to the 3.4.4 section according to Bruce Ashfield's
feedback. I also added a new section 3.4.5 (Creating a BSP Based on an
Existing Similar BSP Without a Local Kernel Repository).
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Added text after the sample bbappend file stating that the user needs
to update the KSRC assignment statement and also remove its comment.
Also they have to remove the comment from the SRC_URI line.
Changed the bitbake command in step 4 to use the linux-yocto-stable
file rather than the linux-yocto file.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Changed 'linux-yocto_git.bbappend' to 'linux-yocto-stable_git.bbappend'
in step 3 just before the code example. This makes the code consistent
with the rest of the example supporting the 2.6.34 kernel.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Step one states that the linux-yocto_git.bbappend file is left. This
file is associated with distro 2.6.37 kernel and the rest of the
example is associated with the 2.6.34 kernel. So, I changed the
step to indicate that the directory is left with a linux-yocto-stable_git.bbappend
file.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
These changes implemented Bruce Ashfield's next round of changes to the
section 4.3.3 example.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
In section 4.3.3 step 2 there was a directory 'build/donf/bblayers.conf'.
I fixed the typo to 'build/conf/bblayers.conf'.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
The example used to show how to condense and merge two BSPs into a second
SCM used a non-existant machine (cav_ebt5800-standard). I replaced this
machine with 'common_pc_64-standard, which is a real machine.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
[BUGID# 597] - After talking with Bruce Ashfield the kernel documentation
needs to support the 2.6.34 disribution. So, the 'common-pc-standard'
strings need to be changed back to 'common_pc-standard'. This fix restores
them.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
[BUGID# 631] - I added a tip in the section where we show a sample build.
The tip says that you can add 'INHERIT += "rm_work"' to the local.conf file
to help conserve disk space during a build.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Discovered that the manual was not making correctly due to a stray
</literallayout> statement. I removed this statement and the manual
now builds.
Signed-off-by: Scott Rifenbark <scott@scott-desktop.(none)>
Depending on the architecture you are booting and the profile of the
filesystem image QEMU might come up in a new shell, and existing shell,
have a GUI, or be in command-line mode. I added a note indicating this
behavior.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
The value for the 64-bit architecture was "x86-64" and not "x86_64".
Changed it to be correct.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
The section that introduces the using a pre-built binary section needed
more items in the list. I added text for setting up the environment
and for starting QEMU.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
The pre-built image section was one long section that naturally
broke into several areas. I inserted some sub-sections for better
organization.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
I added the exact architecture strings for each of the five supported
architectures as part of the /opt/poky/environment-setup.... commands
resulting from installing the toolchain tarballs.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Revised the manual for better grammar and more technically accurate wordings.
Worked closely with Scott Garman on the revision.
Signed-off-by: Scott Rifenbark <scott@scott-desktop.(none)>
Added the packages autoconf and automake to both the Debeian-based
host and the RPM-based host example commands. During a fresh
development host system test run I found these packages were
necessary to develop Yocto projects using Eclipse IDE.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Made several small changes:
- Added a period to three-bullet list for consistency
- grammar fix to sentence
- Added clarification for getting stuff from qemu URL
- Fixed the forms for the image and the file system image
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
There are some sections now that don't correspond one-to-one with the
standard file structure presented in section 1.1. So I am commenting them
out for now. Since I am still in the process of iterating on this
manual I don't want to just delete the information.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Section 1.1 has the example filesystem layout. The last line of the
example filesystem layout had linux-wrs. It has been changed to
linux-yocto-stable.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
I added a reference to the specific section in the kernel documentation
that describes how to create a BSP Based on an existing similar
BSP. The tools we have that create the PDF manuals from the DocBook
XML do not support cross-referencing to another PDF manual. So, I was
left with adding a clunky text-based reference to the section and a link
to the docs page on the web-site.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Added wording to indicate this directory as optional if the BSP had
special requirements for graphics support.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Found a mis-spelling that I corrected.
Also added wording to indicate this directory is optional.
Put in a note telling that defaults are set if a formfactor is
not found.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Added wording to be sure user knows to replace "bsp" and "_bsp" in the
boilerplate template example with the actual BSP name (i.e. <bsp_name>).
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
It makes more sense to have the sections that describe the various
parts of the common structure as sub-sections to that. That pulls
out the click-through licensing into a higher-level section.
This is better overall section organization.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
There are some sections now that don't correspond one-to-one with the
standard file structure presented in section 1.1. So I am commenting them
out for now. Since I am still in the process of iterating on this
manual I don't want to just delete the information.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Added some text in section 1.1 explaining that the file structure example
is an example and that the file structure of specific BSPs could differ.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Lowered the "E" for the "meta-emenlow" BSP.
Removed the "oaktrail" one, which is an Intel code name and replaced
it with "beagleboard", which is a non-Intel board.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Added information in the section about Pre-built User Binaries.
In the first paragraph I stated that this directory would contain
the Application Development Toolkit and minimal live images when the
BSP is "tarred" up and placed on the Yocto Project website.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Two lines had been earlier turned into a single sentence but the
capitalization of the second line still remained.
I switched "The" into "the".
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Inserted a note that states the BSP file structure shown is an example
only and that a given BSP could have different files.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Replaced meta-<bsp_name>/recipes-<bsp_name> with meta-<bsp_name>/recipes-bsp.
This conforms to how the BSP standard will be working.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Updated the figure to not use "preempt_rt". Now uses "preempt-rt".
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
1. Edited to incorporate new file system naming structure per Saul Wold. This
is the version I am sending him and Tom Z. to review.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Conflicts:
documentation/bsp-guide/bsp.xml
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
There was a git checkout and git push command that did not have a newline
character between the two line in a literallayout block.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
removed the ";" character that was part of the git log --pretty=oneline
command example. This fixes bug [BUGID# 588].
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Comments covered some minor points. We did remove the "Creating
a Transition Kernel Layer" section however.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Cyril submitted a patch via email form for several spelling corrections. The master docs, however, are not up-to-date with what I have on my contrib area. Many of Cyril's corrections were already addressed. A few were not and I have updated them here with this commit.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
There is inconsistent use of how BitBake is spelled. Sometimes it uses no capitalization, just a leading "B", or "BitBake". I looked at the BitBake manual and it seems that "BitBake" is the correct way to refer to it.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
I pulled the openembedded mailing list information and provided information for yocto@yoctoproject.org, yocto-announce@yoctoproject.org, and poky@yoctoproject.org. I also updated the IRC section to include both #poky and #yocto channels.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
This version represents the completed first draft with all of Bruce Ashfield's comments applied and a good scrubbing of the text.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Re-writing up to the "Export for External (Upstream) Submission" section.
I am cleaning up the English and style.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Feedback indicated by Dave suggested getting rid of this. So I commented out the text around it and modified the reminder text so it did not reference a figure.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
The make process for the kernel book now includes multiple chapters instead of a single chapter.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
This is inline with how the other docs are built. kernel-manual.xml
is called by xsltproc from the Makefile.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
I made this file similar to the bsp.xml file so that it would build into
a PDF file. It was throwing an error because of the imagedata tag
that was up front.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Code now calls a new file called kernel-manual.xml that in turn
includes the yocto-project-kernel-manual.xml file. This is in line
with how the other docs are built.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
this section is based on an email that Bruce Ashfield sent me. It replaces
what was in there in the form of sub-sections for creating a new BSP,
cloning one and bsp bootstrapping.
I needed more demarcation for these section titles. They were not visually
different enough.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
These sections were commented out after a review by Bruce Ashfield. They
need to be revisited as we continue with the 1.0 work.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
I had to rename these files because I had kernel mis-spelled when I committed
the original manual files.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
I noticed I had mis-spelled kernel for these files names after committing
the new kernel manual. I renamed the files and had to remove these two.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
This is the first draft of the Yocto Project Kernel manual. The
manual consists of two sections: concepts and a practical section that
has examples. It is based of Bruce Ashfield's kernel theory paper.
This first draft has been re-written and organized through the
concepts section. The remainder was just placed in as-is due to
time constraints for getting some kernel documentation up on the website.
The manual still needs scrubbing and organization in the latter half.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Added an entry in the glossary for INC_PR. Also updated section
"Package Revision Incrementing" to mention the use of INC_PR in conjuntion
with the PR and PV variables.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
After moving BSP Guide into its own folder for documentation I discovered
a consequence of that. There are two separate bsp.xml files now: one
in the poky-ref-manual folder and one in the bsp folder. I had done some
good cleanup work in the version in the poky-ref-manual folder. This
commit reflects a 'meld' operation where I re-sync'ed the bsp.xml
file in the bsp-guide folder to be the same (almost) as the one in the
poky-ref-manual folder. There is still one slight difference between the
two files due to one's context as a stand-alone manual and the other as
a section in a larger book.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
I am using "xxxxxx" task as the way to call out a specific task in the
text. Previously a mix of <function>xxxxxx</function> and the "xxxxxx"
methods were being used.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Because I am single-sourcing the bsp.xml file that is used both as
chapter 4 in the Poky Reference Manual and as the singe file in the BSP
Guide I removed the bsp.xml file that was local to the poky-ref-manual
folder.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
I created wording in the second paragraph of this file so that it can
fit both the context of the BSP Guide and the BSP chapter of the
Poky Reference Manual.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Because BSP chapter (bsp.xml) is identical to the single file used
in the BSP Guide (also bsp.xml but in the bsp-guide folder) I have decided
to change where the Poky Reference Manual get the bsp.xml file. This commit
causes it to get the file from the bsp-guide folder instead of an identical
but separate bsp.xml file local to the poky-ref-manual folder.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
There was a mis-matched list element in an ordered list near the end
of the chapter. I had an <orderedlist> tag matched with an </itemizedlist>
tag preventing the make.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
There was a errant tag mis-match where I had used <orderedlist> and
ended it with </itemizedlist>. This was preventing the make.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
After moving BSP Guide into its own folder for documentation I discovered
a consequence of that. There are two separate bsp.xml files now: one
in the poky-ref-manual folder and one in the bsp folder. I had done some
good cleanup work in the version in the poky-ref-manual folder. This
commit reflects a 'meld' operation where I re-sync'ed the bsp.xml
file in the bsp-guide folder to be the same (almost) as the one in the
poky-ref-manual folder. There is still one slight difference between the
two files due to one's context as a stand-alone manual and the other as
a section in a larger book.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
The xsltproc command in the Makefile now uses the XSL Customization
layer style sheet poky-ref-manual-customization.xsl for the style
sheet parameter. This method will allow for customization of the
HTML version formatting that might be unique for the manual. I have
added the new file to the file structure.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
The xsltproc command now uses the XSL Customization layer style sheet
poky-ref-manual-customization.xsl for the style sheet parameter. This
method will allow for customization of the HTML version formatting that
might be unique for the manual.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
I moved the XSLTOPTS variables to the top of the file so they will
be defined first. This is an attempt to fix the seemingly random
HTML runtime errors I am getting during the 'make html' command.
It seems to be consistently working now.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
In the Ref Images appendix there was a link to the section
"External Development Using the Poky SDK" section that did not work
due to the section id string changing. I fixed the link.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
The Extending Poky chapter was referencing a non-existent BBFILE_COLLECTIONS
glossary term. I added the term.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Added an entry for BBLAYERS in the ref-variables (glossary) appendix.
The Extending Poky chapter was referencing this variable and it did not
exist.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Removed a couple of redundant </ulink> tags.
Also indented the literallayout text by five spaces for formatting.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
I found another redundant </ulink> tag.
I removed the word sections from within a section link in a couple of places.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Added a section id to the 'welcom to poky' section that was missing.
Removed a redundant </ulink> tag that was not needed.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Because I created the file 'bsp-guide-customization.xsl' to try and eliminate odd
HTML runtime errors and to allow for customized XSL layer of formatting, it was necessary to
update the Makefile to call the new file as the XSL style sheet.
The Yocto Project Quickstart uses this technique and has no HTML build
problems.
HTML build errors seem to be eliminated so far.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Since the BSP Guide is under its own cover I thought it would be good
to have its title page not have the Poky Handbook PNG image. I created
this BSP image for use with the stand-alone BSP Guide.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
I created the file 'bsp-guide-customization.xsl' to try and eliminate odd
HTML runtime errors and to allow for customized XSL layer of formatting.
The Yocto Project Quickstart uses this technique and has no HTML build
problems.
HTML build errors seem to be eliminated so far.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
I am getting occasional errors while attempting to make the HTML version
of this manual. The error is generated from line 367 of the html.xsl
style sheet and seems to come from confusion of not finding the css
style sheet parameter. Here is the error from the shell window.
scottrif@scottrif-desktop:~/poky/documentation/bsp-guide$ make html
xsltproc --stringparam html.stylesheet style.css --stringparam chapter.autolabel 1 --stringparam section.autolabel 1 --stringparam section.label.includes.component.label 1 --xinclude -o bsp-guide.html http://docbook.sourceforge.net/release/xsl/current/xhtml/docbook.xsl bsp-guide.xml
Note: namesp. cut : stripped namespace before processing
WARNING: cannot add @xml:base to node set root element. Relative paths may not work.
Note: namesp. cut : processing stripped document
runtime error: file http://docbook.sourceforge.net/release/xsl/current/xhtml/html.xsl line 367 element choose
Variable 'generate.css.header' has not been declared.
make: *** [html] Error 10
The odd think is that running "make html" immediately again could cause the
make to be entirely successful.
So this commit involved moving the XSLTOPTS parameters to the top of the
make file and the *_URI parameter declarations to the top as well. This
takes them out of the "pdf" area of the make file and they should be
more universal. The reason I tried this is because I have no such issues
when building the yocto-project-qs HTML file.
However, even with these changes the occasional runtime error (shown above)
still occurs.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Since this manual is about BSP and not Poky as is the Poky Reference
Manual I updated the title page to include the title combined with the
Yocto Project logo. So for the background-image url in the .authorgroup
style I replaced the poky-ref-manual.png file with bsp-title.png.
Updates affect both the PDF and HTLM versions of the BSP Guide.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Since this manual is about BSP and not Poky as is the Poky Reference
Manual I updated the title page to include the title combined with the
Yocto Project logo. Updates affect both the PDF and HTLM versions
of the BSP Guide.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Since this manual is about BSP and not Poky as is the Poky Reference
Manual I updated the title page to include the title combined with the
Yocto Project logo. Updates affect both the PDF and HTLM versions
of the BSP Guide.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
I created a new sub folder to hold the BSP Guide by itself so there are
three folders now for each of the Yocto manuals: BSP Guide, quick start
and poky ref manual. The new folder for the BSP guide is 'bsp-guide'.
It contains the bsp.xml file, its own Makefile, a bsp-guide.xml file,
and its own 'Figures' directory. The 'bsp-guide.xml' file that was
in the poky reference folder was deleted.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
I completed general edits to the second chapter of the poky reference
manual. These edits went from section 2.4.5 through the end of the
chapter. They consist of text rewrites for more active voice and follow
general technical writing principles.
I completed the same types of edits in the third chapter of the manual
from the beginning through section 3.3.2.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Extensive language and consistency edits being applied to the manual.
During the 0.9 push I did not have time to make a pass through the
document.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Changed "source poky-4.0/poky-init-build-env poky-4.0-build"
to be "source poky-laverne-4.0/poky-init-build-env poky-4.0-build"
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
There was a grammatical error in the title and redundancy in the
first sentence of this section. Cleaned up the title and wording.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
I did a complete edit pass through this chapter. The manual has
not been fully edited from its original state. One critical technical
correction was corrected where the green-3.3 release was referenced.
I changed this to laverne 4.0.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
I changed the figure that goes along with building an image based on
Kevin's input. Also, removed several URLs that had 'yoctolinux' in them
along with a 'tar' command example with the same string. LF does
not want these in there.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Removed several blocks of text from section 5.1.2.1.1
"Installing and Setting up the Eclipse IDE". This text according
to Jessica was no longer needed.
Corrected a typo listing the package libsdl1.2-dev as libsdll.2-dev.
Also added the package mercurial.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Added commands to support package installation of RPM-based host systems
to the example. Input based on feedback from Dirk.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
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 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>
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>
It's no longer neccesarry to define THISDIR and FILESPATH in each bbappend
recipe. Should you need to reference extra files you should use FILESEXTRAPATHS
Signed-off-by: Joshua Lock <josh@linux.intel.com>