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.
(From yocto-docs rev: bca280e74f81a0401c520c8a59e9e07e16f28b8b)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
These changes are for installing the YP Eclipse plug-in using a built out
ZIP file.
(From yocto-docs rev: ea50f63d448b4ff6026a9334440058511782461d)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Feedback from Richard Purdie inserted. I made an edit pass for
style to Richard's re-write.
(From yocto-docs rev: e5bb08e966614c610e6357642b3b2d1522332f7f)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
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.
(From yocto-docs rev: 96de3d21946d64e6b877f067912da8677c3d373a)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This section used the term "tree construction" somewhat out of context.
The section really focuses on what the build process and the user does
prior to compilation. I changed wording to indicate the tree is
validated to be sure that the SRC_URI point to the right stuff and
that the BSP build branch exists.
(From yocto-docs rev: e6332d5045b21354b53bbbe1203f9d52d4d97964)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Made a few corrections to the section describing how to build
the tcf-agent into non-sdk images.
(From yocto-docs rev: e78dc3b3d3dd443506e78651cf9673358577c21d)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The YP only ships one pre-built image that has the tcf-agent built
into it - core-image-sato-sdk. There are a couple methods that exist
to create images that do not normally have this agent so that they
will have it. I updated the "Getting the Images" section to
contain those steps. Lianhao and Jessica Zhang were the technical
resources for these changes. These changes are the first draft.
(From yocto-docs rev: 85432e4892c3fe924bf90961f89e8edfd9693e84)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I created a section on how to prepare for and use the multilib
feature. The information is leveraged off the "Multilib" wiki page
at http://wiki.yoctoproject.org/wiki/Multilib. This is the first
draft of the changes. I expect corrections.
(From yocto-docs rev: 8cf41c90f772018f4f144d63df911912cc298d70)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updated the title pages for the ADT, BSP, Dev, and Ref manuals to
contain the Oct 6 release date for the books. Also, changed the
author field for the BSP guide to include Tom Zanussi as well
as Richard Purdie.
(From yocto-docs rev: 301da0a5b305e4b332397bb67f6a6a77751991d2)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I went through and made sure examples are relevant, wording is correct,
large blocks of unused text was removed, and some references included
to other YP documents.
(From yocto-docs rev: 2231082530dd9cecc234f5f024c4e246afb2968d)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Per Paul Eggleton he suggested that the wording we had about YP focusing
on the GNOME Mobile environment was misleading now. It was in there in the
original version of the FAQ but with time has become outdated. I simply
removed the "GNOME" part and left the part that mentions about YP
being a stable
environment and well-suited for the embedded mobile environment.
(From yocto-docs rev: cc7103eda3fd77d89cecfffa23f0f798aa512132)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
In the example I use for the BSP structure I use the Crown Bay
BSP. I neglected to include any explanation of the recipes-core
directory. I have added some description around this area.
(From yocto-docs rev: ba56c86e5a4aa3fbf23b12d26ffe35a3b6193a78)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I updated the section on the supported distribution section by including
a link to the wiki page that shows what distros we have tested and
their status.
(From yocto-docs rev: e66a18a13dc02af6a0846dd1ecf14aeafcbe5d61)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
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.
(From yocto-docs rev: dea5b1dacc16c08d61356e95bece2aec581dd16d)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This is the second pass for re-documenting RDEPENDS, RRECOMMENDS,
MACHINE_ESSENTIALS_EXTRA_RDEPENDS, MACHINE_ESSENTIALS_EXTRA_RRECOMMENDS,
MACHINE_EXTRA_RDEPENDS, and MACHINE_EXTRA_RRECOMMENDS. These
variables are in dire need of better explanations and examples.
(From yocto-docs rev: cc60bd4c50c7b19209dae06307aec26e962cf476)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I did complete rewrites of RDEPENDS, RRECOMMENDS,
MACHINE_ESSENTIAL_EXTRA_RDEPENDS, MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS,
MACHINE_EXTRA_RDEPENDS, and MACHINE_EXTRA_RRECOMMENDS. These are
sent out for review but these changes represent the first attempt
to clear up confusion on how the six variables are used and relate
to each other.
(From yocto-docs rev: 1d93707fb9383d51322e96eb521e96fcac8bcc47)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Provided better descriptions of these variables and some examples on
how to use them.
(From yocto-docs rev: 3a5cce8c9ba02f90b3554a6f800f69c2e8e77911)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added a more robust description and provided a couple of usage
examples.
(From yocto-docs rev: b8b842b57cc003f1351a551041fe4b3de2fcbfd6)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I added sterner wording on usage and provided an example.
(From yocto-docs rev: 32e07fafadb602b93c9f7b8a78e5baf4c7e1ab5e)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Changed the description of POKYLIBC to note the variable is not supported
and provided a link to TCLIBC. I added the entry for TCLIBC, which
was missing.
(From yocto-docs rev: d76a1ddb79577a3e121df3d590fb601b5e5fbb98)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Noted that POKYMODE is no longer supported and provided link to TCMODE.
Added richer description to TCMODE.
(From yocto-docs rev: a7a326c2c8f4c5f29f3a9723a6895a7113a78357)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Some minor re-wordings to give some context on how to use these special
files and the variable to point to them.
(From yocto-docs rev: 4482b42f4a224bada7a0fa5fe4821a753ba55d80)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I added the directory where the list of know licenses are in the YP
files structure (meta/files/common-licenses).
(From yocto-docs rev: 6a8db1a5ac653dbc8730e61293221c0b0890888d)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Per Paul Eggleton's suggestion I updated the description of this
variable. Some minor wording changes as well as covering two
automatic handling features.
(From yocto-docs rev: 15be3502ca20f657051e02d698b459328328fb14)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Several manuals and areas were still referring to 'glibc' as the
GNU version of the Unix statndrd C library. We do not support this
any longer and now use 'eglibc' to build with. Notable changes were
in the required packages area of the QS manual. I also added a
bit in the reference guide saying how this release does not use
'glibc' to build with but rather 'eglibc'.
(From yocto-docs rev: c2c58914996d747c510706d78ecfd8f41c5e694d)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I added a new section to the "Adding a Package" section. This section
describes how to define the *.a files for when you create a library
that has static linking. Response to a comment from Paul Eggleton.
(From yocto-docs rev: 64499006ecd1e6b7573f1955a2f6e2f1a9564ce8)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The target SDK packages don't need to fulfil a shell dependency
so add /bin/sh to the list of packages we don't need to resolve.
(From OE-Core rev: da761df049249e1ca99eb569642246e51e5bae91)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
RP: It would be better if we could find a way to patch out the compiler
checks in this package...
JaMa: drop PACKAGE_ARCH for now (nobody likes hal nowadays)
(From OE-Core rev: 870191c1c46e36f92c5d90a3eb049154b0597133)
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Jansa: rebased on current master, added nocompiler patch also to
font-alias, dropped allarch from linux-firmware, gnome-icon-theme, hal-info as
those are checking compiler (ie in intltool check) and better to build
them as default arch instead of rebuilding after every machine
change.
* this is also part of [BUGID# 1075]
(From OE-Core rev: 85d8362e0c443f11fe8d3fd0fba55d1bd4983613)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The translation support was disable in build. The
fix-translation.patch was imported from OpenEmbedded to fix a linking
issue in phonon translation support.
(From OE-Core rev: 8d5a5d78f9e83c64ebddcecd7c4fd89cc1264163)
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The documentation was 285M and doesn't fit on the NAND of many machines,
but in another had part of the documentation is needed for the
QT demos, so we split the documentation: so qt demo only RRECOMMAND
the documentation that it really needs.
Thanks to Eric Bénard for explaining me how to split it.
(From OE-Core rev: 97446651cd5128ca7a549df677c920e2463c46f9)
Signed-off-by: Denis Carikli <denis@eukrea.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Without the -no-neon flag, neon is "autodetected"
by looking if the compiler is capable of compiling
a neon test, and succeed, and neon is then enabled
during the compilation.
(From OE-Core rev: 026b59180fe3fbeb43cfd143f053ef33f482ef0c)
Signed-off-by: Denis Carikli <denis@eukrea.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The documentation is 285M and doesn't fit on the NAND of many machines.
(From OE-Core rev: 64d6a6ceceb1f1a599b8140f30071f8bc8e60393)
Signed-off-by: Denis Carikli <denis@eukrea.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
- qt4-tools-nativesdk : actually the qmake binary which gets installed
comes from the native recipe. This patch fix this problem by launching
configure twice : once to compile qmake using the right toolchain for
nativesdk, and a second time using the native qmake to compile all the
other tools for the nativesdk. Then we install the right qmake.
- mkspec : the link actually created in qt4-tools-nativesdk's
do_install point to nowhere so remove it and generate the link in
meta-toolchain-qte as it's the only place where we have all the variable
to create it.
- toolchain_create_sdk_env_script_append : we need to add OE_QMAKE_CFLAGS,
OE_QMAKE_CXXFLAGS and OE_QMAKE_LDFLAGS else the sdk won't find these
variables that are inserted by qmake in the Makefiles.
- with this patch, oe-core generates a working meta-toolchain-qte which
can compile a small example and is properly recognized by qtcreator (this
brings oe-core's meta-toolchain-qte to oe-dev's functional state).
(From OE-Core rev: 5f6fb92b939147d2d6aa7790a378d4b7cce3ada5)
Signed-off-by: Eric Bénard <eric@eukrea.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Use ${POKY_BASE_INSTALL} in order to have the base files and
tools in the image.
(From OE-Core rev: c2f4bae0a100f3752153ecb93adb9ede4f55322a)
Signed-off-by: Eric Bénard <eric@eukrea.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This fixes some error messages in the do_rootfs logs of non-multilib
builds.
(From OE-Core rev: 439867efcc9a7df6062fdb8dae85004b1e9ed08c)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
meta-XYZ directories have been manually added in the past, instead
always ignore them unless they are explicitly added
(From OE-Core rev: 3c6e85c653ce176fd2cb5a570e63c8e5da5a4e48)
Signed-off-by: Matthew McClintock <msm@freescale.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
