Age | Commit message (Collapse) | Author |
|
Conversion of hard links to use the variables set up in the file
documentation/poky.ent.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
|
|
The menu for the YoctoTools in Eclipse moved from underneath
"Windows" to the top level. I fixed the reference to reflect
that change in the GUI.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
|
|
I changed the wording in an example to use "menu" instead of
the incorrect "navigator pane".
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
|
|
I added a bit more information to the third step of the
example that reconfigures a project.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
|
|
I removed a redundant link to the QS manual.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
|
|
I worked through these methods and discovered a bit more on how
they actually work and when the user would use a given method.
The updates reflect this new knowledge.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
|
|
There are many references to YP documentation throughout the
YP manual set. They used to have hard-coded links to the
current release (e.g. yoctoproject.org/docs/1.1 for Edison).
This created a situation where if you went to a document on
the website and clicked on a external reference to another
manual, you would redirect to the current manual on the website.
Really, you would want to go to the latest manual, which is
one that is under development. Changing the links to
"yoctoproject.org/docs/latest" makes the tip of master, which
is used for devloping the next release, always have references
to the manuals being developed and not back to the stable
released set of manuals.
This "latest" and "current" scheme for the links is not perfect.
What has to happen when the latest set of the manuals freezes
and becomes the next stable release, all the links in the docs
will need to be changed from "latest" in the URL to the new
release number. So for example, all the "latest" occurences
would need to be changed to "1.2". Then for the next cycle
as development begins again, the links need to be infused with
"latest" again.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
|
|
Discovered a missing section for installation of the Eclipse Yocto Plug-in.
This information is critical to the release. Jessica discovered the problem.
New section added that describes how to install the plug-in as a standard
"New Software" installation from within the Eclipse IDE.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
|
|
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
|
|
I made several changes based on feedback from Jessica Zhang.
1. Removed "SDKVERSION" as a way of identifying the directory in
which a toolchain tarball is installed. I replaced with "1.1"
2. Cleaned up the bitbake command verbage to consistently use
'bitbake' command.
3. Cleaned up an erroneous reference to the toolchain environment
setup scripts. I was referring the user to the oe-init-build-env
area.
4. Changed wording to indicate that the toolchain tarball is generated
after running bitbake rather than installing the toolchain.
5. Replaced the gmae tarball file used in an example to be the
regular taball.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
|
|
No need to use the long command to restart Eclipse. It will have
been restarted as part of the procedure. I updated the last paragraph
to simply point the user off to the next section.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
|
|
install.
These changes are for installing the YP Eclipse plug-in using a built out
ZIP file.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
|
|
I made some slight edits to configuring the Eclipse IDE and the
procedure to install the plug-in from the zip file. This is not
complete yet.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
|
|
I added a new subsection to the section that talks about how to install
the YP eclipse plug-in. According the Jessica, we should document
this method for installing the plug-in.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
|
|
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
|
|
I made changes to the section titles so they have quotes around them
for easier reading in the PDF manual.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
|
|
I added a development writer note and I noted that running a project
as an eclipse application pops a new instance of Eclipse.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
|
|
fixed some section naming conventions and minor wordings.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
|
|
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
|
|
These edits are extensive and cross into two files: adt-prepare.xml
and adt-eclipse.xml. This is the first pass of a large re-write
to bring the examples up-to-date using the preferred version of
the Eclipse IDE (Indego 3.7). Much has changed.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
|
|
I performed general edits to this chapter as well as addressed the two
items for the YOCTO #1419, which was re-opened. These included
specifying oprofile version 0.9.4 required and the note that
oprofile-server is only installed by default in the core-image-sato-sdk
image.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
|
|
YOCTO #1419: I have re-worded the informational bullet on the OProfile
tool to indicate that you must have version 0.9.4 or greater of the
oprofile-viewer in order to have usable data on the host.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
|
|
In the PDF version of the manual the "‐‐" docbook statement
does not disply correctly. I changed them to "--".
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
|
|
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
|
|
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
|
|
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
|
|
The "Poky Tree Mode" has been replaced with "Build System Derived
Toolchain". SDK Root Mode has been replaced with Stand-alone
Prebuilt Toolchain.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
|
|
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
|
|
Used clearer wording.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
|
|
Updated wording to reflect proper use of build tree terminology.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
|
|
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
|
|
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
|
|
changed the wording for installing required Eclipse Plug-ins.
It was confusing.
|
|
Substituted 'pokylinux.org' with 'yoctoproject.org' in an URL
to locate the OProfile viewer and server.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
|
|
The link to autotools was incorrect. It had 'www' in the URL
when it should not have. it is now
'http://download.eclipse.org/technology/linuxtools/update/'
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
|
|
Updated the URL that points to the Yocto Eclipse Plug-in to
http://www.yoctoproject.org/downloads/eclipse-plugin/1.0.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
|
|
requirement.
Jessica flip-flopped on the need for the Autotools plug-in that was
removed from the manual. I have re-inserted the instructions for adding
this plug-in in as part of the Eclipse set up.
|
|
brackets.
Section 4.1.3.4 discusses custom options for when you want to run
a QEMU image. Jessica felt that we needed to stress the fact that
the options "serial", "nographic", and "kvm" must all appear outside
of the angled brackets.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
|
|
Section 4.1.2 lists plug-ins that need to be installed prior to installing
the Yocto Plug-in for Eclipse. I removed the Autotools plug-in
requirement per Jessica Zhang's instructions.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
|
|
This is the initial draft of the Eclipse chapter.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
|
|
The initial chapters were failing to make due to duplicate section
identifiers that were created when I copied in the original files.
I gave each of the five chapter files (adt-command.xml, adt-eclipse.xml,
adt-intro.xml, adt-package.xml, and adt-prepare.xml) unique identifier
tags.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
|
|
I have added a new directory to documentation named adt-manual.
This directory holds a Figures folder, and the 9 files needed
for the ADT manual. The book consists of five chapters:
adt-intro, adt-prepare, adt-package, adt-eclipse, and adt-command.
There is also a adt-manual.xml file called by the Makefile.
There is also a style.css file. And finally, a adt-manual-customization.xsl
file to control numbering.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
|