Age | Commit message (Collapse) | Author |
|
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
Using "June 2018"
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
Fixed the notes to help the user understand where to get
the correct version of the manuals for any given version
of YP.
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
Signed-off-by: Kristi Rifenbark <kristi@buzzcollectivemarketing.com>
|
|
Fixed [YOCTO #12458]
Signed-off-by: Kristi Rifenbark <kristi@buzzcollectivemarketing.com>
|
|
poky.ent - changed variables to reflect 2.2.4
mega-manual.sed - "2.2.4" for "2.2.3" string replace
<manual>.xml - Updated manual revision date for "TBD 2018"
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
Fixes [YOCTO #12467]
Changed the CentOS variable to use python34-pip
instead of python3-pip. Removed notes indicating
CentOS 6.x exceptions because this version does
not support CentOS 6.x.
Signed-off-by: Kristi Rifenbark <kristi@buzzcollectivemarketing.com>
|
|
Changed release date from November to December 2017
Signed-off-by: Kristi Rifenbark <kristi.rifenbark@gmail.com>
|
|
Poky.ent - variables changed
<manual>.xml - Updated manual revision table
mega-manual.sed - updated 2.2.2 to 2.2.3
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
Signed-off-by: Kristi Rifenbark <kristi.rifenbark@gmail.com>
|
|
is about changing "pip3" to "python3-pip" and "pexpect" to
"python3-pexpect".
Merge branch 'morty' of ssh://git.yoctoproject.org/yocto-docs into morty
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
Fixes [YOCTO #11578]
The package names "pip3" and "pexpect" do not exist for Ubuntu
and Debian. They need to be "python3-pip3" and "python3-pexpect".
I changed them in the poky.ent file and did some reformatting so
the install lines appear nice. I updated the other distributions
as well.
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
Fixes [YOCTO #11578]
The package names "pip3" and "pexpect" do not exist for Ubuntu
and Debian. They need to be "python3-pip3" and "python3-pexpect".
I changed them in the poky.ent file and did some reformatting so
the install lines appear nice. I updated the other distributions
as well.
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
Changes include:
* poky.ent - changing variables for 2.2.2
* mega-manual.sed - updated "2.2.1" to "2.2.2" for links
* *.xml - Changed all the manual revision tables to say
"June 2017" for now.
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
Fixes [YOCTO #10889]
Missing this package. Speculation is that this package was
part of the Python 2.7 stuff but not Python 3. So, adding it
clears the issue up.
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
* poky.ent - changed variables appropriately for 2.2.1
* <manual> - updated the manual revision tables to have a new
2.2.1 entry indicating a "January 2017" release
* mega-manual.sed - Updated the "2.2" string to "2.2.1" so
links will work.
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
section
Fixes [YOCTO #7096]
Applied a couple review comments to the section to clarify where
to set key variables. Also fixed an incorrect variable name used
to specify the *.cpio file.
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
Fixes [YOCTO #10763]
The final example in the section describing how to create
the base recipe using receipetool create was wrong. I updated
it to use the -d option in addition to the -o opetion. I also
changed the description to match appropriately.
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
Fixes [YOCTO #7096]
We did not document how to create an initramfs image to be included
with a kernel build. Various variables sort of inferred the
knowledge. I created a new section in the "Common Tasks" section
of the dev-manual that describes how to create an initramfs image.
Also, I updated the kernel.bbclass reference section to point back
to the new "how-to" section.
Finally, I also created a bunch of cross-reference links from various
related variables back to the new "how-to" section.
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
This term was incorrect and I have replaced it with the
term "partitioned."
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
new information on how wic works
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
This new variable points to the location of the wics kickstart
file.
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
Fixes [YOCTO #10714]
Apparently there is some issues with GTK3 libraries for the Mars
Eclipse version. The note provides a workaround that requires
editing the eclipse.ini file.
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
The fact that the OpenEmbedded build system can now build
multiple image types caused the KERNEL_IMAGE_BASE_NAME variable
to have the KERNEL_IMAGETYPE portion removed. This could cause
existing recipes that use the KERNEL_IMAGE_BASE_NAME variable
directly issues. I added a section indicating that the user
should address those recipes to avoid problems.
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
Fixes [YOCTO #10717]
Now that multiple images can be built, the KERNEL_IMAGE_BASE_NAME
no longer requires "${KERNEL_IMAGETYPE}" as part of its default
value. I have removed this portion of the default definition
described in the glossary.
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
Fixes [YOCTO #10351]
I added a note to the "Post Installation Scripts" section of the
"Writing a New Recipe" section to call out the fact that the
RPM package manager will not install packages on the target when
any RPM post-install script returns a non-zero exit code when
the script is run on the target.
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
Fixes [YOCTO #10692]
I updated the STAGING_DIR variable description to have a reference
to the SYSROOT_DIRS variable as well as the "Sharing Files
Between Recipes" section of the dev-manual.
I also updated the "Sharing Files Between Recipes" section so
that the role of SYSROOT_DIRS is explained and actually used
in an example to add another directory.
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
Fixes [YOCTO #8584]
Made some edits to tighten this down and make it more efficient.
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
Fixes [YOCTO #8584]
This fix essentially had to document how to add the API
documentation to the standard SDK. The fix required adding a
new appendix to the SDK manual on how to customize that
standard SDK. I could not put just one topic in a new appendix
so I also added a sub-section on how to add indidual packages
to the standard SDK.
Other changes here were the introduction of a new file for the new
appendix, updated the mega-manual.xml file so that it would include
the new chapter when the MM was built. Finally, I added some
cross-referencing to the new appendix from the TOOLCHAIN_HOST_TASK
and TOOLCHAIN_TARGET_TASK variables. And a cross reference from the
distro features section on the api-documentation bullet.
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
Fixes [YOCTO #8584]
Updated the "Distro Features" section to include the
"api-documentation" feature.
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
The string appeared in the text as "$(INC_PR).0". So, fixed
it to be proper with the curly braces.
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
The way I had this string was incorrect. I changed it to "openSUSE".
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
Fixes [YOCTO #10445]
Pointed out that the EXTENDPKGV variable is hard to locate in the
BB manual. Firstly, we don't document that variable in the
BB manual.... maybe we should. For the ref-manual, however, it is
barely referenced in a side example from the dev-manual. So, I
updated the RDEPENDS variable to have a "Tip" box in the area where
it is shown how to use the package version as part of the RDEPENDs
variable.
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
Fixed [YOCTO #10588]
This section was confusing due to the fact that it used an actual
set of IP addresses and image name where they should be clearly
called out as examples. Fixed it.
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
Fixes [YOCTO #10451]
Added a missing closing parentheses to a sentence.
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
The "runqemu Ported to Python" section was using past tense
for a note about previous usage patterns being supported. I
changed this to present tense.
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
These requirements were in place for the ADT, which is gone now.
I have removed the four supported host lists for packages to
support the SDK.
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
Moved a couple notes around and changed some wordings...
nothing major.
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
Fixes [YOCTO #10462]
The section that shows how to build images had two examples all
within the same section. It was suggested to place these examples
in their own sub-sections. Good suggestion. I broke them out into
sub-sections titled appropriately.
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
Fixes [YOCTO #10451]
The example that writes the image to bootable media did not seem
to work when using 'mkefidisk.sh'. It does work using 'dd'. I changed
the procedure to use 'dd'.
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
I added a new section in the "Common Tasks" chapter to support
the fact that BB can now build for multi-configurations.
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
Indicated that the configuration file is not mandatory. Also,
documented the supported qemu* machines should you run the
script without a configuration file.
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
This variable is now redundant due to the way these image
files are staged now. The variable does not need to be
in the glossary. Removing the images is now the default
behavior.
Author: Joshua Lock <joshua.g.lock@intel.com>
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
Provided more detail on what the user can do with configuration files
to use the changed runqemu.
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
I did not put in the links for a couple commits for some of the
2.2 bitbake changes. Put in the links.
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|