summaryrefslogtreecommitdiff
path: root/poky/documentation/ref-manual/resources.xml
diff options
context:
space:
mode:
authorAndrew Geissler <geissonator@yahoo.com>2020-10-16 18:22:50 +0300
committerAndrew Geissler <geissonator@yahoo.com>2020-10-19 20:45:27 +0300
commitaf5e4ef732faedf66c6dc1756432e9de2ac72988 (patch)
tree8f49154a7382b1beb2c3a2b50a6e7c632484fa25 /poky/documentation/ref-manual/resources.xml
parent36fe5df200a94e3ce82ba2dcad16c0a4127f6d46 (diff)
downloadopenbmc-af5e4ef732faedf66c6dc1756432e9de2ac72988.tar.xz
poky: subtree update:b23aa6b753..ad30a6d470
Armin Kuster (1): timezone: update to 2020b Bruce Ashfield (7): linux-yocto/5.4: fix kprobes build warning linux-yocto/5.4: update to v5.4.67 linux-yocto/5.8: update to v5.8.11 linux-yocto/5.4: update to v5.4.68 linux-yocto/5.8: update to v5.8.12 linux-yocto/5.4: update to v5.4.69 linux-yocto/5.8: update to v5.8.13 Fabio Berton (1): weston-init: Add environment file support for systemd unit file Jon Mason (5): armv8/tunes: Move TUNECONFLICTS armv8/tunes: reference parent's TUNE_FEATURES armv8/tunes: Add tunes for supported ARMv8a cores armv8/tunes: Add tunes for supported ARMv8.2a cores tune-cortexa32: fix cortexa32 tune Joshua Watt (2): classes/sanity: Bump minimum python version to 3.5 classes/waf: Add build and install arguments Khem Raj (3): systemd: Use ROOTPREFIX without suffixed slash in systemd.pc.in musl: Update to master strace: Fix value of IPPROTO_MAX Martin Jansa (3): base.bbclass: use os.path.normpath instead of just comparing WORKDIR and S as strings mtd-utils: don't use trailing slash in S base.bbclass: warn when there is trailing slash in S or B variables Michael Thalmeier (1): IMAGE_LOCALES_ARCHIVE: add option to prevent locale archive creation Naoki Hayama (3): uninative: Fix typo in error message local.conf.sample: Fix comment typo local.conf.sample.extended: Fix comment typo Naveen Saini (2): linux-yocto: update genericx86* SRCREV for 5.4 linux-yocto: update genericx86* SRCREV for 5.8 Nicolas Dechesne (8): bitbake: docs: ref-variables: add links to terms in glossary bitbake: docs: sphinx: replace special quotes with double quotes bitbake: docs: update README file after migrationg to Sphinx bitbake: docs: sphinx: report errors when dependencies are not met bitbake: sphinx: remove DocBook files bitbake: sphinx: rename Makefile.sphinx sphinx: remove DocBook files sphinx: rename Makefile.sphinx Peter Kjellerstedt (1): tune-cortexa65.inc: Correct TUNE_FEATURES_tune-cortexa65 Quentin Schulz (4): docs: ref-manual: ref-variables: fix one-letter pointer links in glossary docs: ref-manual: ref-variables: fix alphabetical order in glossary docs: ref-manual: ref-variables: add links to terms in glossary bitbake: docs: static: theme_overrides.css: fix responsive design on <640px screens Richard Purdie (25): glibc: do_stash_locale must not delete files from ${D} libtools-cross/shadow-sysroot: Use nopackages inherit pseudo: Ignore mismatched inodes from the db pseudo: Add support for ignoring paths from the pseudo DB pseudo: Abort on mismatch patch psuedo: Add tracking of linked files for fds pseudo: Fix xattr segfault pseudo: Add may unlink patch pseudo: Add pathfix patch base/bitbake.conf: Enable pseudo path filtering wic: Handle new PSEUDO_IGNORE_PATHS variable pseudo: Fix statx function usage bitbake.conf: Extend PSEUDO_IGNORE_PATHS to ${COREBASE}/meta docs: Fix license CC-BY-2.0-UK -> CC-BY-SA-2.0-UK abi_version,sanity: Tell users TMPDIR must be clean after pseudo changes pseudo: Update to account for patches merged on branch pseudo: Upgrade to include mkostemp64 wrapper poky.conf: Drop OELAYOUT_ABI poking bitbake: command: Ensure exceptions inheriting from BBHandledException are visible bitbake: tinfoil: When sending commands we need to process events scripts/oe-build-perf-report: Allow operation with no buildstats oe-build-perf-report: Ensure correct data is shown for multiple branch options skeleton/baremetal-helloworld: Fix trailing slash oeqa/selftest/runtime_test: Exclude gpg directory from pseudo database bitbake: process: Show command exceptions in the server log as well Ross Burton (10): bjam-native: don't do debug builds coreutils: improve coreutils-ptest RDEPENDS parted: improve ptest devtool: remove unused variable selftest: skip npm tests if nodejs-native isn't available selftest: add test for recipes with patches in overrides devtool: fix modify with patches in override directories boost: build a standalone boost.build boost: don't specify gcc version boost: consolidate and update library list Usama Arif (1): kernel-fitimage: generate openssl RSA keys for signing fitimage Victor Kamensky (2): qemu: add 34Kf-64tlb fictitious cpu type qemumips: use 34Kf-64tlb CPU emulation Yann Dirson (1): rngd: fix --debug to also filter syslog() calls Yoann Congal (1): bitbake-bblayers/create: Make the example recipe print its message Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: I7139cb04b43f722a2118df5346a7a22a13c6a240
Diffstat (limited to 'poky/documentation/ref-manual/resources.xml')
-rw-r--r--poky/documentation/ref-manual/resources.xml298
1 files changed, 0 insertions, 298 deletions
diff --git a/poky/documentation/ref-manual/resources.xml b/poky/documentation/ref-manual/resources.xml
deleted file mode 100644
index 4899b2e59..000000000
--- a/poky/documentation/ref-manual/resources.xml
+++ /dev/null
@@ -1,298 +0,0 @@
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
-"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
-[<!ENTITY % poky SYSTEM "../poky.ent"> %poky; ] >
-<!--SPDX-License-Identifier: CC-BY-2.0-UK-->
-
-<chapter id='resources'>
-<title>Contributions and Additional Information</title>
-
-<section id='resources-intro'>
- <title>Introduction</title>
- <para>
- The Yocto Project team is happy for people to experiment with the
- Yocto Project.
- A number of places exist to find help if you run into difficulties
- or find bugs.
- This presents information about contributing and participating in
- the Yocto Project.
- </para>
-</section>
-
-<section id='resources-contributions'>
- <title>Contributions</title>
-
- <para>
- The Yocto Project gladly accepts contributions.
- You can submit changes to the project either by creating and sending
- pull requests,
- or by submitting patches through email.
- For information on how to do both as well as information on how
- to identify the maintainer for each area of code, see the
- "<ulink url='&YOCTO_DOCS_DEV_URL;#how-to-submit-a-change'>Submitting a Change to the Yocto Project</ulink>"
- section in the Yocto Project Development Tasks Manual.
- </para>
-</section>
-
-<section id='resources-bugtracker'>
- <title>Yocto Project Bugzilla</title>
-
- <para>
- The Yocto Project uses its own implementation of
- <ulink url='&YOCTO_BUGZILLA_URL;'>Bugzilla</ulink> to
- track defects (bugs).
- Implementations of Bugzilla work well for group development because
- they track bugs and code changes, can be used to communicate changes
- and problems with developers, can be used to submit and review patches,
- and can be used to manage quality assurance.
- </para>
-
- <para>
- Sometimes it is helpful to submit, investigate, or track a bug against
- the Yocto Project itself (e.g. when discovering an issue with some
- component of the build system that acts contrary to the documentation
- or your expectations).
- </para>
-
- <para>
- A general procedure and guidelines exist for when you use Bugzilla to
- submit a bug.
- For information on how to use Bugzilla to submit a bug against the
- Yocto Project, see the following:
- <itemizedlist>
- <listitem><para>
- The
- "<ulink url='&YOCTO_DOCS_DEV_URL;#submitting-a-defect-against-the-yocto-project'>Submitting a Defect Against the Yocto Project</ulink>"
- section in the Yocto Project Development Tasks Manual.
- </para></listitem>
- <listitem><para>
- The Yocto Project
- <ulink url='&YOCTO_WIKI_URL;/wiki/Bugzilla_Configuration_and_Bug_Tracking'>Bugzilla wiki page</ulink>
- </para></listitem>
- </itemizedlist>
- For information on Bugzilla in general, see
- <ulink url='http://www.bugzilla.org/about/'></ulink>.
- </para>
-</section>
-
-<section id='resources-mailinglist'>
- <title>Mailing lists</title>
-
- <para>
- A number of mailing lists maintained by the Yocto Project exist
- as well as related OpenEmbedded mailing lists for discussion,
- patch submission and announcements.
- To subscribe to one of the following mailing lists, click on the
- appropriate URL in the following list and follow the instructions:
- <itemizedlist>
- <listitem><para><ulink url='&YOCTO_LISTS_URL;/listinfo/yocto'></ulink> -
- General Yocto Project discussion mailing list. </para></listitem>
- <listitem><para><ulink url='&OE_LISTS_URL;/listinfo/openembedded-core'></ulink> -
- Discussion mailing list about OpenEmbedded-Core (the core metadata).</para></listitem>
- <listitem><para><ulink url='&OE_LISTS_URL;/listinfo/openembedded-devel'></ulink> -
- Discussion mailing list about OpenEmbedded.</para></listitem>
- <listitem><para><ulink url='&OE_LISTS_URL;/listinfo/bitbake-devel'></ulink> -
- Discussion mailing list about the
- <link linkend='bitbake-term'>BitBake</link>
- build tool.</para></listitem>
- <listitem><para><ulink url='&YOCTO_LISTS_URL;/listinfo/poky'></ulink> -
- Discussion mailing list about
- <link linkend='poky'>Poky</link>.
- </para></listitem>
- <listitem><para><ulink url='&YOCTO_LISTS_URL;/listinfo/yocto-announce'></ulink> -
- Mailing list to receive official Yocto Project release and milestone
- announcements.</para></listitem>
- </itemizedlist>
- </para>
- For more Yocto Project-related mailing lists, see the
- <ulink url='&YOCTO_HOME_URL;'>Yocto Project Website</ulink>.
-</section>
-
-<section id='resources-irc'>
- <title>Internet Relay Chat (IRC)</title>
-
- <para>
- Two IRC channels on freenode are available for the Yocto Project and Poky discussions:
- <itemizedlist>
- <listitem><para><filename>#yocto</filename></para></listitem>
- <listitem><para><filename>#poky</filename></para></listitem>
- </itemizedlist>
- </para>
-</section>
-
-<section id='resources-links-and-related-documentation'>
- <title>Links and Related Documentation</title>
-
- <para>
- Here is a list of resources you might find helpful:
- <itemizedlist>
- <listitem><para>
- <emphasis>
- <ulink url='&YOCTO_HOME_URL;'>The Yocto Project website</ulink>:
- </emphasis> The home site for the Yocto Project.
- </para></listitem>
- <listitem><para>
- <emphasis>
- <ulink url='&YOCTO_WIKI_URL;/wiki/Main_Page'>The Yocto Project Main Wiki Page</ulink>:
- </emphasis>
- The main wiki page for the Yocto Project.
- This page contains information about project planning,
- release engineering, QA &amp; automation, a reference
- site map, and other resources related to the Yocto Project.
- </para></listitem>
- <listitem><para>
- <emphasis>
- <ulink url='&OE_HOME_URL;'>OpenEmbedded</ulink>:
- </emphasis>
- The build system used by the Yocto Project.
- This project is the upstream, generic, embedded distribution
- from which the Yocto Project derives its build system (Poky)
- and to which it contributes.
- </para></listitem>
- <listitem><para>
- <emphasis>
- <ulink url='http://www.openembedded.org/wiki/BitBake'>
- BitBake</ulink>:
- </emphasis> The tool used to process metadata.
- </para></listitem>
- <listitem><para>
- <emphasis>
- <ulink url='&YOCTO_DOCS_BB_URL;'>BitBake User Manual</ulink>:
- </emphasis>
- A comprehensive guide to the BitBake tool.
- If you want information on BitBake, see this manual.
- </para></listitem>
- <listitem><para>
- <emphasis>
- <ulink url='&YOCTO_DOCS_BRIEF_URL;'>Yocto Project Quick Build</ulink>:
- </emphasis>
- This short document lets you experience building an image using
- the Yocto Project without having to understand any concepts or
- details.
- </para></listitem>
- <listitem><para>
- <emphasis>
- <ulink url='&YOCTO_DOCS_OM_URL;'>Yocto Project Overview and Concepts Manual</ulink>:
- </emphasis>
- This manual provides overview and conceptual information
- about the Yocto Project.
- </para></listitem>
- <listitem><para>
- <emphasis>
- <ulink url='&YOCTO_DOCS_DEV_URL;'>Yocto Project Development Tasks Manual</ulink>:
- </emphasis>
- This manual is a "how-to" guide that presents procedures
- useful to both application and system developers who use the
- Yocto Project.
- </para></listitem>
- <listitem><para>
- <emphasis>
- <ulink url='&YOCTO_DOCS_SDK_URL;'>Yocto Project Application Development and the Extensible Software Development Kit (eSDK)</ulink>
- manual:</emphasis>
- This guide provides information that lets you get going
- with the standard or extensible SDK.
- An SDK, with its cross-development toolchains, allows you
- to develop projects inside or outside of the Yocto Project
- environment.
- </para></listitem>
- <listitem><para>
- <emphasis>
- <ulink url='&YOCTO_DOCS_BSP_URL;'>Yocto Project Board Support Package (BSP) Developer's Guide</ulink>:
- </emphasis>
- This guide defines the structure for BSP components.
- Having a commonly understood structure encourages
- standardization.
- </para></listitem>
- <listitem><para>
- <emphasis>
- <ulink url='&YOCTO_DOCS_KERNEL_DEV_URL;'>Yocto Project Linux Kernel Development Manual</ulink>:
- </emphasis>
- This manual describes how to work with Linux Yocto kernels as
- well as provides a bit of conceptual information on the
- construction of the Yocto Linux kernel tree.
- </para></listitem>
- <listitem><para>
- <emphasis>
- <ulink url='&YOCTO_DOCS_REF_URL;'>Yocto Project Reference Manual</ulink>:
- </emphasis>
- This manual provides reference material such as variable,
- task, and class descriptions.
- </para></listitem>
- <listitem><para>
- <emphasis>
- <ulink url='&YOCTO_DOCS_MM_URL;'>Yocto Project Mega-Manual</ulink>:
- </emphasis>
- This manual is simply a single HTML file comprised of the
- bulk of the Yocto Project manuals.
- The Mega-Manual primarily exists as a vehicle by which you can
- easily search for phrases and terms used in the Yocto Project
- documentation set.
- </para></listitem>
- <listitem><para>
- <emphasis>
- <ulink url='&YOCTO_DOCS_PROF_URL;'>Yocto Project Profiling and Tracing Manual</ulink>:
- </emphasis>
- This manual presents a set of common and generally useful
- tracing and profiling schemes along with their applications
- (as appropriate) to each tool.
- </para></listitem>
- <listitem><para>
- <emphasis>
- <ulink url='&YOCTO_DOCS_TOAST_URL;'>Toaster User Manual</ulink>:
- </emphasis>
- This manual introduces and describes how to set up and use
- Toaster.
- Toaster is an Application Programming Interface (API) and
- web-based interface to the
- <link linkend='build-system-term'>OpenEmbedded Build System</link>,
- which uses BitBake, that reports build information.
- </para></listitem>
- <listitem><para>
- <emphasis>
- <ulink url='&YOCTO_WIKI_URL;/wiki/FAQ'>FAQ</ulink>:
- </emphasis>
- A list of commonly asked questions and their answers.
- </para></listitem>
- <listitem><para>
- <emphasis>Release Notes:</emphasis>
- Features, updates and known issues for the current
- release of the Yocto Project.
- To access the Release Notes, go to the
- <ulink url='&YOCTO_HOME_URL;/software-overview/downloads/'>Downloads</ulink>
- page on the Yocto Project website and click on the
- "RELEASE INFORMATION" link for the appropriate release.
- </para></listitem>
- <listitem><para>
- <emphasis>
- <ulink url='&YOCTO_BUGZILLA_URL;'>Bugzilla</ulink>:
- </emphasis>
- The bug tracking application the Yocto Project uses.
- If you find problems with the Yocto Project, you should report
- them using this application.
- </para></listitem>
- <listitem><para>
- <emphasis>
- <ulink url='&YOCTO_WIKI_URL;/wiki/Bugzilla_Configuration_and_Bug_Tracking'>Bugzilla Configuration and Bug Tracking Wiki Page</ulink>:
- </emphasis>
- Information on how to get set up and use the Yocto Project
- implementation of Bugzilla for logging and tracking Yocto
- Project defects.
- </para></listitem>
- <listitem><para>
- <emphasis>Internet Relay Chat (IRC):</emphasis>
- Two IRC channels on freenode are available
- for Yocto Project and Poky discussions: <filename>#yocto</filename> and
- <filename>#poky</filename>, respectively.
- </para></listitem>
- <listitem><para>
- <emphasis>
- <ulink url='http://wiki.qemu.org/Index.html'>Quick EMUlator (QEMU)</ulink>:
- </emphasis>
- An open-source machine emulator and virtualizer.
- </para></listitem>
- </itemizedlist>
- </para>
-</section>
-</chapter>
-<!--
-vim: expandtab tw=80 ts=4
--->