Age | Commit message (Collapse) | Author |
|
Add release date for 3.0.2.
Signed-off-by: Armin Kuster <akuster808@gmail.com>
|
|
Added a few comment lines in Makefile to commemorate Scott's
contributions
Signed-off-by: Jefro <jefro@jefro.net>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Signed-off-by: Armin Kuster <akuster808@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
I had a duplicate "October 2019" release in the dev-manual.
Also, I forgot the year for the "October 2019" release entry.
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
They were confused with the 3.0 variable set.
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
* Updated poky.ent
* Updated mega-manual.sed
* Updated <manual>.xml with release date
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
using ../.. instead of ../../..
Fixes [YOCTO #13553]
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
Fixes [YOCTO #12760]
Updated the cmake.bbclass description to tell what directory
to insall custom CMake toolchain files into. Also, updated
the two areas in the "Writing a New Recipe" section that
mention CMake. Placed a couple notes there concerning the
same directory stuff.
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
Fixes [YOCTO #13596]
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
Alejandro Enedino Hernandez Samaniego <aehs29@gmail.com>
commited a change to these manuals (see
9e79e96cad66316c1b4ee608723edfa763f0f9ef) and did not
use YP documentation standards for the content. I cleaned
up the text and tabbing.
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
This was in a moving to YP version 1.8 migration section.
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
I was using "2.8" throughout the manual set instead
of "3.0". Updated all aspects to "3.0".
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
Turned "2.8" into "3.0". Nobody told me about skipping
2.8 and 2.9.
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
|
|
Add Fedora 30 and Ubuntu 19.04.
Swap openSUSE 42.3 for Leap 15.1.
Remove huge comment of old distributions.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
The syntax to use multiconfig builds changed from multiconfig:foo:target
to mc:foo:target.
Clarify that BBMULTICONFIG defines additional configurations along with
the one coming from local.conf.
Fix these changes on both the dev manual and the reference manual.
Signed-off-by: Alejandro Enedino Hernandez Samaniego <aehs29@gmail.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
|
|
When removed all it did was
inherit gnomebase gtk-icon-cache gconf mime
which would also be the most trivial replacement.
Most of the time not all of these classes were needed,
and it is recommended to use only the ones actually required.
Signed-off-by: Adrian Bunk <bunk@stusta.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Debian 10 is a supported distribution now, so add it to the documentation.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
bluez4 was removed even from meta-oe 2 years ago,
which made made the bluez5 feature for selecting between
bluez4 and bluez5 mandatory for using the bluetooth feature.
The backfilled bluez5 feature has been removed,
including the bluetooth class that helped recipes
for selecting between bluez4/bluez5.
Recipes can replace ${BLUEZ} with bluez5.
Signed-off-by: Adrian Bunk <bunk@stusta.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
|
|
Corrected the requirements for the KERNEL_DEVCIETREE
variable example.
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
This section needed the wording updated.
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
We are not using Python2. I removed this instance in the ref
manual. The variable "PYTHON_PN" referenced Python 2. It no
longer does.
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
There was a typo in the BBMULTICONFIG variable description.
It appeared as "BBMULTIFONFIG". I fixed it.
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
In the "Enabling GObject Introspection Support" section, a link
existed to the "Known Issues" section further down in the
chapter. The target of the link was missing and appeared as the
placeholder "xxx". I put in the proper link.
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
Fixes YOCTO #13079
Bug is about making sure the section on the devtool command
talks about oe-local-files. Two devtool commands (modify
and upgrade) needed to mention the role of the oe-local-files
area and how it is used during these commands. I updated the
appropriate sections:
* Use devtool modify to Modify the Source of an Existing Component
* Use devtool upgrade to Create a Version of the Recipe that
Supports a Newer Version of the Software.
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
Missing information for some of the releases put back in.
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
Fixed in "Selecting an Initialization Manager" section.
Extraneous word needed removed.
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
Fixes [YOCTO #10098]
I updated the "Source Control Managers (Optional)" section
to reference the "Fetchers" section in the BB manuual.
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
I provided a general link to the wiki on npm software.
Also, updated the section to point to the new section on how to
create NPM packages, which is in the dev-manual.
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
I added the "Creating node package manager (NPM) packages
section link to the list. Also, made some edits to make
the capitalization consistent in the list items.
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
The newly created section on how to create NPM packages
required a figure. I added the figure to both the dev-manual
and mega-manual tarballs creation areas.
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
Fixes [YOCTO #10098]
This is a new section in the development tasks manual that describes
how to create Node Package Manager (NPM) packages. I put the
section in the "Working with Packages" section.
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
I left out the word "not" in a key sentence in the new
"Checking on the Upgrade Status of a Recipe" section.
Little words can make big differences.
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
I updated the section to include more detail on what the user
sees in the returned table.
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
I show the "devtool check-upgrade-status" command as part of
the "do_checkpkg" task section. I added a cross-reference
link to the "Checking on the Upgrade Status of a Recipe"
section in the ref-manual.
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
The section "Upgrading Recipes" covers several ways of
upgrading a recipe. I added some stuff in the introductory
area that mentions the fact a user might want to check
the upgrade status of a recipe first.
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
I added a new section showcasing the "devtool check-upgrade-status"
command.
Also, added a note in the "Upgrading a Recipe" section" to tell
the reader they might want to check on a recipe's upgrade
status before upgrading a recipe.
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
Specifically missing was the "devtool check-upgrade-status"
command.
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
This class was removed for 2.7 and I took the reference section
out of the class area.
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
The migration section noted this class as becoming obsolete.
I removed it from the class reference section.
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|
|
Ousted these since it was noted in the migration section that
the class had been removed. Modified all references to the
removed class as needed.
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
|