diff options
author | Andrew Geissler <geissonator@yahoo.com> | 2020-10-27 21:52:24 +0300 |
---|---|---|
committer | Andrew Geissler <geissonator@yahoo.com> | 2020-11-23 23:00:33 +0300 |
commit | 4c19ea120a3e7a73dc8470c86744bc95997f1c90 (patch) | |
tree | dd2f114bc0a3614b653d1afde08bec22ab646e7e /poky/documentation/dev-manual/dev-manual-start.rst | |
parent | 5f4b874fc7d6f8941582b97eb688c67dc21efffb (diff) | |
download | openbmc-4c19ea120a3e7a73dc8470c86744bc95997f1c90.tar.xz |
poky: subtree update:ad30a6d470..7231c10430
Akira Shibakawa (3):
License-Update: attr: Add a missing file to LIC_FILES_CHKSUM.
License-Update: kmod: Add a missing file to LIC_FILES_CHKSUM.
License-Update: gdk-pixbuf: Fix LICENSE.
Alejandro Hernandez Samaniego (1):
baremetal-helloworld: Fix install path since S doesnt have a trailing slash
Alexander Kanavin (4):
ncurses: only include upstream releases in version check
python3: fix upstream version check
boost-build-native: fix upstream version check
selftest/virgl: drop the custom 30 sec timeout
Alistair (1):
weston-init: Allow setting idle time to 0
Changqing Li (1):
toolchain-shar-extract.sh: don't print useless info
Charlie Davies (1):
bitbake: bitbake: fetch/git: use shlex.quote() to support spaces in SRC_URI url
Chen Qi (2):
watchdog: use /run instead of /var/run in systemd service file
cups: use /run instead /var/run in systemd's unit file
David Reyna (1):
bitbake: toaster: Enable Gatesgarth branch in place of Zeus
Douglas Royds (1):
externalsrc: No single-task lock if S != B
Joshua Watt (2):
ref-variables: Given example for naming sources
ref-manual: Document wic --offset option
Khairul Rohaizzat Jamaluddin (1):
imagefeatures: New test case, test_empty_image, added
Khem Raj (5):
autotools.bbclass: Order CONFIG_SHELL before CACHED_CONFIGUREVARS
boost: Fix build on 32-bit arches with 64bit time_t only
mesa: Fix build on 32bit arches supporting 64bit time_t only
packagegroup-core-tools-debug: Disable for rv32/glibc as well
packagegroup-core-tools-profile: Remove lttng-tools and perf for rv32/glibc
Konrad Weihmann (1):
lib/oe/rootfs: introduce IMAGE_LOG_CHECK_EXCLUDES
Lee Chee Yang (2):
libproxy: fix CVE-2020-25219
grub2: fix CVE-2020-10713
Martin Jansa (11):
tune-cortexa76ae.inc: Correct TUNE_FEATURES
arch-armv7a.inc: fix typo
arch-mips.inc: remove duplicated mips64el-o32 from PACKAGE_EXTRA_ARCHS_tune-mips64el-o32
arch-arm64.inc: don't append _be to ARMPKGARCH for tune-aarch64_be
tune-mips64r6.inc: fix typo in mipsisa64r6-nf
tune-ep9312.inc: add t suffix for thumb to PACKAGE_EXTRA_ARCHS_tune-ep9312
tune-riscv.inc: use nf suffix also for TUNE_PKGARCH
tune-supersparc.inc: remove
tune-thunderx.inc: don't append _be to ARMPKGARCH for tune-thunderx_be
siteinfo: Recognize 32bit PPC LE
siteinfo: Recognize bigendian sh3be and sh4be
Max Krummenacher (2):
linux-firmware: package marvel sdio 8997 firmware
linux-firmware: package nvidia firmware
Mingli Yu (1):
tcl: adapt to potential pseudo changes
Naoki Hayama (1):
dev/test/ref-manual: Fix typos
Neil Armstrong (1):
linux-firmware: add Amlogic VDEC firmware package
Nicolas Dechesne (4):
sdk-manual: use built-in footnotes
dev-manual/dev-manual-common-tasks: fix warning
sphinx: add 3.1.3 and 3.0.4 release in the switcher
dev-manual/dev-manual-common-tasks: fix typos and use extlinks
Paul Eggleton (2):
classes/buildhistory: record SRC_URI
classes/buildhistory: also save recipe info for native recipes
Quentin Schulz (17):
docs: poky.yaml: use HTTPS for links
docs: ref-manual: indentation, links and highlights fixes
docs: remove OE_INIT_FILE variable
docs: ref-manual: fix typos
docs: ref-manual: migration-2.3: specify 2.3 version instead of DISTRO
docs: ref-manual: ref-classes: remove dropped tinderclient class
docs: ref-manual: ref-system-requirements: update requirements to build Sphinx docs
docs: sphinx: yocto-vars: rebuild files when poky.yaml has changed
docs: poky.yaml: fix identation in host packages variables
docs: dev-manual-common-tasks: remove paragraph about race when missing DEPENDS
docs: dev-manual-common-tasks: update python webserver example to python3
docs: dev-manual: fix typos, highlights, indentation and links
docs: ref-manual: ref-terms: add links to terms in glossary
docs: bsp-guide: bsp: fix typos, highlights and links
docs: kernel-dev: fix typos, highlights and links
docs: kernel-dev-common: add .patch file extension to SRC_URI files
docs: kernel-dev-faq: update outdated RDEPENDS_kernel-base
Reyna, David (1):
bitbake: toaster: Update documentation links to new URLs
Richard Purdie (10):
layer.conf: Switch to gatesgarth only in preparation for release
bitbake: ui/toasterui: Fix startup faults from incorrect event sequencing
bitbake: bitbake: Bump version to 1.48.0 ready for the new release
oeqa: Add sync call to command execution
poky.conf: Bump version for 3.2 gatesgarth release
build-appliance-image: Update to master head revision
bitbake: tests/fetch: Update upstream master->main branchname transition
Revert "classes/buildhistory: also save recipe info for native recipes"
valgrind: Fix build on musl after drd fixes
build-appliance-image: Update to master head revision
Robert Yang (1):
weston: Fix PACKAGECONFIG for remoting
Roland Hieber (1):
devtool: make sure .git/info exists before writing to .git/info/excludes
Ross Burton (4):
waf: don't assume the waf intepretter is good
waf: add ${B} to do_configure[cleandirs]
scripts/install-buildtools: Update to 3.2 M3 buildtools
glib-2.0: fix parsing of slim encoded tzdata
Sourabh Banerjee (1):
layer.conf: fix sanity error for PATH variable in extensible SDK workflow
Stacy Gaikovaia (2):
valgrind: drd: fix pthread intercept test failures
bitbake: main: Handle cooker daemon startup error
Tim Orling (1):
bitbake: lib/bb/ui/knotty: fix typo in parseprogress
Victor Kamensky (3):
Revert "qemumips: use 34Kf-64tlb CPU emulation"
Revert "qemu: add 34Kf-64tlb fictitious cpu type"
qemu: change TLBs number to 64 in 34Kf mips cpu model
Yi Zhao (1):
dhcpcd: add PACKAGECONFIG for ntp/chrony/ypbind hooks
Zang Ruochen (1):
harfbuzz: Refresh patch
akuster (2):
busybox: add rev and pgrep
kea: add init scripts
leimaohui (1):
docs: Updated the status of spdx module.
zangrc (1):
classes: Fixed the problem of undefined variables when compiling meta-toolchain.
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: Ic45bc219b94960751896a0ae3d4923a9f5849e70
Diffstat (limited to 'poky/documentation/dev-manual/dev-manual-start.rst')
-rw-r--r-- | poky/documentation/dev-manual/dev-manual-start.rst | 79 |
1 files changed, 32 insertions, 47 deletions
diff --git a/poky/documentation/dev-manual/dev-manual-start.rst b/poky/documentation/dev-manual/dev-manual-start.rst index 333c6a566..a85b86fbf 100644 --- a/poky/documentation/dev-manual/dev-manual-start.rst +++ b/poky/documentation/dev-manual/dev-manual-start.rst @@ -88,12 +88,10 @@ particular working environment and set of practices. .. note:: For information about BitBake, see the - BitBake User Manual - . + :doc:`bitbake:index`. It is relatively easy to set up Git services and create - infrastructure like - :yocto_git:`http://git.yoctoproject.org <>`, which is based on + infrastructure like :yocto_git:`/`, which is based on server software called ``gitolite`` with ``cgit`` being used to generate the web interface that lets you view the repositories. The ``gitolite`` software identifies users using SSH keys and allows @@ -106,10 +104,7 @@ particular working environment and set of practices. However, sites such as the following exist that describe how to perform setup: - - `Git documentation <http://git-scm.com/book/ch4-8.html>`__: - Describes how to install ``gitolite`` on the server. - - - `Gitolite <http://gitolite.com>`__: Information for + - `Gitolite <https://gitolite.com>`__: Information for ``gitolite``. - `Interfaces, frontends, and @@ -161,8 +156,7 @@ particular working environment and set of practices. integration" style testing of software components and regression identification and tracking. - See "`Yocto Project - Autobuilder <http://autobuilder.yoctoproject.org>`__" for more + See ":yocto_ab:`Yocto Project Autobuilder <>`" for more information and links to buildbot. The Yocto Project team has found this implementation works well in this role. A public example of this is the Yocto Project Autobuilders, which the Yocto Project team @@ -207,8 +201,7 @@ particular working environment and set of practices. .. note:: - You can also use a more collective push model. The - gitolite + You can also use a more collective push model. The ``gitolite`` software supports both the push and pull models quite easily. As with any development environment, it is important to document the @@ -285,11 +278,10 @@ v2 (WSL). .. note:: The Yocto Project is not compatible with - Windows Subsystem for Linux v1 - . It is compatible but not officially supported nor validated with + `Windows Subsystem for Linux v1 <https://en.wikipedia.org/wiki/Windows_Subsystem_for_Linux>`__. + It is compatible but not officially supported nor validated with WSLv2. If you still decide to use WSL please upgrade to - WSLv2 - . + `WSLv2 <https://docs.microsoft.com/en-us/windows/wsl/install-win10>`__. Once your build host is set up to use the Yocto Project, further steps are necessary depending on what you want to accomplish. See the @@ -453,9 +445,9 @@ as your Yocto Project build host: Once you have a container set up, everything is in place to develop just as if you were running on a native Linux machine. If you are going to -use the Poky container, see the "`Cloning the ``poky`` -Repository <#cloning-the-poky-repository>`__" section. If you are going -to use the Extensible SDK container, see the +use the Poky container, see the +":ref:`dev-manual/dev-manual-start:cloning the \`\`poky\`\` repository`" +section. If you are going to use the Extensible SDK container, see the ":doc:`../sdk-manual/sdk-extensible`" Chapter in the Yocto Project Application Development and the Extensible Software Development Kit (eSDK) manual. If you are going to use the Toaster container, see @@ -566,10 +558,7 @@ your Yocto Project build host: The current implementation of WSLv2 does not have out-of-the-box access to external devices such as those connected through a USB - port, but it automatically mounts your - C: - drive on - /mnt/c/ + port, but it automatically mounts your ``C:`` drive on ``/mnt/c/`` (and others), which you can use to share deploy artifacts to be later flashed on hardware through Windows, but your build directory should not reside inside this mountpoint. @@ -623,11 +612,8 @@ Use the following procedure to locate the latest upstream copy of the .. note:: - For information on cloning a repository, see the " - Cloning the - poky - Repository - " section. + For information on cloning a repository, see the + ":ref:`dev-manual/dev-manual-start:cloning the \`\`poky\`\` repository`" section. Accessing Index of Releases --------------------------- @@ -653,12 +639,10 @@ Follow these steps to locate and download a particular tarball: .. note:: - The - yocto - directory contains the full array of released Poky tarballs. The - poky - directory in the Index of Releases was historically used for very - early releases and exists now only for retroactive completeness. + The ``yocto`` directory contains the full array of released Poky + tarballs. The ``poky`` directory in the Index of Releases was + historically used for very early releases and exists now only for + retroactive completeness. 2. *Select a Component:* Click on any released component in which you are interested (e.g. ``yocto``). @@ -702,8 +686,7 @@ Releases <#accessing-index-of-releases>`__" section. .. note:: For a "map" of Yocto Project releases to version numbers, see the - Releases - wiki page. + :yocto_wiki:`Releases </wiki/Releases>` wiki page. You can use the "RELEASE ARCHIVE" link to reveal a menu of all Yocto Project releases. @@ -825,8 +808,9 @@ and then specifically check out that development branch. 1. *Switch to the Poky Directory:* If you have a local poky Git repository, switch to that directory. If you do not have the local - copy of poky, see the "`Cloning the ``poky`` - Repository <#cloning-the-poky-repository>`__" section. + copy of poky, see the + ":ref:`dev-manual/dev-manual-start:cloning the \`\`poky\`\` repository`" + section. 2. *Determine Existing Branch Names:* :: @@ -854,13 +838,13 @@ and then specifically check out that development branch. &DISTRO; Release (&DISTRO_NAME;), use the following command: :: - $ git checkout -b &DISTRO_NAME; origin/&DISTRO_NAME; - Branch &DISTRO_NAME; set up to track remote branch &DISTRO_NAME; from origin. - Switched to a new branch '&DISTRO_NAME;' + $ git checkout -b &DISTRO_NAME_NO_CAP; origin/&DISTRO_NAME_NO_CAP; + Branch &DISTRO_NAME_NO_CAP; set up to track remote branch &DISTRO_NAME_NO_CAP; from origin. + Switched to a new branch '&DISTRO_NAME_NO_CAP;' - The previous command checks out the "&DISTRO_NAME;" development + The previous command checks out the "&DISTRO_NAME_NO_CAP;" development branch and reports that the branch is tracking the upstream - "origin/&DISTRO_NAME;" branch. + "origin/&DISTRO_NAME_NO_CAP;" branch. The following command displays the branches that are now part of your local poky repository. The asterisk character indicates the branch @@ -868,8 +852,8 @@ and then specifically check out that development branch. :: $ git branch - master * - &DISTRO_NAME; + master + * &DISTRO_NAME_NO_CAP; .. _checkout-out-by-tag-in-poky: @@ -889,8 +873,9 @@ similar to checking out by branch name except you use tag names. 1. *Switch to the Poky Directory:* If you have a local poky Git repository, switch to that directory. If you do not have the local - copy of poky, see the "`Cloning the ``poky`` - Repository <#cloning-the-poky-repository>`__" section. + copy of poky, see the + ":ref:`dev-manual/dev-manual-start:cloning the \`\`poky\`\` repository`" + section. 2. *Fetch the Tag Names:* To checkout the branch based on a tag name, you need to fetch the upstream tags into your local repository: |