poky-ent: Fixed the variables and set release to March 2019
<manual>.xml: Fixed manual revision tables
(From yocto-docs rev: 16f3ecf054baa4316ab8946681eda353f7c5ece8)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updated poky.ent to use "TBD" for the release date variable.
Updated the mega-manual.sed file to use "2.5.2"
Updated all the <manual>.xml files to include a new entry for
the 2.5.2 release date
Updated poky.ent to have all applicable 2.5.2 variables changed.
(From yocto-docs rev: 189ec469aa8797d75567cfef444b9896d3467e7a)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
poky.ent - updated variables for 2.5.1
mega-manual.sed - updated string from "2.5" to "2.5.1"
<manual>.xml - updated manual revision tables for 2.5.1
and September 2018 date
(From yocto-docs rev: a47382f00ad1a5a1df02ffa3dead7a0bd597bf45)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Broken link fixed.
(From yocto-docs rev: 915f9e8e47ae95a3102063f5825730953afb1ff0)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I made some re-writes for clearity.
(From yocto-docs rev: 45e710923afb45066383877252af79faf3b2f5fc)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
On second thought, the list I turned into a bullet list from the
previous commit was a bit hasty. That list is order dependent.
Reverted the list.
(From yocto-docs rev: 24a77078af0e7a59dd180bdfe6a29afbaefdffcf)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The list appears to be not a numbered list. Fixed that. Also, provided
better wording around "exposing" the sstate-cache.
(From yocto-docs rev: e1f8c9bf3ef7028b48b38801557292434c872419)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Step 1 of the "Providing Updates to the Extensible SDK After Installation"
section really did not do much for the reader regarding setting up a
HTTP or HTTPS directory. I added more detail on how to generally do
that.
(From yocto-docs rev: b90de53859545a835629a56eab08fa58479c36ff)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
There are two sections that deal with this topic. One is from the
standpoint of a user using a 3rd party published and installed
extensible SDK ("Applying Updates to an Installed Extensible SDK").
The other is from the standpoint of a person providing Extensible
SDKs for consumption ("Providing Updates to the Extensible SDK
After Installation"). These sections needed some closer examination
regarding fully describing what was going on. I provided some
re-writes to both.
(From yocto-docs rev: 62028ea4df684e495e78d00a440318d061098f15)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The title for the section on how to effect changes to an installed
extensible SDK is better suited as "Providing Updates to the
Extensible SDK AFter Installation."
(From yocto-docs rev: 382c172fd9a51cd4c650333549210aa760ea9774)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
In "Providing Updates After Installing the Extensible SDK" section,
Step 1 had a bit of a grammar error. Not technically, but it
could have been written better. I fixed that.
(From yocto-docs rev: f6710a7047c215f9a1a989b9a009399405770c06)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I added more information on how this is done. Still could use a bit
of detail on how you actually do it.
(From yocto-docs rev: 7a035ffb4443f7920521ccd918ec844d1ca118e5)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I updated this section with clearer text.
(From yocto-docs rev: bb0e6613b7dbe7f8c9ca80a64ee9c67a74e01fc1)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Made improvements to this section and tied the variables together
for the explanation.
(From yocto-docs rev: 592abe8fe11389b58e8c0cf7991a400bdd515b16)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This figure had changed. I updated the file and folder hierarchy.
Also fixed some wording.
(From yocto-docs rev: 40e89997f50fdaecee88c8c98e21cc212bf1ed13)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The figure was incorrect for the installed file and folder hierarchy
for a standard SDK. I updated it. This figure goes in both the sdk-manual
and the mega-manual.
(From yocto-docs rev: c21d76b885afedafe7b866d9f4997633a776902c)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Verified a good example and updated the text to match that example.
(From yocto-docs rev: 8655662b1f031463fafcf11fcd22243a75e817f8)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The value of SDKMACHINE must match the architecture of the machine
on which the SDK installer is being built if you are building an
installer for an extensible SDK. I added a note to this effect.
(From yocto-docs rev: 8720b3ea9e7260f891db1be46fb756aba09d5f51)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updated the example to more current information.
(From yocto-docs rev: 6c37cc5231ae560762c5bc8234331d53ebe7b69d)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updated some links. Also, rewrote the note about the libraries.
It was inaccurate.
(From yocto-docs rev: ca6593ea9336dd1974ce65ce1d9ca15af8583915)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I corrected some wrong information. Provided the correct terminology
for the build host, and provided quotations for supplied values to
be in line with manual writing conventions.
(From yocto-docs rev: aa88f3f09dce042a2f5b39bf059401b0cd08a6cc)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Made several formatting changes for selections. These should
be using quotes and not being formatted in Courier.
(From yocto-docs rev: 0ca787b3ce91afbb4ea4aeb12052cff39892e99f)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Rendered a menu correctly instead of in formatting mode.
(From yocto-docs rev: 4c98d18ee3fbc57a369df4eb1251cafaaf16adee)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The step that describes how Eclipse runs the Autotools is too
detailed and can run into problems as Autotools workflow changes.
I made it more general.
(From yocto-docs rev: 5a67a115395d3e18523c4a3b3be24c214e560e54)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Needed to render fields and items from the dialog in normal
text, not in formatted text.
(From yocto-docs rev: a2e17bd828ab1205bbb0c99fa00a76c2f5727e99)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Both Neon and Oxygen needed some changes for correct use of the
way we refer to menus and fields.
(From yocto-docs rev: c35168b623f6bece20ae7df1ae430259b2d20044)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Used correct formatting for menu items and items fromt the
dialog screens.
(From yocto-docs rev: 28b37c9b0785da50a0da19757d70429de06991b5)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The list in the "Configuring the Neon Eclipse Yocto Plug-In
section should be an ordered list and not a bulleted list.
(From yocto-docs rev: 9e616582ee27d0bb976427d21d54b023f83eff56)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I provided similar wordings in places in this section as were provided
in the parallel "oxygen" section.
(From yocto-docs rev: 956ee839f05d6608c315899c4444d125db338ef7)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Needed to consolidate a couple steps here. When you add in the
location for the YP Plug-in, it auto-populates the options.
Updated the prose to reflect that.
(From yocto-docs rev: 3d621a1fe552c6133517256c21efdfe4cacfe6ed)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The "Configuring the Neon Eclipse IDE" section needed a bit more
information in the note. Telling the users that if some options
are already installed they will not appear in the list.
(From yocto-docs rev: 09b3252aaf49574e669b67e3ff00dceab89b40f5)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Steps indicated you had to be in a clean directory to unpack the
tarball. This is false. You can be in any directory and unpack the
file. Unpacking it puts all the files into a directory named
"eclipse".
(From yocto-docs rev: 426aa18db25dbc275674a8aef26ede586a79ed3f)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixed this step to be more accurate.
(From yocto-docs rev: 9df184b4ed7e8a7fa5849624911b810129c099a7)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The link was pointing to the Chapter 5 as if it were in a different
manual. The link worked but should have been pointing to the actual
section of the Eclipse flow overview. Fixed it.
(From yocto-docs rev: c60bc694a5b25fd2a9df5a10691ba301d39c5f16)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Using consistent wording.
(From yocto-docs rev: 067cba1b925cca971e783bd7e4abc9c965b0d8de)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The step describes the installation process and the intial launch
process. No information exists for describing how you launch
Oxygen from outside the install process. I added a note that
tells where the "eclipse" binary is installed and an example
line to invoke it.
(From yocto-docs rev: 6e3dbc9e123394d311da234e4457b9a6c253ff0d)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Provided better instructions and accounted for the fact that it
is just this workflow here that is assuming the need for a
YP-built image.
(From yocto-docs rev: edba9e07d7029e9276ebfd288448f4849ff3aed4)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updated the "Workflow Using Eclipse" section head to not match so
closely the "Working With Eclipse" section heading. TOC appeared
funny.
Also, updated the step 1 to be more accurate regarding the real
need of having a YP build host and where to go to get information
on setting it up.
(From yocto-docs rev: 4951b3f492c24724f1169068ee3593ad93b0c48a)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Found several items that were slightly off after working through the
procedure. Updates to bring it into line with reality.
(From yocto-docs rev: bc024c4484db3fdfb44fdb6f8709ad47378d85e2)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Expanded this section to contain a figure of the flow and an
example that showcases the ways to override and use SDK
environment and Makefile variables.
(From yocto-docs rev: 422b5dda50c47d03adf2a8c4e8cfdb02eddff0ca)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The Makefile-Based Projects section was expanded to add a useful
example and figure. Added this figure to the sdk-manual and
mega-manual figures folders.
Updated the Makefile to include the new figure as part of the
tar files for each manual.
(From yocto-docs rev: 5bf979f924200a31cb28fe9920b0877d5562e0f5)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Autotools is simpler now as it uses "autoreconf" to one-step a bunch
of the existing tools such as aclocal and autoconf. I updated the
figure to reflect the simpler flow and also the steps that accompany
the figure.
(From yocto-docs rev: 232f80b4723c1a51ed0d0e55c00b13e64390d69a)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I wrote the section to include a flow diagram using "make" and
provided a working example highlighting how to override environment
variables.
(From yocto-docs rev: c147d1ee1f6f33a5222eb1ccf466d1854c67815c)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Two changes here. One was a note to the "make" step of the
Autotools-based section. I cross-referenced the Makefile section
for information on how SDK installation environment variables
are respected and or overridden when using make variables.
Also, fixed the quotation syntax of the four environment variable
examples used in the "Makefile-Based Projects" section.
(From yocto-docs rev: a5742a8730359ed28f10108cb741913472337c57)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
New figure for the section on Autotools workflow. The figure
goes in the folders for both the sdk-manual and the
mega-manual.
Updated the Makefile to include the new figure in the tarball
when creating both manuals.
(From yocto-docs rev: 01f33f7ee293de4dbe0398aae6c087de686be965)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Did a re-write of this section with better explanations.
I also pulled the bit about passing parameters to the
configure script into the step that talks about that.
(From yocto-docs rev: 778e566100450cce15808f80ace2b92f811001a7)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
