summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFiles
2011-01-27eds-dbus: Do not disable old API after upgrading gtk+Zhai Edwin2
This avoid build error due to defination missing. Signed-off-by: Zhai Edwin <edwin.zhai@intel.com>
2011-01-27gtk+: Update to 2.22.1Zhai Edwin13
Remove disable-gio-png-sniff-test.diff as it alreay in upstream. gdk-pixbuf in gtk+ is separated as another stand-alone package, so remove it. In future need only pick up stable version(even number like 2.20.x, 2.22.x). Signed-off-by: Zhai Edwin <edwin.zhai@intel.com>
2011-01-27sstate.bbclass: Optimise to check if the manifest exists without taking locksRichard Purdie1
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-01-27external-python-tarball: include multiprocessing moduleJoshua Lock1
Signed-off-by: Joshua Lock <josh@linux.intel.com>
2011-01-27perl: Remove ${MACHINE} dependency in compile and package.Dongxiao Xu1
The judgement on ${MACHINE} is meaningless, remove it in order to avoid being rebuild on second machine. Signed-off-by: Dongxiao Xu <dongxiao.xu@intel.com>
2011-01-27bitbake/build.py: When looking up extra stamp info for setscene tasks, use ↵Richard Purdie1
the real taskname (Fixed based on a bug reported by Dongxiao Xu <dongxiao.xu@intel.com>) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-01-27rm_work.bbclass: Update to convert stamps to setscene stampsRichard Purdie1
We need to manipulate the stamps when removing WORKDIR to indicte that tasks like compile or install can't just rerun. The most effective method to do this is to convert the layout to match that which would have been the case had the system been build from sstate packages. For example, we'd task stamps like: xxx-1.4.7-r3.do_compile xxx-1.4.7-r3.do_configure xxx-1.4.7-r3.do_fetch xxx-1.4.7-r3.do_generate_toolchain_file xxx-1.4.7-r3.do_install xxx-1.4.7-r3.do_package.emenlow xxx-1.4.7-r3.do_package_write xxx-1.4.7-r3.do_package_write_ipk xxx-1.4.7-r3.do_package_write_rpm xxx-1.4.7-r3.do_patch xxx-1.4.7-r3.do_populate_sysroot.emenlow xxx-1.4.7-r3.do_setscene xxx-1.4.7-r3.do_unpack and after rm_work, we'd have stamps of: xxx-1.4.7-r3.do_package_setscene.emenlow xxx-1.4.7-r3.do_package_write_ipk_setscene xxx-1.4.7-r3.do_package_write_rpm_setscene xxx-1.4.7-r3.do_populate_sysroot_setscene.emenlow We also need to handle stamps in the form xxx-1.4.7-r3.do_package.MACHINE.TASKHASH as used by some signature generators. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-01-27autotools.bbclass: Drop unused autotools_stage_dir dummy functionRichard Purdie1
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-01-27autotools.bbclass: Only include aclocal directories if the exist, no point ↵Richard Purdie1
in creating them Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-01-26send-pull-request: ensure a proper FROM header is includedDarren Hart1
Commit 94629f2521711055b412f954af19e48b9bda6e50 removes the FROM header when sending via sendmail to avoid sending mail as the original change committer (as opposed to the local user). This resulted in mail going out without any FROM header, which some mailing lists correct by adding the *bounce address as the FROM. Correct this by reading FROM from the environment, from a new -f argument, or from the git user.name and user.email config settings, in that order of preference. Also display the FROM that will be used prior to the send confirmation. This has no effect if the -g (send via git) argument is specified, other than printing the git sendemail.from config setting. Signed-off-by: Darren Hart <dvhart@linux.intel.com> Reported-by: Saul Wold <saul.wold@intel.com>
2011-01-26meta-toolchain: Fix tar commandRichard Purdie1
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-01-26bitbake/unlockfile: Fix exception handlingRichard Purdie1
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-01-26crosssdk: Drop PACKAGES setting as its set in cross.bbclass alreadyRichard Purdie1
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-01-26sstate.bbclass: Correctly handle empty sstate packagesRichard Purdie1
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-01-26cross.bbclass: Move sysroot_stage_all function to the only place that uses ↵Richard Purdie2
it now (gcc-cross-intermediate) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-01-26staging.bbclass: No need to create these directories any more, also remove ↵Richard Purdie1
invalid comment Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-01-26meta-toolchain: Use --owner and --group options instead of using pseudo's ↵Richard Purdie1
overhead for a simple task Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-01-26perl: Remove MACHINE reference in do_configure, it causes perl to be rebuild ↵Richard Purdie1
many times Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-01-25kern-tools: update to the new repositoryBruce Ashfield1
As the first of several changes to the kern-tools coupled to the branch management in the yocto kernels the repository is being renamed to it proper name. This change switches us to that newly created repo. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2011-01-25documentation/yocto-project-qs/yocto-project-qs.xml: Added note to ↵Scott Rifenbark1
poky-qemu command Depending on the architecture you are booting and the profile of the filesystem image QEMU might come up in a new shell, and existing shell, have a GUI, or be in command-line mode. I added a note indicating this behavior. Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
2011-01-25documentation/yocto-project-qs/yocto-project-qs.xml: Updated <arch> value ↵Scott Rifenbark1
for environment setup command The value for the 64-bit architecture was "x86-64" and not "x86_64". Changed it to be correct. Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
2011-01-25documentation/yocto-project-qs/yocto-project-qs.xml: Updated list ↵Scott Rifenbark1
introducing pre-built section The section that introduces the using a pre-built binary section needed more items in the list. I added text for setting up the environment and for starting QEMU. Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
2011-01-25documentation/yocto-project-qs/yocto-project-qs.xml: Added sub-sections to ↵Scott Rifenbark1
pre-built image section The pre-built image section was one long section that naturally broke into several areas. I inserted some sub-sections for better organization. Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
2011-01-25documentation/yocto-project-qs/yocto-project-qs.xml: Corrected environment ↵Scott Rifenbark1
setup command I added the exact architecture strings for each of the five supported architectures as part of the /opt/poky/environment-setup.... commands resulting from installing the toolchain tarballs. Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
2011-01-25linux-yocto/stable: perf: hard-code NO_LIBPERL/NO_LIBPYTHOBruce Ashfield1
Updating SRCREVs to reflect: perf: hard-code NO_LIBPERL/NO_LIBPYTHON ExtUtils::Embed ccopts is getting the host's -I/usr/local/include and using it to compile perf, which results in a compilation error that started appearing just recently. This turns the code that makes use of ExtUtils::Embed off and simply hard-codes NO_LIBPERL. It does the same for LIBPYTHON while we're at it, since it probably suffers from a similar underlying problem and just by chance hasn't broken anything yet. This will be re-enabled after I familiarize myself with the perf recipe and am able to create a proper fix. Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2011-01-25util-linux.inc: Fix DEPENDS on gettext for native caseRichard Purdie2
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-01-25distro_tracking: Update for poky-image-sdk renamingSaul Wold1
Signed-off-by: Saul Wold <sgw@linux.intel.com>
2011-01-25poky-image-sdk* renamed to poky-image-sato-sdk*Saul Wold5
Signed-off-by: Saul Wold <sgw@linux.intel.com>
2011-01-25meta-toolchain-sdk: Rename meta-toolchain-sdk to meta-toolchain-gmaeJessica Zhang2
Change the name from toolchain-sdk to toolchain-gmae, which is more accurate to what meta-toolchain-sdk generates Signed-off-by: Jessica Zhang <jessica.zhang@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2011-01-25util-linux: tidy up metadataJoshua Lock1
Apply a couple of best practices to the recipe: 1) use the gettext class to ensure the right versions of gettext are used for the recipe variants (target, native, etc). 2) use layout variables rather than absolute paths in the package FILES_ definitions. Signed-off-by: Joshua Lock <josh@linux.intel.com>
2011-01-25sanity/sstate: Due to the sysroot layout changes, the toolchain bootstrap ↵Richard Purdie3
process changes and the recent pseudo bug, bump the tmpdir layout version number and the sstate version numbers Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-01-25bitbake/fetch2: Instrument fetchers when making network accessYu Ke9
Signed-off-by: Yu Ke <ke.yu@intel.com>
2011-01-25bb.fetch2: add "BB_NO_NETWORK" optionYu Ke1
Sometime user want a purely local fetching, i.e. using local mirror without any remote netowrk access. BB_NO_NETWORK option is introduced for this purpose check_network_access() is the guard for BB_NO_NETWOKR option. it should be put in any place that fetcher use network access Signed-off-by: Yu Ke <ke.yu@intel.com>
2011-01-25bb.fetch2: remove the obsolate Fetch.try_mirrors referrenceYu Ke1
Fetch.try_mirrors is no longer exists, so the code is obsolate Signed-off-by: Yu Ke <ke.yu@intel.com>
2011-01-25git.py: split download to download() and build_mirror_data()Yu Ke2
the download is to fetch the source from URL, the build_mirror_data is to create the mirror tar ball. the original go() method mix them together, it is more clean to split them. Signed-off-by: Yu Ke <ke.yu@intel.com>
2011-01-25base/sstate.bbclass: Rename fetcher "go" method to "download" when using ↵Yu Ke2
fetch v2 Signed-off-by: Yu Ke <ke.yu@intel.com>
2011-01-25bb.fetch2: rename "go" with "download" to better reflect its functionalityYu Ke13
no functional change Signed-off-by: Yu Ke <ke.yu@intel.com>
2011-01-25base.bbclass: use bb.fetch2 unpack APIYu Ke1
Signed-off-by: Yu Ke <ke.yu@intel.com>
2011-01-25bb.fetch: add fetch version to distinguish bb.fetch and bb.fetch2Yu Ke2
there is case that we need to distingush bb.fetch and bb.fetch2, and use different API for bb.fetch and bb.fetch2. so it is necessary to add version info for distinguish purpose Signed-off-by: Yu Ke <ke.yu@intel.com>
2011-01-25bb.fetch2: revise the Fetch.unpack APIYu Ke1
change the unpack to use the urldata and rootdir parameter - urldata is the FetchData instance - rootdir is the dir to put the extracted source. the original unpack use current dir (os.getcwd) as destination dir, which is not flexible and error-prone (error will occur if caller not chdir to dest dir) Signed-off-by: Yu Ke <ke.yu@intel.com>
2011-01-25bb.fetch2: add unpack method in fetcherYu Ke1
copy exactly the base.bbclass:oe_unpack_file() to bb.fetch2 as the code base Signed-off-by: Yu Ke <ke.yu@intel.com>
2011-01-25emenlow: Change PACKAGE_EXTRA_ARCHS and BASE_PACKAGE_ARCH to core2Dongxiao Xu1
After machine specific sysroot is implemented, emenlow and atom-pc could build together as one architecture. Thus change emenlow architecture back to core2. Signed-off-by: Dongxiao Xu <dongxiao.xu@intel.com>
2011-01-25bitbake: machine specific sysroots implementationDongxiao Xu12
This commit changes the sysroots path to be machine specific. Changes includes: 1) STAGING_DIR_TARGET and STRAGING_DIR_HOST points to machine specific paths. 2) task stamp files. Adding ${MACHINE} info into stamp files for do_populate_sysroots and do_package tasks. Add a BB_STAMPTASK_BLACKLIST to keep native, nativesdk, crosssdk, and cross-canadian stamp unchanged. 3) siteconfig path. Separate the site config path for different machines to avoid one machine adopting the cache file of another machine. 4) sstate. Add machine name to sstate manifest file. Change relocation code for sstate paths since sysroot is machine. Keep native, nativesdk, crosssdk, and cross-canadian unchanged. 5) toolchain scripts. Change the environment path to point to machine specific sysroots in toolchain scripts bbclass. 6) Relocate la files when populating to a different machine of the same architecture. 7) Exclude STAGING_DIR_TARGET and STAGING_DIR_HOST parameter from sstate siginfo since they contain ${MACHINE} information. Signed-off-by: Dongxiao Xu <dongxiao.xu@intel.com>
2011-01-25base-files: Add to make some directories needed by LSB.Jingdong Lu1
LSB will check some directories,eg, "/usr/local/" and need to make them for LSB test. Signed-off-by: Jingdong Lu <jingdong.lu@windriver.com>
2011-01-25liburi-perl: Rename liburi-perlJingdong Lu1
Signed-off-by: Jingdong Lu <jingdong.lu@windriver.com>
2011-01-25pseudo: Revert msg cache changesMark Hatle3
The message cache code in pseudo seems to be causing problems. So we have finally decided to revert that optimization. (The revert is in the upstream pseudo.) Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
2011-01-25gcc/libc: Change bootstrap to use an intermediate sysroot and hence no ↵Richard Purdie7
longer overwrite files Based upon patches from Dexuan Cui <dexuan.cui@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-01-25gcc-cross-intermediate, gcc-crosssdk-intermediate: change ↵Dexuan Cui3
CROSS_TARGET_SYS_DIR and install into new locations Signed-off-by: Dexuan Cui <dexuan.cui@intel.com>
2011-01-25gcc-cross-initial, gcc-crosssdk-initial: change CROSS_TARGET_SYS_DIR and ↵Dexuan Cui7
insall into new locations Signed-off-by: Dexuan Cui <dexuan.cui@intel.com>
2011-01-25sstate.bbclass: allow each step of toolchain bootstrap processes to do ↵Dexuan Cui1
populate_sysroot independently Some steps (like gcc-cross-initial, gcc-cross-intermediate and eglibc-initial) will install to new locations to avoid file overwriting. Signed-off-by: Dexuan Cui <dexuan.cui@intel.com>