summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* at: fix configure option with/without-selinuxWenzong Fan2016-03-252-0/+54
| | | | | | | | | | | | | | | | without-selinux doesn't work since WITH_SELINUX is always be defined no matter which option is given: with-selinux, without-selinux. This causes build errors if '--without-selinux' is used and libselinux is not buildable in project: atd.c:87:29: fatal error: selinux/selinux.h: No such file or directory (From OE-Core rev: f1f676cf720b869999553eecdb113a2a2daa61fe) Signed-off-by: Wenzong Fan <wenzong.fan@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* no-static-libs: just like target and native, nativesk-libcap doesn't like ↵Ross Burton2016-03-251-0/+1
| | | | | | | | | unrecognised options (From OE-Core rev: 79ec2ec397a35d6405f9c2b3c67e8b9981fbe7be) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-firmware: package firmware for Marvell 88W8688Jens Rehsack2016-03-251-1/+7
| | | | | | | | | | | | | | | | | | | | | | | | According to error messages from guruplug [ 35.826441] btmrvl_sdio mmc0:0001:2: Direct firmware load for mrvl/sd8688_helper.bin failed with error -2 [ 35.903291] Bluetooth: request_firmware(helper) failed, error code = -2 [ 35.909942] Bluetooth: Failed to download helper! [ 36.052820] Bluetooth: Downloading firmware failed! ... [ 764.422739] libertas_sdio: Libertas SDIO driver [ 764.438213] libertas_sdio: Copyright Pierre Ossman [ 764.461186] libertas_sdio mmc0:0001:1: Direct firmware load for libertas/sd8688_helper.bin failed with error -2 [ 764.488234] libertas_sdio mmc0:0001:1: Direct firmware load for sd8688_helper.bin failed with error -2 [ 764.507382] libertas_sdio: failed to find firmware (-2) and http://wiki.beyondlogic.org/index.php?title=GuruPlug_Libertas_SD8688, package the firmware files for Marvell 88W8688, too. (From OE-Core rev: 5a5a6cab382e003cc5debb0b9af18d5f0ea3ce39) Signed-off-by: Jens Rehsack <sno@netbsd.org> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tune-arm926ejs: Handle missing thumb suffixJens Rehsack2016-03-251-1/+1
| | | | | | | | | | | | When enabling tune for arm926ejs, poky optionally appends suffixes for thumb and dsp support. Since sometimes arm926ejse (ARM code) and sometime arm926ejste (thumb code) is used in PACKAGE_ARCH, allow both. (From OE-Core rev: dbd7fd1cbbc3e7003a48542642acdc80dca3f514) Signed-off-by: Jens Rehsack <sno@netbsd.org> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* nativesdk-coreutils: a lot of warnings fixedDengke Du2016-03-251-1/+2
| | | | | | | | | | | | | | | | | | | When we create nativesdk-coreutils, a lot of warnings appear,it show many files can't find. Because in the coreutils recipe, it didn't contain the do_install for the nativesdk, so when the alternative system check the files in the following process, it can't find the files. So we should add the do_install for the nativesdk, change the function do_install_append_class-target() to do_install_append() in the file: meta/recipes-core/coreutils/coreutils_8.25.bb in this way, the alternative system can find the files, the warnings disappear. (From OE-Core rev: 37039da6a09d7781beb93892932488940786b41f) Signed-off-by: Dengke Du <dengke.du@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* runqemu-internal: split the code into functionsRobert Yang2016-03-251-91/+89
| | | | | | | | | | | Use config_<machine> to split the code into separate functions, so that different machines won't affect each other, and they will have a better structure. (From OE-Core rev: 6098a72e8d21f6321636e727703ca7c29d9af142) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* runqemu-internal: cleanup unsed codeRobert Yang2016-03-252-46/+1
| | | | | | | | | | | | | | | | | | | * remove akita and spitz related code They are not supported by runqemu anymore: $ runqemu spitz Error: unable to classify arg [spitz] So remove related code. * Remove checking of 256M for qemuarm, qemu can check it, for example: $ runqemu qemuarm qemuparams="-m 1024" [snip] qemu: Too much memory for this machine: 1024 MB, maximum 256 MB [snip] (From OE-Core rev: 36fb785bf8cd2f387c91d52f597602a5dbc3948b) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* runqemu: simplify checking for iso and ramfsRobert Yang2016-03-252-8/+3
| | | | | | | (From OE-Core rev: 69a1fca4374797dea56035ce56a17441a2ca9280) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* runqemu: add support for qcow2 and vdiRobert Yang2016-03-251-4/+3
| | | | | | | | | [YOCTO #9168] (From OE-Core rev: 0f8306c77b4ebed1ff127b0786b7109abf0d57cd) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* runqemu: remove ISO and RAMFS from help textRobert Yang2016-03-251-2/+0
| | | | | | | | | They don't work, and the script can check the type correctly. (From OE-Core rev: b5cc1e70dbd5df160ddedcaa40d0ab714a307561) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* runqemu: simplify the checking for vm imagesRobert Yang2016-03-252-16/+28
| | | | | | | | | | * So that we can add more image support easliy. * I think that wic should be vm images. (From OE-Core rev: 82d0014a0e1526ffa1ff7c8ea3903aeae31bada4) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* runqemu: fix ROOTFS for vmdkRobert Yang2016-03-252-45/+61
| | | | | | | | | | | | | | | | | | | | * Make it can boot scsi and virtio block drive such as root=/dev/sdX and /dev/vdX. * Drop VM from help info, id doesn't work, and the script can check whether it is a vm disk or not. * Make it can be run by: $ runqemu tmp/deploy/images/qemux86-64/core-image-minimal-qemux86-64.vmdk or: $ runqemu qemux86-64 vmdk [YOCTO #9170] (From OE-Core rev: 88c081b10902ec52928be78ad320c474bb918e01) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python(3): Disable tkinterMartin Jansa2016-03-252-0/+28
| | | | | | | | | | | | | | | | | | | | | | | | | | | * restore changes from: http://git.openembedded.org/openembedded-core/commit/?id=53ae544cfdac22c82af452b8c7ebe6664296bd9b * which were shamelessly removed in upgrade to 2.7.9: http://git.openembedded.org/openembedded-core/commit/?id=d4ad95f0d5f08891637c644e85b09da9c4585059 and then spread to python3 as well * fixes following issues reported by test-dependencies WARN: python3: python3-tkinter rdepends on glibc, but it isn't a build dependency? WARN: python3: python3-tkinter rdepends on libpython3, but it isn't a build dependency? WARN: python3: python3-tkinter rdepends on tcl-lib, but it isn't a build dependency? WARN: python: python-tkinter rdepends on glibc, but it isn't a build dependency? WARN: python: python-tkinter rdepends on libpython2, but it isn't a build dependency? WARN: python: python-tkinter rdepends on tcl-lib, but it isn't a build dependency? and following QA warnings in normal builds: python-2.7.11: python-tkinter rdepends on tcl-lib, but it isn't a build dependency, missing tcl in DEPENDS or PACKAGECONFIG? [build-deps] python-2.7.11: /usr/lib/python2.7/lib-dynload/_tkinter.so contained in package python-tkinter requires libtk8.6.so, but no providers found in RDEPENDS_python-tkinter? [file-rdeps] python3-3.5.1: python3-tkinter rdepends on tcl-lib, but it isn't a build dependency, missing tcl in DEPENDS or PACKAGECONFIG? [build-deps] python3-3.5.1: /usr/lib/python3.5/lib-dynload/_tkinter.cpython-35m-arm-linux-gnueabi.so contained in package python3-tkinter requires libtk8.6.so, but no providers found in RDEPENDS_python3-tkinter? [file-rdeps] (From OE-Core rev: 8cc5e36cd7978186d5ea1fe8af2f2bd6b3df8885) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* selftest/signing.py: RPM_GPG_PASSPHRASE_FILE -> RPM_GPG_PASSPHRASERobert Yang2016-03-252-2/+1
| | | | | | | (From OE-Core rev: ce14964d99741f1a4579bae18da5013498c365fd) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gpg_sign.py: get rid of pexpectRobert Yang2016-03-252-22/+12
| | | | | | | | | | | | | The python-expect is not installed on the distro such as Ubuntu by default, and we can get rid of it. Use RPM_GPG_PASSPHRASE to replace of RPM_GPG_PASSPHRASE_FILE which is more straightforward. (From OE-Core rev: 4a8a74c62836a20610daf029d4cec0b3087758b2) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rpm: check _gpg_passphrase before ask for inputRobert Yang2016-03-252-0/+71
| | | | | | | | | | | | rpm always asked for pass phrasae when add signature, which made it can't work non-interactively, this patch fix the problem. It will work non-interactively if _gpg_passphrase is defined, and work as before if not. (From OE-Core rev: 3cd4f96e94d8756d332b13215ce3ac2e1eaddee7) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oe-publish-sdk: fix remote publishingPaul Eggleton2016-03-251-1/+1
| | | | | | | | | | A typo in the command prevented the last part of the publish from succeeding. (From OE-Core rev: 5d51bd1f02fb20e02d0de0ac9874d7f9a6f5ddc6) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oe-publish-sdk: improve help output slightlyPaul Eggleton2016-03-251-10/+16
| | | | | | | | | | | | | | This was just copy-and-pasted from devtool - set a reasonable description and tweak the sdk parameter help text. Also add a copyright statement and drop the opening comment describing the command-line syntax that duplicated the help output (with at least one mistake in it). (From OE-Core rev: b18f9cb62e12d068fb840fd7ab9f35b4f039e649) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oe-publish-sdk: drop SDK installer file from published outputPaul Eggleton2016-03-251-1/+5
| | | | | | | | | | | | | | | | | | | We don't really need the SDK installer in the published output, for two reasons: 1) The directory produced is for the consumption of devtool sdk-update, and the installer isn't used by that at all 2) It wouldn't really make sense to point users at the update directory to download the SDK installer because it contains a bunch of things that aren't meant for manual download, so it wouldn't be very tidy. Leaving the file present can mislead you into thinking the opposite of both of the above. (From OE-Core rev: a9ec72b7897ffc0b901c1ccbcbe3cabbc7ac41ee) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* devtool: add: create git repository if URL specified as positional argumentPaul Eggleton2016-03-252-1/+3
| | | | | | | | | | | | | | | When we add from a fetched URL we are supposed to turn the resulting source tree into a git repository (if it isn't already one). However, we were using the older deprecated option name here instead of the positional argument, so "devtool add -f <url>" resulted in the repo being created but "devtool add <url>" didn't, which was wrong. Also update the oe-selftest tests to check that this worked. (From OE-Core rev: a7b6b1f8cc1c096724f794ac9dee312b0f771f66) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* devtool: add: delete externalsrc files on npm recipe do_installPaul Eggleton2016-03-252-2/+15
| | | | | | | | | | | | | | The npm class just installs whatever is in ${S}; if you're using externalsrc in conjunction with it the symlinks (oe-workdir and oe-logs by default) plus singletask.lock will end up in the final package, which isn't really right. Introduce a variable so we know the path the files will be installed into within npm.bbclass, and append to do_install within the workspace bbappend to delete the files. (From OE-Core rev: 766845e06db9d7d595e836ea1364c16fa132a413) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* devtool: configure-help: fix error if do_configure not already runPaul Eggleton2016-03-251-1/+1
| | | | | | | | | | The code here for running do_configure if it hadn't already been run was using the wrong string substitution parameters; fix it and test it. (From OE-Core rev: b2677a4448dbc42e523c731b953b44006749252c) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: whitelist proxy variables in config hashPaul Eggleton2016-03-251-1/+3
| | | | | | | | | | | | | | | We don't need these variables incorporated in the config hash (i.e. we don't need to reparse if they change). This fixes an issue with the extensible SDK where the cache generated at installation time not to be used afterwards due to the way we're allowing through the proxy variables into the install environment (such that they get set to "" if not set externally). (From OE-Core rev: 3dc7c58b7b3224f3ed2d59d95313e70e4c57d7c4) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/populate_sdk_ext: parse metadata on minimal SDK installPaul Eggleton2016-03-252-4/+8
| | | | | | | | | | | | Instead of skipping the build system preparation step within the extensible SDK install process when SDK_EXT_TYPE is "minimal", run bitbake -p so that the cache is populated ready for the first time devtool is run. (From OE-Core rev: 6b38a991a3475fb82889428b94563968c7570473) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* devtool: sdk-install: add option to allow building from sourcePaul Eggleton2016-03-251-1/+20
| | | | | | | | | | | | | | By default the sdk-install subcommand expects to restore the requested items from sstate and fails if it can't. If the user is OK with building from source, add a -s/--allow-build option to allow them to do that. In the process, ensure we show the status output while we're installing. Also add the missing header to the top of the file. (From OE-Core rev: a86b426cdd465ec5cb08bb5fa7729e4e673d94bb) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/distutils*: don't hide logs when setup script failsPaul Eggleton2016-03-253-12/+12
| | | | | | | | | | | | We need to see the output of the setup script in the error message because what we are having bbfatal print here doesn't completely describe what went wrong, thus we should use bbfatal_log here and not bbfatal. (From OE-Core rev: 970a02061b474a238f57cd0cc4db7b62e36dfa3d) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/packagegroup: drop complementary -ptest if ptest not in DISTRO_FEATURESPaul Eggleton2016-03-251-1/+4
| | | | | | | | | | If ptest isn't in DISTRO_FEATURES, there won't be any -ptest packages and thus no need for the -ptest package for the packagegroup either. (From OE-Core rev: 52f9b12601c02f1585438f890f847b4596170362) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/packagegroup: fix dbg/dev/ptest complementary packagesPaul Eggleton2016-03-251-3/+6
| | | | | | | | | | | | | OE-Core commit 8981ed20234c42dc1f5cdef802ebe7214bd55238 (from 2013) caused a regression where -dbg/-dev/-ptest packages weren't generated for packagegroups because we weren't setting ALLOW_EMPTY for them. Break out the code for adding complementary groups to its own conditional so we can set ALLOW_EMPTY at the same time. (From OE-Core rev: 340e9d619c881f320070474d5c4674dcaeabad35) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake: xmlrpc: set single use mode differentlyEd Bartosh2016-03-243-7/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | Currently xmlrpc server implicitly sets itself into single use mode when bitbake server is started with anonymous port (0) or no port is provided in command line. In this mode bitbake shuts down xmlrpc server after build is done. This assumption is incorrect in some cases. For example Toaster uses bitbake in this mode and expects xmlrpc server to stay in memory. Till recent changes single use mode was always unset due to the bug. When the bug was fixed it broke toaster builds as Toaster couldn't communicate with bitbake server in single use mode. Reimplemented logic of setting single use mode. The mode is explicity set when --server-only command line parameter is not provided to bitbake. It doesn't depend on the port number anymore. [YOCTO #9275] [YOCTO #9240] [YOCTO #9252] (Bitbake rev: afc0dd5c532684f6201b1e12bbf4c226ea19062d) Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com> Signed-off-by: Elliot Smith <elliot.smith@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sdk-manual: Added note for running remote apps with SSH port forw enabled.Scott Rifenbark2016-03-231-0/+17
| | | | | | | | | | | | | | | | | | | | | | | | | | | I added the following note in the section that deals with running Eclipse with a remote application. Fixes [YOCTO #9276] Currently, Eclipse does not support SSH port forwarding. Consequently, if you need to run or debug a remote application using the host display, you must create a tunneling connection from outside Eclipse and keep that connection alive during your work. For example, in a new terminal, run the following: ssh -XY user_name@remote_host_ip After running the command, add the command to be executed in Eclipse's run configuration before the application as follows: export DISPLAY=:10.0 (From yocto-docs rev: 7bf2875ff1653a8e50fa8e2bba540b2eb2512d2d) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* poky.ent: Added code name for 2.1 release to the variableScott Rifenbark2016-03-231-1/+1
| | | | | | | | | Krogoth (From yocto-docs rev: 619c704632e9316d4953fbccab0416460cdc9a00) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sdk-manual: Applied more review edits to the manual per Eggleton.Scott Rifenbark2016-03-232-12/+40
| | | | | | | (From yocto-docs rev: 8987852ad23e8a4694be55425e2c76bcd4301850) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Created distrodata and checkpkg tasks, updated distrodata classScott Rifenbark2016-03-232-1/+66
| | | | | | | | | | | | | Fixes [YOCTO #7894] I created two new task reference sections: distrodata and checkpkg. Also, updated the distrodata class description to reflect the presence of these new tasks. (From yocto-docs rev: 3896cbf640d296dafb5eda37f89bba31a47ca8a5) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sdk-manual: Applied 2nd round of review edits.Scott Rifenbark2016-03-233-25/+10
| | | | | | | (From yocto-docs rev: 046b8ed69e0c6403f455e2ec8a0ccc30aea894de) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sdk-manual: Applied review edits to the manual.Scott Rifenbark2016-03-235-475/+498
| | | | | | | (From yocto-docs rev: be853fb74b28bcf1b27b3b7a8e83012928d4e53a) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sdk-manual: Updated the SDK devtool modify flow diagram.Scott Rifenbark2016-03-231-0/+0
| | | | | | | (From yocto-docs rev: 0fa48508dc6da53f4611d41fee9aa946de6cf07b) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dev-manual: Fixed a grammar errorScott Rifenbark2016-03-231-1/+1
| | | | | | | (From yocto-docs rev: 7b81f29a641cad4f10c3c721c0d40ce11d928648) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sdk-manual, mega-manual: Updated the SDK devtool modify diagramScott Rifenbark2016-03-231-0/+0
| | | | | | | | | Removed the bitbake option and the TMPDIR terminology. (From yocto-docs rev: c543e00eeb9e9a8074dfb195c971c37c095ecbdd) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dev-manual, profile-manual, ref-manual: Updates to remove meta-toolchainScott Rifenbark2016-03-237-16/+16
| | | | | | | | | | | The term "meta-toolchain" is legacy now. I went through and removed its use except for where it appears still as output from the oe-init-build-env script. (From yocto-docs rev: 1cc134060459278997d57f1293f54091c5404d85) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sdk-manual: Edits to add extensible SDK configuration sections.Scott Rifenbark2016-03-234-101/+506
| | | | | | | (From yocto-docs rev: 378bbceb8ea06c225c4758807e25a35521faa3a9) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual, sdk-manual: Changed section heading.Scott Rifenbark2016-03-236-9/+9
| | | | | | | | | | | Changed the heading for "Optionally Building a Toolchain Installer" to "Building an SDK Installer". This changes the heading and many references to that heading. (From yocto-docs rev: 97d8cd34d0dd0993b1b1135bb75f2212bb46878a) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Added some SDK manual support to introductionScott Rifenbark2016-03-231-7/+14
| | | | | | | (From yocto-docs rev: 6021a1024b51ab65659e132870eb75d1bf53aedb) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* profile-manual: Updated screen output for oe-init-build-envScott Rifenbark2016-03-231-9/+1
| | | | | | | (From yocto-docs rev: 36029fbcb03487ece65c7c43d9bf1bf20b4fc308) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kernel-dev: Changed a link from an example to in-text.Scott Rifenbark2016-03-231-3/+4
| | | | | | | | | | Better placement of this link. It did not need to be in the <literallayout> example. (From yocto-docs rev: 53c33ea4cc929e016812f0d3aac0d302758dc0f8) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dev-manual: Edits from a 2.1 read-through.Scott Rifenbark2016-03-236-77/+117
| | | | | | | | | | | | * Removed some eMenlow stuff * Cleaned up the description of the BSP structures we have now. * Various links fixed into the SDK manual. * Other minor fixes. (From yocto-docs rev: 5e45005d7ff2254df2754a5ea2d7efd7f1c19a42) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* poky.ent: Fixed a typo in one of the variables "ftar" to "tar"Scott Rifenbark2016-03-231-1/+1
| | | | | | | (From yocto-docs rev: 8ecef805bdb3493052f4d1f951e157f488d83c4d) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* poky.ent, bsp-guide: Removed eMenlow example and updated 2.1 variablesScott Rifenbark2016-03-233-166/+310
| | | | | | | | | | | | | | | Probably should have committed these separately but.... * Updated the BSP guide to use an example that we support. I removed the eMenlow stuff completely. * Fixed poky.ent so the 15.0.0 stuff is used for the variables. This supports the 2.1 release. (From yocto-docs rev: 598b261725235b6f160561db22bd9f31ec721066) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-project-qs: Performed a read-through edit.Scott Rifenbark2016-03-231-15/+13
| | | | | | | | | | * Fixed some wordings * Fixed some links for consistency (From yocto-docs rev: 9737ba3a572140bec892ffb555241a2259bd517a) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* poky.ent: Updated copyright year and version variables.Scott Rifenbark2016-03-231-3/+3
| | | | | | | | | Set year to 2016 and fixed some variables. (From yocto-docs rev: d1e15dac45cb689c59d9301af776101336e07bf2) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* mega-manual: Added two new sections for the sdk manualScott Rifenbark2016-03-231-17/+4
| | | | | | | (From yocto-docs rev: 89bf843f13563288d556edf13fde8f6ad3c32868) 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-06-29 00:21:32 +0000