Bruce Ashfield [Tue, 6 Feb 2018 16:34:28 +0000 (11:34 -0500)]
poky: update default kernel to v4.15
Updating the default kernel for qemu* to be v4.15. This allows easy
integration of the latest fixes/features for new BSPs. 4.14 is also
available as a LTS kernel option.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Richard Purdie [Wed, 14 Feb 2018 14:43:42 +0000 (14:43 +0000)]
ltp: Improve package stripping
Just exclude the specific tests which have an issue with being stripped
rather than the whole package. This reduces the disk footprint by around
400MB.
Richard Purdie [Wed, 14 Feb 2018 14:40:55 +0000 (14:40 +0000)]
package: Add INHIBIT_PACKAGE_STRIP_FILES to allow files to remain unstripped
There are cases where its useful to allow only a select few files
to be excluded from the package stripping mechanism. Currently
this isn't possible so add a variable to allow this.
This is to be used sparingly as in general the core code should be
doing the right thing. This is better than the alternative of leaving the whole
package unstripped.
Signed-off-by: Chang Rebecca Swee Fun <rebecca.swee.fun.chang@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Yeoh Ee Peng [Thu, 8 Feb 2018 00:01:04 +0000 (16:01 -0800)]
oe-selftest: meta_ide: add tests for meta-ide-support
QA team were testing meta-ide-support manually. Add automated
tests to test that bibtake meta-ide-support will create the
toolchain and environment setup script. Also test that after
using environment setup script, one can compile c program
and build cpio project.
Signed-off-by: Yeoh Ee Peng <ee.peng.yeoh@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Chang Rebecca Swee Fun <rebecca.swee.fun.chang@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
64 bit entry point should be passed in 2 literals ( "0x1 0x00008000"
).ENTRYPOINT is assigned with first half only and erroring out as
'command not found' for the second half. Adding quotes while assignment fixes the
issue.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bruce Ashfield [Tue, 6 Feb 2018 16:21:59 +0000 (11:21 -0500)]
linux-yocto/4.9: drop recipe
As was previously announced, anything older than 4.14 is being
dropped in the master/release branches to better support newer
processors and to ensure that safe/secure kernels are the
defaults for all builds. The time required to update the older
kernels with constant updates (more than just CVEs) is not
justified in new releases.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bruce Ashfield [Tue, 6 Feb 2018 16:21:58 +0000 (11:21 -0500)]
linux-yocto/4.4: drop recipe
As was previously announced, anything older than 4.14 is being
dropped in the master/release branches to better support newer
processors and to ensure that safe/secure kernels are the
defaults for all builds. The time required to update the older
kernels with constant updates (more than just CVEs) is not
justified in new releases.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bruce Ashfield [Tue, 6 Feb 2018 16:21:57 +0000 (11:21 -0500)]
linux-yocto/4.10: drop recipe
As was previously announced, anything older than 4.14 is being
dropped in the master/release branches to better support newer
processors and to ensure that safe/secure kernels are the
defaults for all builds. The time required to update the older
kernels with constant updates (more than just CVEs) is not
justified in new releases.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bruce Ashfield [Tue, 6 Feb 2018 16:21:55 +0000 (11:21 -0500)]
linux-yocto/4.12: pinctrl backports
Backporting the following pinctrl commits to enable controllers on
Intel Cannon Lake:
4b7a5c1b4ec5 pinctrl: intel: Add Intel Cannon Lake PCH-H pin controller support 044631ce1937 pinctrl: intel: Add Intel Cannon Lake PCH pin controller support 2054b0ea59a7 pinctrl: intel: Make it possible to specify mode per pin in a group 55b9053b5a5a pinctrl: intel: Add support for variable size pad groups
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Richard Purdie [Fri, 9 Feb 2018 09:48:48 +0000 (09:48 +0000)]
utility-tasks: Drop fetchall and checkuriall tasks
The same thing can now be done with "bitbake <target> --runall=fetch"
or "bitbake <target> --runall=checkuri".
Dropping the tasks takes "bitbake core-image-sato -g" from 22s to 8s
since it no longer has to resolve the recursive dependencies (it
doesn't know if any given target will touch them or not until it
computes them). That is a significant enough win that its worth any
impact this may have on the small number of users using the tasks.
Nicolas Cornu [Fri, 9 Feb 2018 16:42:07 +0000 (08:42 -0800)]
bitbake: bitbake-user-manual: Added google-repo fetcher and REPODIR var.
Added a new repo Fetcher section in the same spirit as the existing
sections for other supported fetchers. Changes included the new section,
removal of the bulleted item that mentioned this fetcher as an
"additional" fetcher, and the creation of a new variable in the glossary
named REPODIR.
Signed-off-by: Nicolas Cornu <nicolac76@yahoo.fr> Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Robert Yang [Thu, 8 Feb 2018 04:29:38 +0000 (12:29 +0800)]
bitbake: bitbake: toaster: don't use git fetch --all
The '--all'' fetches all remotes, including the ones in $HOME/.gitconfig, which
causes the fetching very slow, so don't use "--all", git fetch should be
enough.
Nathan Rossi [Fri, 2 Feb 2018 13:51:15 +0000 (23:51 +1000)]
bitbake: fetch2: Handle missing donestamp file when content is valid
In order to allow users to manually populate the download directory with
valid content change the assumption that missing the donestamp file
means unfetched content.
This allows users to populate the download dir without needing to create
dummy .done files such that a user does not need a PREMIRROR when using
BB_NO_NETWORK to provide valid content files in the download directory.
To ensure the correct result this change also fails first if the
localpath does not exist. This prevents further parts of the function
attempting to calculating the checksum on non-existent files. This also
fixes some edge conditions around where if the donestamp exists but the
localpath does not it returns, and did not remove the donestamp.
Also added test cases to cover this use case and additional use cases
where for example the fetcher does not support checksums.
bitbake: fetch2/npm.py: Fix inverted condition to prevent infinite loop
At least the cli-color node module has dependencies that have
cyclic dependency among themselves. npm.py is prepared to deal
with such a case but the condition is handled only for downloading
or not a dependency again, but then it goes checking the its
dependency which causes an infinite loop in _getdependencies().
Make this function simply return when a dependency is already
downloaded and only download and check its dependencies when not.
Robert Yang [Wed, 7 Feb 2018 08:01:59 +0000 (16:01 +0800)]
bitbake: contrib/dump_cache.py: make it can dump everything
Have a simple tool to dump bb_cache.dat is useful for investigating and
studying bitbake cache. The old contrib/dump_cache.py can dump pn, pv and
packages for it, now enhance it dump everything.
Here is the usage:
$ /path/to/dump_cache.py --help
usage: dump_cache.py [-h] [-r RECIPE] [-m MEMBERS] [-s] cachefile
optional arguments:
-h, --help show this help message and exit
-r RECIPE, --recipe RECIPE
specify the recipe, default: all recipes
-m MEMBERS, --members MEMBERS
specify the member, use comma as separator for
multiple ones, default: all members
-s, --skip skip skipped recipes
Robert Yang [Thu, 1 Feb 2018 15:15:26 +0000 (23:15 +0800)]
bitbake: bitbake: cache: improve debug message
* Print message when cachefile is found/not can help debug.
* Update "Using cache in" to "Cache dir:" since it was the same as the debug
message of "codeparser & file checksum caches", which caused confusion. And
whether the cache file will be used or not is still unknown at that time, so
just print the cache dir.
Robert Yang [Thu, 1 Feb 2018 15:15:24 +0000 (23:15 +0800)]
bitbake: bitbake: cooker: don't stop file notifier when cooker is shutdown
It should be live/exited with server rather than cooker, fixed:
$ bitbake --server-only -T -1
Set MACHINE = "qemux86" in conf/local.conf
$ bitbake quilt
Set MACHINE = "qemuppc" in conf/local.conf
$ bitbake quilt
[snip]
ERROR: When reparsing /workspace1/lyang1/poky/meta/recipes-connectivity/openssl/openssl_1.0.2m.bb.do_package, the basehash value changed from c216f7f4fdd3cf4a0b10b975a636426c to d5a8e9431ab261381752d7a64c7b2fa9. The metadata is not deterministic and this needs to be fixed.
[snip]
This is because the server doesn't know local.conf is changed since the
notifiers are stopped, so it doesn't reparse, and then we would get the errors,
let the notifiers live/exited with server can fix the problem.
Robert Yang [Thu, 1 Feb 2018 15:15:23 +0000 (23:15 +0800)]
bitbake: bitbake: cooker: fix for BBFILE_PATTERN matches bbappend
The old code couldn't handle nestled layers correctly, e.g.:
parent_layer/sub_layer/foo.bb
Note there are two layers, parent_layer and sub_layer.
And in parent_layer/conf/layer.conf:
BBFILE_PATTERN_parent_layer = ""^${LAYERDIR}/"
This setting is incorrect since it also matches parent_layer/sub_layer/foo.bb,
so it warns that no files matched sub_layer, this is the expected behavior, but
it doesn't warn when there is a parent_layer/sub_layer/bar.bbappend, this was
incorrect since the bbappend is also matched by BBFILE_PATTERN_parent_layer, it
should warn and let the user fix the problem. Check the bbappend in already
"matched set" before return it as matched by "unmatched set" can fix the problem.
Richard Purdie [Fri, 9 Feb 2018 09:21:00 +0000 (09:21 +0000)]
bitbake: main/runqueue: Rework runall task and add runonly option
The runall commandline option was confusing people. There are in fact two
different behaviours people may want.
a) For a given target (or set of targets) look through the task graph and
run task X only if its present and would have been built.
b) For a given target (or set of targets) look through the task graph and
run task X if any recipe in the taskgraph has such a target even if it wasn't
in the original task graph.
I've decided to interpret the existing "runall" option as b), even if right
now if behaves like a). For a), which is a valid use case, this patch adds
a "runonly" option.
With both behaviours present, I'm hoping we can then kill off the "fetchall",
"checkuriall" and other tasks from OE metadata and replace them with this
option. This would significantly speed up task graph processing.
(Deleting the checkuriall and fetchall tasks takes "bitbake core-image-sato -g"
from 22s to 8s).
Scott Rifenbark [Mon, 12 Feb 2018 17:11:37 +0000 (09:11 -0800)]
getting-started, dev-manual: Created Layer Model section
This involved removing the general information about layers from
the dev-manual and incorporating it into the new section of the
getting-started manual.
Scott Rifenbark [Tue, 6 Feb 2018 18:46:38 +0000 (10:46 -0800)]
getting-started, mega-manual: Added new GS chapter
I have added a chapter to the getting-started manual that will
introduce the YP. Just the framework exists at this point.
Changes to the mega-manual.xml file were made to include the
new chapter in that manual as well.
Scott Rifenbark [Fri, 2 Feb 2018 18:11:58 +0000 (10:11 -0800)]
documentation: Moved the detailed build section to concepts-manual.
The section that provides a closer look into the build system has
moved from the getting-started manaul to the concepts-manual.
I fixed all the links, provided some coded formatting of the
entire section, and made general updates.
The other manuals had links that needed fixed due to the move.
Scott Rifenbark [Wed, 31 Jan 2018 17:49:46 +0000 (09:49 -0800)]
concepts-manual: Content adjustments for the manual.
The manual's two files are an introductory chapter and then
a deeper concepts chapter. I scrubbed through the material, which
originated from the getting-started (overview-manual).
Scott Rifenbark [Wed, 31 Jan 2018 17:31:41 +0000 (09:31 -0800)]
documentation: Updated links into new concepts-manual
Creation of a new concepts manual and moving of chapters from the
getting-started (overview-manual) caused many links and manual
reference titles to break. I fixed these throughout the YP
docs.
Scott Rifenbark [Wed, 31 Jan 2018 16:29:40 +0000 (08:29 -0800)]
concepts-manual: Removed unwanted figures
When creating the new concepts-manual, I copied the existing
getting-started manual over. This created a figures folder that
had a lot of figures not needed in the concepts-manual. They
have been removed.
Scott Rifenbark [Tue, 30 Jan 2018 21:45:31 +0000 (13:45 -0800)]
documentation: Purged overview manual references
When I converted the Yocto Project Overview Manual to the Getting
Started With Yocto Project Manual, I updated the strings for
references from "&YOCTO_DOCS_OVERVIEW_URL" TO
"&YOCTO_DOCS_GS_URL". Unfortunately, I did it with a global command
that did not take into account the text the might follow the link
by saying "see such-and-such section in the Yocto Project Overview
Manual." So, I had to hand fix these.
Additionally, since I have moved a deeper concepts chapter that
was in the getting-started manual to a new Yocto Project Concepts
chapter, many of those links changed had to really go to the new
manual instead. Those were fixed.
Scott Rifenbark [Tue, 30 Jan 2018 21:43:49 +0000 (13:43 -0800)]
mega-manual.xml: Removed the getting-started-concepts.xml file
Because the deeper concepts chapter that was in the Getting Started
With Yocto Project Manual was moved to a new Yocto Project Concepts
Manual, I had to delete it from the mega-manual.xml file where it
would be included as a chapter in the getting-started manual.
Scott Rifenbark [Tue, 30 Jan 2018 21:42:02 +0000 (13:42 -0800)]
getting-started: Removed "concepts.xml" file
This file was for a deeper concepts chapter. It will go into the
new Yocto Project Concepts Manual. Removing it required deleting the
*.xml file and updating getting-started.xml to not include it in the
build.
Scott Rifenbark [Tue, 30 Jan 2018 19:31:29 +0000 (11:31 -0800)]
getting-started: Removed accidental tracked files
I accidentally pushed a commit after building out the new getting-started
manual before applying some key files to the .gitignore file. So,
the HTML, TGZ, and eclipse/* stuff got tracked in Git. I don't
want that. So I had to use the 'git rm' command to untrack those
files.
Scott Rifenbark [Mon, 29 Jan 2018 23:18:03 +0000 (15:18 -0800)]
documentation: Created new "Getting Started" manual.
Creation involved removing the overview-manual and replacing it
with the getting-started manual. All links to the string
"&YOCTO_DOCS_OVERVIEW_URL" had to be replaced with
"&YOCTO_DOCS_GS_URL" across the entire YP manual set. I renamed
files used to create the manual with prefixes suited for the
new manual name, which is "Getting Started With Yocto Project".
The style sheet for the new manual needed updating to display the
new .PNG image for the title page. The mega-manual file had to
be updated to include the files. The mega-manual.sed file had
to be updated to include the new manual and not use the overview
manual.
Scott Rifenbark [Tue, 23 Jan 2018 19:29:22 +0000 (11:29 -0800)]
documentation: Removed "usingpoky" chapter from ref-manual
Fixes [YOCTO #12370]
All of the information from the "usingpoky" chapter in the
ref-manual has been distributed out over the rest of the
YP manual set. Primarily, this information went into the
dev-manual and the overview-manual. Because the chapter is
no more, I had to update the mega-manual.xml to not include that
chapter. Also, had to update ref-manual to exclude the chapter
as part of the Make process.
Scott Rifenbark [Tue, 23 Jan 2018 00:13:34 +0000 (16:13 -0800)]
ref-manual, dev-manual: Moved QEMU info from ref-manual to dev-manual
Fixes [YOCTO #12370]
The QEMU information in the ref-manual "using" chapter has been moved
to the dev-manual's chapter 5, which is a dedicated QEMU chapter.
Some information is reference and that is why I had it separated out
into the reference manual. However, pressures are mounting to get
that stuff out of the ref-manual and into the dev-manual. So, it
has been moved.
Scott Rifenbark [Tue, 16 Jan 2018 18:59:43 +0000 (10:59 -0800)]
dev-manual, ref-manual: Consolidated debug info into dev-manual
Fixes [YOCTO #12370]
Moved the debug information from the ref-manual to the dev-manual
where other debug information exists. We now have a single area
(section) that deals with various debugging techniques and tips.
Scott Rifenbark [Mon, 15 Jan 2018 19:30:54 +0000 (11:30 -0800)]
dev-manual, ref-manual: Moved building image to dev-manual
Fixes [YOCTO #12370]
The section in the ref-manual that overviewed the buld process was
redundant and more of a "how-to" topic. I have moved and merged it
into the dev-manual into a similar area.
Scott Rifenbark [Thu, 11 Jan 2018 22:19:00 +0000 (14:19 -0800)]
ref-manual: Removed the "technical-details.xml" file
Fixes [YOCTO #12370]
The "technical-details.xml" file was for the old chapter four of the
ref-manual. All content in that chapter has been moved to the new
concepts chapter of the overview-manual. I updated the mega-manual.xml
file to not include the old technical-details chapter as part of the
ref-manual. I also updated the ref-manual.xml file to not include the
technical-details.xml chapter when building the ref-manual.
Scott Rifenbark [Thu, 11 Jan 2018 22:11:47 +0000 (14:11 -0800)]
overview-manual, ref-manual: Moved "Licenses" to overview-manual
Fixes [YOCTO #12370]
The "Licenses" section in the technical details chapter of the
ref-manual was concepts and needed moved to the new overview-manual.
Some links were broke during the move and they were fixed in the
BSP and dev-manual.
Scott Rifenbark [Thu, 11 Jan 2018 19:51:23 +0000 (11:51 -0800)]
overview-manual, ref-manual: Moved "Wayland" section to overview manual
Fixes [YOCTO #12370]
The "Wayland" section needed to be moved to the concpets chapter in the
new overview-manual. I moved it and fixed a few links that needed
adjusting due to the move.
Scott Rifenbark [Thu, 11 Jan 2018 19:17:06 +0000 (11:17 -0800)]
overview-manual, ref-manual: Moved Pseudo and Fakeroot to overview manual
Fixes [YOCTO #12370]
The "Fakeroot and Pseudo" section is concepts and needed moved from the
ref-manual to the new concepts chapter of the overview-manual. Some
links needed to be fixed as well.
Scott Rifenbark [Thu, 11 Jan 2018 19:02:11 +0000 (11:02 -0800)]
overview-manual, ref-manual: Moved auto added runtime deps section
Fixes [YOCTO #12370]
The "Automatically Added Runtime Dependencies" section moved from the
ref-manual to the overview-manual. This topic is concepts and needs
to live in the new overview-manual's concepts chapter. Fixed some
links in the ref-manual and one in the dev-manual.
Scott Rifenbark [Wed, 10 Jan 2018 23:21:38 +0000 (15:21 -0800)]
yocto-project-qs: Defined Poky and added overview manual link
Fixes [YOCTO #12128]
Updated the phonetic rendition of the term "poky". Historically,
this term is mispronounced. I am now saying "Pock-ee" as the official
way of pronouncing this term.
I also added a link to the Yocto Project Overview Manual that was
in the Tip box. The manual did not exist earlier. Since it does
exist now, I have added the link.
Scott Rifenbark [Wed, 10 Jan 2018 21:01:25 +0000 (13:01 -0800)]
ref-manual, overview-manual, Makefile: Moved toolchain concepts
Fixes [YOCTO #12370]
Moved the "Cross-Development Toolchain Generation" section from the
ref-manual to the overview-manual into the concepts chapter. This
information is conceptual and now needs to live in the concepts
chapter of the new overview-manual. Moving the section caused a
few links to have to be fixed in the ref-manual. There was also a
figure in the section. So, I had to move the figure from the ref-manual
to the overview-manual "figures" folder and update the Makefile for
the TARFILE generation.
Scott Rifenbark [Wed, 10 Jan 2018 20:35:02 +0000 (12:35 -0800)]
ref-manual, overview-manual, yocto-project-qs: Moved YP Components
Fixes [YOCTO #12370]
Moved the "Yocto Project Components" section from the ref-manual to
the overview-manual. This material falls into the "concepts" area
and is being moved from the ref-manual. One link in the
yocto-project-qs was affected and updated. Oh... another link in the
ref-manual for a variable also fixed.
Scott Rifenbark [Wed, 10 Jan 2018 19:36:56 +0000 (11:36 -0800)]
dev-manual, ref-manual: Moved Wic Plug-In section to dev-manual
Fixes [YOCTO #12370]
I had a section on Wick Plug-Ins in the ref-manual in the
"technical details" chapter. This section has been combined with the
section on using Wic that lives in the dev-manual. This move creates
a single section on using Wic to create Wic-partitioned images.
The section was moved out of the ref-manual and merged into the
dev-manual Wic section.
Scott Rifenbark [Tue, 9 Jan 2018 23:53:40 +0000 (15:53 -0800)]
overview-manual, ref-manual, dev-manual: Moved x32 stuff
Fixes [YOCTO #12370]
The section on the x32 psABI topic was in the "technical details"
section of the reference manual. This section combined conceptual
and "how to" information for x32 psABI. I moved the conceptual
information to a new chapter in the overview-manual. I moved the
"how-to" information to a separate topic in the dev-manual. This
resulted in the mega-manual being updated to take on a new chapter
for the overview-manual (overview-concepts.xml). No links were
affected.
Scott Rifenbark [Fri, 5 Jan 2018 23:43:42 +0000 (15:43 -0800)]
ref-manual: Separated terms into separate chapter
Pulling out some introductory information from the old "Introduction"
chapter of the ref-manual has isolated the system requirements and
term definitions sections. I have decided to create a new chapter
for terms as they are a reference item. This leaves system requirements
also alone as a new chapter. So, I dumped the introduction.xml chapter
in favor of the two new chapters.
Scott Rifenbark [Fri, 5 Jan 2018 22:03:53 +0000 (14:03 -0800)]
overview-manual, ref-manual: Moved introductory material to overview manual
Fixes [YOCTO #12370]
Moved an introductory section for YP that was in the ref-manual
to the beginning of the YP environment chapter of the overview-manual.
Had to move a figure and update the makefile as well as adjust some
links.
Scott Rifenbark [Fri, 5 Jan 2018 20:45:34 +0000 (12:45 -0800)]
ref-manual: Fixed targets for sdk-manual links
I had tried using a #-type target for some links designed to go
to the top of the sdk-manual. It was not working out so I removed
the targets. The links now render benign for the mega-manual as
they should and render hot for the individual manual as they should.
Scott Rifenbark [Fri, 5 Jan 2018 20:23:24 +0000 (12:23 -0800)]
mega-manual: Updated sdk-manual figure used
I failed to copy the updated sdk-manual title figure to the
mega-manual/figures directory when the sdk-manual title had changed.
This was causing the title of the sdk-manual in the mega-manual
to render as the old one.
projects / thirdparty / openembedded / openembedded-core-contrib.git / log
