summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* package_ipk: Parallelise ipk creationRichard Purdie2017-06-221-2/+18
| | | | | | | | | Allow the creation of ipks to happen in parallel, making best use of resources on multiprocessor systems. (From OE-Core rev: 07f6c0b464f0671bc39116317138e4ddf27bdae9) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* package_deb: Enable multithreaded package creationRichard Purdie2017-06-221-2/+18
| | | | | | | | | Allow the creation of debs to happen in parallel, making best use of resources on multiprocessor systems. (From OE-Core rev: dd540fba6c65fb74df014f5d9d2965078314a790) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* pseudo: Handle too many files deadlockRichard Purdie2017-06-222-0/+63
| | | | | | | | | | | | | | If we have large amounts of parallelism, pseudo can end up with too many open connections and will no longer accept further connections, hanging. This patch works around that by closing some clients, allowing turnover of connections and unblocking the system. The downside is a small but theoretical window of data loss. This is likely better than locking up entirely though. Discussions with Peter are onging about how we could better fix this. (From OE-Core rev: f3589f154dad1c92e599737623d392508810ae7e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ovmf: fix secureboot PACKAGECONFIG + OpenSSL updatePatrick Ohly2017-06-161-7/+6
| | | | | | | | | | | | | | | The recent ovmf update broke secureboot because upstream changed the way how openssl gets compiled into ovmf. It's now integrated directly into the ovmf build process, without having to patch it first. In addition, more recent OpenSSL releases are supported. 1.1.0e was explicitly mentioned in the ovmf commits and because the current 1.1.0f only has minor build enhancements, 1.1.0e is used here. (From OE-Core rev: 1d9a88f635549e68562de681e297b9270ad02d4e) Signed-off-by: Patrick Ohly <patrick.ohly@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* package_ipk: Clean up Source entry in ipk packagesRichard Purdie2017-06-161-4/+2
| | | | | | | | | | | | | | | | There is the potential for sensitive information to leak through the urls there and removing it brings this into the behavior of the other package backends since filtering it is likely error prone. Since ipks don't appear to be generated at all if we don't set this, set the field to the recipe name used (basename only, no paths). This avoids information leaking. We may want to drop the field if opkg can allow that at a future point but the recipe name is a suitable identifier for now. Reported-by: Andrej Valek <andrej.valek@siemens.com> (From OE-Core rev: ec7feb9d315f357b9a073425a31b352ec24ddfd9) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake-user-manual: Updated BBLAYERS_FETCH_DIR variable descriptionScott Rifenbark2017-06-151-2/+0
| | | | | | | | | | | | | Just discovered a minor issue in the bitbake manual - under the variable glossary entry for BBLAYERS_FETCH_DIR we say there's a default value of ${COREBASE} but that's not actually true in bitbake itself - there's no default in bitbake, that default is set in OE-Core. We can keep this in the YP ref manual but in the bitbake manual that sentence should be removed. (Bitbake rev: 7b4e81772ed8789521661a3b32b576c91276ae34) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: cooker: ensure graceful exit after exception during BuildCompleted ↵2.4_M1Paul Eggleton2017-06-141-2/+4
| | | | | | | | | | | | | | | | handler If an event handler for bb.event.BuildCompleted fails, we still need to call finishAsyncCommand() or else BitBake will just exit immediately without showing any error summary, or worse in the case of memory resident mode BitBake will hang and if you Ctrl+C to break out, the command won't be marked as finished which means that no further commands will be able to be executed until the server is manually restarted. (Bitbake rev: 5639faa3eef55cc476a82e810e61ca228cbdf221) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: cooker: fix always loading cache on every UI start with memresPaul Eggleton2017-06-141-5/+12
| | | | | | | | | | | | | | | | | | | | | The main point of memory resident bitbake is to avoid loading data unnecessarily on every bitbake invocation. Unfortunately the code that updated options from the UI was simply treating the fact that either of the "prefile" or "postfile" options were in the list of options passed in as an indication that the configuration was invalid, which was bad because these are always passed in. We only need to mark the configuration as invalid and thus reload it (and thus reload the cache) if the option value has actually changed. At the same time, the recently handled "tracking" option needs to be treated in a similar manner since the configuration needs to be reparsed if that has changed. Also, add a few extra debug messages to aid debugging this code in future. (Bitbake rev: 18dfd144d0da6ff662308ce4f9d135dc11412133) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake: runqueue: multiconfig fixJuro Bystricky2017-06-141-1/+1
| | | | | | | | | | Differentiate between fn and taskfn in "execute". This was somehow missed in "fakeroot" handling. (Bitbake rev: d848bff7cf78f63986467b51f701a998a480eb25) Signed-off-by: Juro Bystricky <juro.bystricky@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake:process: flush stderr/stdout to logJuro Bystricky2017-06-141-36/+43
| | | | | | | | | | | | | | | | | When a process terminates, some messages may still remain in stdout or stderr and do not make it into the log file. In addition, the messages that do make it to the log file may end up in the log file in incorrect order. This patch flushes all messages into the log file after the process terminates. Some additional log flushing is also needed to keep the various messages showing up in the log file in proper order. [YOCTO#10785] (Bitbake rev: 1f6e6aa8262369eafc3bbf9f01f8d981f90becdf) Signed-off-by: Juro Bystricky <juro.bystricky@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* mtools-native: fix Upstream-StatusEd Bartosh2017-06-141-1/+1
| | | | | | | | | This is OE-specific customisation so set the status as such. (From OE-Core rev: 059846662f1ea1c82804cfce5f91afcb2980ec8a) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* package_manager: flush installed_pkgs file before oe-pkgdata-util uses itMartin Jansa2017-06-141-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | * since this commit: commit f5a1013ffa9815f22e13989e2bcb83f966e7ce2c Author: Ross Burton <ross.burton@intel.com> Date: Tue Apr 18 16:19:12 2017 +0100 package_manager: don't race on a file when installing complementary packages the file isn't closed before oe-pkgdata-util uses it and this temporary file might look empty to oe-pkgdata-util, because it wasn't flushed yet. Which resulted in almost empty debugfs tarballs and no locale packages in regular rootfs. * without this change: 124K May 30 07:41 core-image-full-cmdline-raspberrypi3-64-20170530054003-dbg.rootfs.tar.gz * with this change: 173M May 30 07:29 core-image-full-cmdline-raspberrypi3-64-20170530052715-dbg.rootfs.tar.gz (From OE-Core rev: 877d38db08aa7060d16405443cf70539c559fe82) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* distrooverrides.bbclass: DISTRO_FEATURES as overridesPatrick Ohly2017-06-141-0/+32
| | | | | | | | | | | | | | | | | | | | | | | | This achieves the same goal as the same change to bitbake.conf itself, but because the class gets added later as part expanding INHERIT, this new approach is less likely to run into problems when DISTRO_FEATURES contains complex code. Another difference is that the class currently does not get inherited by default and thus is completely absent from a build unless some layer or include file adds it to INHERIT. Compared to the earlier code in bitbake.conf and a similar class in intel-iot-refkit, additional overrides now get sorted. This makes the final OVERRIDES more deterministic. The lessons learned about unintentionally depending on OVERRIDES are documented in the class because such problems are more likely to show up as unexpected signature differences when using this class. (From OE-Core rev: e982ca7f2d4fb0aef3fedc00af1e90f613e7b5ee) Signed-off-by: Patrick Ohly <patrick.ohly@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Revert "bitbake.conf: DISTRO_FEATURES as overrides"Patrick Ohly2017-06-141-16/+1
| | | | | | | | | | | | | | | | This reverts commit 3b3ae91a22d6f685e804df4f32cdeebe1bd6bd88. It turned out that the code which expands DISTRO_FEATURES early during base config parsing can fail because some entries in DISTRO_FEATURES might call Python functions like base_conditional() from base.bbclass which aren't defined yet. A different solution will be needed. (From OE-Core rev: 0c6e4a14ba8d9d9701ec16ffe46d618f41633571) Signed-off-by: Patrick Ohly <patrick.ohly@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python-3.5: Move bz2.py, lzma.py and _compression.py from python3-misc to ↵Martin Jansa2017-06-142-5/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | python3-compression * the /usr/lib/python3.5/_compression.py file is possibly incorrectly included in python3-misc. This runtime dependency is needed in order to use e.g. gzip.py in runtime: >>> import tarfile, zlib, gzip Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/lib/python3.5/gzip.py", line 12, in <module> import _compression ImportError: No module named '_compression' * at least python3-tests and lzma and bz2 still in python3-misc are using this as well: $ grep -R import.*_compression tmp-glibc/work/aarch64-oe-linux/python3/3.5.2-r1.0/packages-split/ tmp-glibc/work/aarch64-oe-linux/python3/3.5.2-r1.0/packages-split/python3-compression/usr/lib/python3.5/gzip.py:import _compression tmp-glibc/work/aarch64-oe-linux/python3/3.5.2-r1.0/packages-split/python3-misc/usr/lib/python3.5/lzma.py:import _compression tmp-glibc/work/aarch64-oe-linux/python3/3.5.2-r1.0/packages-split/python3-misc/usr/lib/python3.5/bz2.py:import _compression tmp-glibc/work/aarch64-oe-linux/python3/3.5.2-r1.0/packages-split/python3-tests/usr/lib/python3.5/test/test_bz2.py:import _compression tmp-glibc/work/aarch64-oe-linux/python3/3.5.2-r1.0/packages-split/python3-tests/usr/lib/python3.5/test/test_lzma.py:import _compression and python3-tests are using it as well, so add new runtime dependency on python3-compression (From OE-Core rev: 987363c3c720b3764f4d64976d7455f6b0bae99c) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* attr: Fix build failure when image includes man-pages pkgMark Asselstine2017-06-143-0/+908
| | | | | | | | | | | | | | | | | | | | | | | | If you attempt to build an image with both attr(-doc) and man-pages packages your rootfs might fail to assemble. The error will be something like: Error: Transaction check error: file /usr/share/man/man2/fgetxattr.2 from install of \ attr-doc-2.4.47-r0.core2_64 conflicts with file from \ package man-pages-4.11-r0.core2_64 (the error is usually only seen on builders which don't have manpages installed, if you have /usr/share/man/man1/man.1.gz your build will complete but you will have duplicate manpages, just one zipped and one not) Backporting changes from upstream attr removes the conflicted files in favour of those in the man-pages package. (From OE-Core rev: 5e6595ef42807c8d2a100da3d9862152daf68d3d) Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* externalsrc: verify that EXTERNALSRC/EXTERNALSRC_BUILD are absolute pathsRoss Burton2017-06-141-1/+6
| | | | | | | | | If these are set to URLs then the errors produced are not helpful. (From OE-Core rev: 946b6623154e748a0d75ff498802a720aeec27a6) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* adwaita-icon-theme: add a patch to speed up the do_install() taskAlexander Kanavin2017-06-142-1/+84
| | | | | | | | | | | | | Goes down to 40 seconds from over 4 minutes :) Note that there is no control over the amount of shell jobs; on my machine this is not a problem, but if it's a problem on less capable hardware, we can add some kind of limiter. (From OE-Core rev: cd9af17028c069f52fb0616074170093dd63c143) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* runqemu: change terminal settings for valid tty'sMikko Ylinen2017-06-141-5/+5
| | | | | | | | | | | | | | | | | | | | | | | | runqemu uses stty to change terminal settings to give users better control to qemu. However, stty does not work when runqemu is run directly or indirectly via oe-selftest in a Docker container (presumably some problems with Docker's pseudo-tty implementation). The error reported is: stty: 'standard input': Inappropriate ioctl for device As runqemu recently moved to subprocess.check_call() for stty calls we now get thrown an error and all runqemu runs fail. sys.stdin.isatty() does proper job in detecting if the stty calls can work so we use that check before running the stty subprocess operations. (From OE-Core rev: 06742ed59092530aedf03f65c3c9542c24ff7ac3) Signed-off-by: Mikko Ylinen <mikko.ylinen@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* grub: switch from ftp to httpsMaxin B. John2017-06-141-1/+1
| | | | | | | | | | For the same reasons as Debian: https://www.debian.org/News/2017/20170425 (From OE-Core rev: 3a603a805ff3495ac9b8431acbf698757a28d32d) Signed-off-by: Maxin B. John <maxin.john@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libid3tag: switch from ftp to httpMaxin B. John2017-06-141-1/+1
| | | | | | | | | | For the same reasons as Debian: https://www.debian.org/News/2017/20170425 (From OE-Core rev: 134151fbf3ade16f1175002c76028adeb2426354) Signed-off-by: Maxin B. John <maxin.john@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libglu: switch from ftp to httpsMaxin B. John2017-06-141-1/+1
| | | | | | | | | | For the same reasons as Debian: https://www.debian.org/News/2017/20170425 (From OE-Core rev: 057bcb34b9cd7b52932320206132ab381f00c674) Signed-off-by: Maxin B. John <maxin.john@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* mesa: switch from ftp to httpsMaxin B. John2017-06-141-1/+1
| | | | | | | | | | For the same reasons as Debian: https://www.debian.org/News/2017/20170425 (From OE-Core rev: ca626abbe1883bce6ebc1d2b86d4efb74e31ec8e) Signed-off-by: Maxin B. John <maxin.john@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* mesa-demos: switch from ftp to httpsMaxin B. John2017-06-141-1/+1
| | | | | | | | | | For the same reasons as Debian: https://www.debian.org/News/2017/20170425 (From OE-Core rev: 31a6e2dca7c22420d981bca199299c4457e3c3d2) Signed-off-by: Maxin B. John <maxin.john@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dhcp: switch from ftp to httpMaxin B. John2017-06-141-1/+1
| | | | | | | | | | For the same reasons as Debian: https://www.debian.org/News/2017/20170425 (From OE-Core rev: 95a83b81421e07b5daa42c2311f8f5fce859c391) Signed-off-by: Maxin B. John <maxin.john@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libpcre: switch from ftp to httpsMaxin B. John2017-06-141-1/+1
| | | | | | | | | | For the same reasons as Debian: https://www.debian.org/News/2017/20170425 (From OE-Core rev: 1127af1eddf2cb49b1fbef473a20ae9b446b8369) Signed-off-by: Maxin B. John <maxin.john@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* image.bbclass: fix setting of vardeps flagEd Bartosh2017-06-141-1/+1
| | | | | | | | | | Added leading space to vardeps to avoid flag value to be added to the existing value without a separator. (From OE-Core rev: f582773c2b1e8db441f397867d3c9665fd265cec) Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* image.bbclass: improve setup of flagsEd Bartosh2017-06-141-3/+4
| | | | | | | | | | | | | Replaced setVarFlag calls to appendVarFlag to allow modification of prefuncs, postfuncs and subimages flags in inherited image classes. [YOCTO #11372] (From OE-Core rev: 6690f3ab43c04fa7cff7215d4a5d8d639e41aed8) Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* image.bbclass: cleanup: add new variable "task"Ed Bartosh2017-06-141-13/+13
| | | | | | | | | | | Replaced repeated expression "do_image_%s" % t with a variable 'task' to simplify the code and increase readability. (From OE-Core rev: d24dd95f2c1c7f773875454bee3f2016c4e7553c) Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* staging.bbclass: fix typoChen Qi2017-06-141-1/+1
| | | | | | | | | The function is "sysroot_strip" instead of "split_and_strip_files". (From OE-Core rev: f2d349887710dcae05db09dc2277223e85fa1c19) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* connman: correct the systemd boot in read only rootfsMaxin B. John2017-06-143-1/+44
| | | | | | | | | | | | | | | | | connman fails to start in systemd based read-only images while creating links: Jun 08 12:53:56 qemux86-64 systemd[1]: Starting Create Volatile Files and Directories... Jun 08 12:53:56 qemux86-64 systemd-tmpfiles[366]: [[0;1;31msymlink(/var/run/connman/resolv.conf, /etc/resolv.conf) failed: Read-only file system[[0m Fix this failure and make connman co-exist with systemd-resolved. (From OE-Core rev: 732e1f74bb9f5ecc98b29197f6bcab117710adab) Signed-off-by: Maxin B. John <maxin.john@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* systemd: enable resolved and networkdMaxin B. John2017-06-141-3/+10
| | | | | | | | | | | | | Enable systemd-resolved and systemd-networkd by default. Make it co-exist with connman and Fix associated problems in read-only rootfs. Fixes [YOCTO #11331] (From OE-Core rev: d9b6d538e3d81ab0d5e7b7b6adecef555d782217) Signed-off-by: Maxin B. John <maxin.john@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* selftest/sstatetests: Fix potential failure on uniprocessor machinesRichard Purdie2017-06-141-1/+1
| | | | | | | | It was pointed out +1 is safer than -1 for systems with one processor. (From OE-Core rev: 78041e20e43d9583448ff31f8b9b1c6157da8625) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto: remove user-specific description/config files from machine ↵Leonardo Sandoval2017-06-148-16/+0
| | | | | | | | | | | | | | | | description Remove user-specific descrition files and config fragments from main machine description file otherwise double patch/config inclusion may happen. These files/fragments are already included on the SRC_URI (see poky commit 2db8f3), so no need to reference these inside machine.scc files. [YOCTO #11586] (From meta-yocto rev: 86ab7ab6688f250bb5777371d2cbc28c770847d4) Signed-off-by: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc_7.1.bb: disable thumb on armv5tKhem Raj2017-06-141-1/+2
| | | | | | | | | It results in same link errors like armv4t (From OE-Core rev: 7fb9648f7a055beef9c8a735850b1b51fd23ff1d) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Add recipes for gcc-7Khem Raj2017-06-1466-5/+7242
| | | | | | | | | Switch default compiler to gcc 7 (From OE-Core rev: 03bb12008891cf1a023aaddb6547da6d41d0cab0) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ovmf: Update to latestKhem Raj2017-06-145-60/+72
| | | | | | | | | | | | Fix build with gcc7 clang can not compile it therefore mark it gcc only recipe (From OE-Core rev: 835b705ee92900f0d73cee612ce790fde4b1e2a4) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dev-manual, ref-manual: Reorganized "Other Information"Scott Rifenbark2017-06-143-230/+274
| | | | | | | | | | | | | | | Fixes [YOCTO #11630] The exhaustive list of useful links and references to other YP documentation existed in the dev-manual. This is not the correct place for this type of reference information. I have moved that list to the ref-manual where it should be. The dev-manual now simply provides a link into that section. (From yocto-docs rev: eeceb597988134ced85aab4b9ddaeed923f17b03) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dev-manual, ref-manual: Reorganized Bugzilla informationScott Rifenbark2017-06-143-56/+114
| | | | | | | | | | | | | | | | | Fixes [YOCTO #11630] Reorganized the way the information about entering bugs using Bugzilla is arranged in the documentation set. The dev-manual now has a section that is purely procedural and steps the user through the process of logging a new bug in the Bugzilla system. The ref-manual has a conceptual section that introduces the YP implementation of Bugzilla by simply telling the user what it is and what what its purpose is. (From yocto-docs rev: 4bfba345010be7bc2866b819b9754bb06f93c91f) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dev-manual: Corrected grammar errorKristi Rifenbark2017-06-141-1/+1
| | | | | | | (From yocto-docs rev: 0d432a6890316207f93c149b865d4a9fc020bfa0) Signed-off-by: Kristi Rifenbark <kristi.rifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dev-manual: Edited grammar errorKristi Rifenbark2017-06-141-1/+1
| | | | | | | (From yocto-docs rev: d02aedcd3cf9e30d5d1633ee234af3fcb4a570e3) Signed-off-by: Kristi Rifenbark <kristi.rifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dev-manual: Edited intro para to devtool upgrade figureKristi Rifenbark2017-06-141-5/+2
| | | | | | | | | | The introductory paragraph for this figure was a cut/paste problem from previous devtool figures. (From yocto-docs rev: c02a2a57889bbdcd7e83ab9e2458397189bbb980) Signed-off-by: Kristi Rifenbark <kristi.rifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dev-manual, sdk-manual: Corrected grammar errorKristi Rifenbark2017-06-142-2/+2
| | | | | | | (From yocto-docs rev: ca0843e7651d25e37295094770ca3a97f9150bbc) Signed-off-by: Kristi Rifenbark <kristi.rifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dev-manual: Updated "Kernel Modification Workflow" config file locationKristi Rifenbark2017-06-141-2/+5
| | | | | | | | | | | Warning in step 5 indicated the wrong location for config file. Updated with new location and referenced an illustration to show an example. (From yocto-docs rev: e853e5b89f1dbd7399909064b50bc59e06302560) Signed-off-by: Kristi Rifenbark <kristi.rifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dev-manual: Removed last paragraph of BSP workflow section.Scott Rifenbark2017-06-141-13/+0
| | | | | | | | | | This paragraph had some links to old stuff. Removed the whole paragraph. (From yocto-docs rev: 95c1f348ed018c697cc996bc962787ede056b94b) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dev-manual, mega-manual: Updated kernel overview tree structure figureScott Rifenbark2017-06-142-0/+0
| | | | | | | | | | | This figure was a bit out of date. I updated a few of the file names. Figure needs to reside in the Figures folder of both the dev-manual and the mega-manual. (From yocto-docs rev: 1e76477810b6be095f9ca190c9a8f0276ee4b8f9) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dev-manual: Slight wording change to be clear.Scott Rifenbark2017-06-141-1/+2
| | | | | | | (From yocto-docs rev: f8b0f3e01249ab94520137ecc60dcc08620a2a96) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dev-manual: changed git configuration file nameScott Rifenbark2017-06-141-1/+1
| | | | | | | | | I changed the git config file to ~/.gitconfig (From yocto-docs rev: 0d4f43944b911ee23dd03b5f503173478d6c396d) Signed-off-by: Scott Rifenbark <scottrif@buzzcollectivemarketing.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dev-manual: Formed ordered list for email patch procedureScott Rifenbark2017-06-141-54/+83
| | | | | | | | | | | The section that describes how to create a patch and send it via email is really an ordered procedure. I recast the list of steps using numbers instead of bullets. (From yocto-docs rev: c2d2256ca6d8c8b837bae87a5bd8a3118553935c) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Updated PACKAGECONFIG_CONFARGS variableScott Rifenbark2017-06-141-18/+0
| | | | | | | | | | | Fixes [YOCTO #11600] Removed the example. It was not needed. (From yocto-docs rev: 402bb173b00a665fb55a8f740a4dbe60ead57f25) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-11-18 03:24:24 +0000