summaryrefslogtreecommitdiffstats
path: root/meta/classes/sstate.bbclass
Commit message (Collapse)AuthorAgeFilesLines
* sstate: Append to EXTRASSTATEMAPS and add commentRichard Purdie2012-09-121-1/+2
| | | | | | | | | Appending to EXTRA_SSTATEMAPS is better than just hardcoding a value. Also add a comment about why this is necessary. (From OE-Core rev: d4f4a57b8d564d57256017d937ed2eabf94c36ae) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate.bbclass: Remove hardcoded task mappingsRichard Purdie2012-09-021-10/+8
| | | | | | | | | | | | I've not idea why this got left in but as per the comment, it needs fixing and we shouldn't have hardcoded mappings like this. Lets remove it and dynamically generate the data instead. [YOCTO #3039] (From OE-Core rev: 2df064ad46c1510fa8a401c22db4ab3278c3c807) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate: Ensure master.list exists if it doesn't alreadyRichard Purdie2012-08-301-0/+4
| | | | | | | | | | This fixes builds where master.list doesn't already exist. This change was meant to be part of the previous sstate commit but ended up separated. (From OE-Core rev: c2109b765b24a7ffe4781257ad3fe4641a3b2a49) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate.bbclass: Detect overwriting files in sstate controlled directoriesRichard Purdie2012-08-301-1/+44
| | | | | | | | | | | | | | | | | | | | We have a potential problem where two sstate packages try and touch the same file. This adds code which will print a warning whenever this happens. The implementation does but by maintaining a master file list and comparing file accesses against this. There are a number of places we have duplicate accesses which are harmless, mostly in the deploy directory so these are whitelisted. For now the code prints warnings, this could be strengthened in future to become error messages. Whilst working on this code on and off over the past few months various issues were uncovered, some serious. [YOCTO #238] (From OE-Core rev: 1f1b6f93d6b7aa8c9bd9bb5b1826997812e36932) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta/classes: Various python whitespace fixesRichard Purdie2012-08-211-13/+13
| | | | | | | | | | | It was pointed out we have a number of weird indentations in the python functions. This patch cleans up 3, 7 and other weird indentations for the core bbclass files. It also fixes some wierd (odd) shell function indentation which my searches picked up. (From OE-Core rev: 8385d6d74624000d68814f4e3266d47bc8885942) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate.bbclass: Add a string representing the lsb release to native/cross sstateRichard Purdie2012-07-281-5/+17
| | | | | | | | | | | | | | | | | | | This patch adds the lsb name and revision to the path used for sstate files. This means that reuse of sstate files between different distributions is restricted by default. The behaviour can be configured using mirror urls, for example: SSTATE_MIRRORS = "file://Ubuntu-11.10/(.*) file://Ubuntu/\1 \n" would map Ubuntu 11.10 to a more generic "Ubuntu" named sstate feed. Usually, more modern distros have increased libc versions for example so whilst more older native/cross sstate packages will usually work on newer distros, the opposite is not true. This patch allows development of policy to better handle this although no default policy is currently being used. (From OE-Core rev: 9360fc318cec5c873b17f59b817dd6312c81ee27) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate: Add a two character subdirectory to the sstate directory layoutRichard Purdie2012-07-281-12/+15
| | | | | | | | | | | | | Currently all sstate files are placed into one directory. This does not scale and causes a variety of filesystem issues. This patch adds a two character subdirectory to the layout (based on the first two characters of the hash) so that files can be split into several directories. This should help performance of sstate in most cases. (From OE-Core rev: 5d45c7b025f6635b2232d7bf92b7c1aba350396b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate: Set SSTAGE_PKGARCH for allarch packages to allow reuseRichard Purdie2012-07-221-0/+3
| | | | | | | | | allarch sstate packages could be marked as machine or package_arch specific. This change ensures they are not. (From OE-Core rev: f3104240ad5bb542c339ee29b2672523ad3ae50c) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Convert tab indentation in python functions into four-spaceRichard Purdie2012-07-191-52/+52
| | | | | | (From OE-Core rev: 604d46c686d06d62d5a07b9c7f4fa170f99307d8) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate.bbclass: Move crosssdk before cross to ensure correct variables are setRichard Purdie2012-07-171-2/+2
| | | | | | | | | | | | | | | | There was a bug showing up where the crosssdk recipes were being installed as machine specific in the sstate-control directory. This turned out to be due to the architecture fields used by sstate being set incorrectly. The problem is that the crosssdk inherits the cross class. It therefore needs to be listed in this if statement block before the cross check, not after. This should resolve some package architecture issue of crosssdk sstate files. (From OE-Core rev: 79fe28e6033273f9632ca7549d1599d3fd1463ef) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta: replace os.system with subprocess.callRobert Yang2012-05-301-3/+6
| | | | | | | | | | | | | | | Replace os.system with subprocess.call since the older function would fail (more or less) silently if the executed program cannot be found More info: http://docs.python.org/library/subprocess.html#subprocess-replacements [YOCTO #2454] (From OE-Core rev: a07d03cc6f67c88feb9813ae7deb6e4a93552dfe) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate.bbclass: Make sure we don't have an empty fixmepath fileMark Hatle2012-05-181-5/+12
| | | | | | | | | | | | | | Jason Wessel noticed that a package without any fixmepath entries would generate a sed warning about no input files. This patch resolves that by ensuring that an empty fixmepath file never gets written into the sstate archive. Also we avoid a second message by only doing xargs if we got input. (From OE-Core rev: 326563d5a897ae2dba7cfd8d73579d3d979d72c8) Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Jason Wessel <jason.wessel@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta/classes/sstate.bbclass: ensure sstate files have group R/WJoshua Lock2012-05-171-0/+1
| | | | | | | | | In order to make sharing sstate files easier chmod them with 0664 permissions so that they are readable and writable by the user and any other members of their group. (From OE-Core rev: dae9ad8a0ba0343e3083694cdcb20f0d02927ad0) Signed-off-by: Joshua Lock <josh@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate.bbclass: Optimize the generation and install path fixupsMark Hatle2012-05-151-1/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The fixmepath file that is generated contains a list of all of the files that need their paths fixed. In the previous version the fixmepath was generated to include all of the files that sed may have changed. In the new version, we first grep the files to see if they contain a path that needs to be changed, only then do we perform the sed operation on those files. This results in a modest performance increate in the creation of the sstate file. The following numbers include the do_package and do_populate_sysroot tasks on the perl recipe. Before the change: real 4m23.018s user 1m57.067s sys 1m33.327s After the change: real 4m13.083s user 1m54.062s sys 1m26.064s However, a more significnt performance gain is felt during the extraction/install of sstate cache files, as the fixmepaths file now has a significantly smaller list of files to modify. Before the change: real 0m39.798s user 0m11.158s sys 0m12.642s After the change: real 0m25.511s user 0m8.408s sys 0m5.077s (All numbers above were recorded with a cold filesystem cache on a machine with 12 GB of ram.) (From OE-Core rev: 46067264bedeff8248a2b2441733420fe6651f84) Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate.bbclass: Improve sstate_installpkg performanceMark Hatle2012-05-111-7/+21
| | | | | | | | | | | | | | | | | | | | | | | | | In a pathological case, lots of files to process, the sstate_installpkg performance was very poor. It interated over each file and ran 3 individual sed commands per file. Changing this to keep iterating but running only a single command took about 1/3 time time. However, when looking at the corresponding sstate_hardcode_path function, it was clear we could optimize this further. Using the same encoding logic to specify only the minimumal sed operation necessary, and using xargs to avoid the os.system call the install step was able to be performed in 13% of the original time. Example timing numbers for perl: 3m7s original code 1m20s single sed, but interating 0m26s using xargs and limited sed (From OE-Core rev: d9f655753fbdc8cbd8e705577430fed4f23732b3) Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Revert "bitbake.conf/sstate.bbclass: Change PATH when installing sstate ↵Richard Purdie2012-03-231-8/+0
| | | | | | | | | | | files to avoid issues" Reluctantly revert this since it breaks the tar-native workaround we have for old versions of tar :( This reverts commit 01218e29f963120c77885964702198d9bce77e11. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate.bbclass: Remove possibility of file corruption and make package ↵Richard Purdie2012-03-231-2/+4
| | | | | | | | | | | | writing atomic There is currently a race window when creating sstate packages since we don't atomically write the files to SSTATE_DIR. This change ensures we do so by writing to a temporary file and then doing an atomic move. (From OE-Core rev: 52bf113e786a57123a9da98f64442afbc2f1471e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf/sstate.bbclass: Change PATH when installing sstate files to ↵Richard Purdie2012-03-211-0/+8
| | | | | | | | | | | | avoid issues This resolves issues related to pigz-native when installing from sstate that people have been seeing. It also gives us a way to solve issues like the gzip-native race during sstate package creation covered in Yocto #1774. (From OE-Core rev: 518dffe20178f5969dddccb17d6ab347afb72beb) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta: Replace bb.data.expand(xxx, d) -> d.expand(xxx)Richard Purdie2012-03-051-15/+15
| | | | | | | | sed \ -e 's:bb.data.\(expand([^,()]*\), *\([^) ]*\) *):\2.\1):g' \ -i `grep -ril bb.data.expand *` Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate: Remove unecessary bb.data.expand()Richard Purdie2012-03-051-7/+7
| | | | Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta/classes: Convert to use appendVar and appendVarFlagsRichard Purdie2012-03-051-6/+2
| | | | Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate.bbclass: improve performance of sstate package creationMartin Jansa2012-02-241-23/+16
| | | | | | | | | | | | * also fixes replacing paths for perl where cmd line was probably too long for os.system(cmd) (it had 560410 characters because a lot of files from sstate_scan_cmd). * also print those 2 commands so we can find them in log.do_package (From OE-Core rev: 94c52d68fc2ce258bcc5b0978ac73413480a1a93) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate.bbclass: add *_config to SSTATE_SCAN_FILESMartin Jansa2012-02-231-1/+1
| | | | | | | | | * e.g. mysql5 has mysql_config not mysql-config (From OE-Core rev: aebdffc93ba8446bbd4e20263f0f75d4d4460c47) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate.bbclass: Optimise sstate_hardcode_pathRichard Purdie2012-02-101-11/+16
| | | | | | | | | | | | | | The sstate_hardcode_path() function triggered large numbers of exec() calls when processing packages with large numbers of file relocations (e.g. perl). This patch optimises those calls into longer single commands which make the code significantly more efficient. This reduced the do_package time for perl by 2 minutes (from 4.75 minutes) for me. (From OE-Core rev: 4159ff761cf29a03aeb56c7686a4e7af02b52219) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate.bbclass: Add support for sstate preinst functionsRichard Purdie2012-01-271-0/+5
| | | | | | (From OE-Core rev: f2b0a71b3100a0d2ceb80300d7f3823a31eb907a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate: Add SSTATE_SCAN_FILESRichard Purdie2011-12-151-1/+2
| | | | | | | | | | | | | | | | We process all files in the native/cross cases for finding and fixing relocation issues. In the target case we've only processed .la and binconfig files. Since there are other files which are in need of this processing, this change allows recipes to specify files that may be outside the normal set. This means hardcoded paths that need to be fixmepathed to work correctly are handled and addresses some sstate relocation bugs that have been seen. Based on a patch from Saul Wold <sgw@linux.intel.com> (From OE-Core rev: 6ffdcd9120b572fa41659029c3bda7bf00ebcb77) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* getVar/setVar cleanupsRichard Purdie2011-11-271-7/+7
| | | | | | | | | Complete the bb.data.getVar/setVar replacements with accesses directly to the data store object. (From OE-Core rev: 2864ff6a4b3c3f9b3bbb6d2597243cc5d3715939) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate.bbclass: Ensure we expand stamp-extra-infoRichard Purdie2011-11-211-1/+1
| | | | | | | | | Without this change we can end up looking for <stamp>.${MACHINE} instead of the expected expanded value. (From OE-Core rev: 9f743b5033177216fe0e1d3e43ba831f356df08e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Convert to use direct access to the data store (instead of bb.data.*Var*())Richard Purdie2011-11-101-47/+47
| | | | | | | | | | | | | | | | | This is the result of running the following over the metadata: sed \ -e 's:bb.data.\(setVar([^,()]*,[^,()]*\), *\([^ )]*\) *):\2.\1):g' \ -e 's:bb.data.\(setVarFlag([^,()]*,[^,()]*,[^,()]*\), *\([^) ]*\) *):\2.\1):g' \ -e 's:bb.data.\(getVar([^,()]*\), *\([^(), ]*\) *,\([^)]*\)):\2.\1,\3):g' \ -e 's:bb.data.\(getVarFlag([^,()]*,[^,()]*\), *\([^(), ]*\) *,\([^)]*\)):\2.\1,\3):g' \ -e 's:bb.data.\(getVarFlag([^,()]*,[^,()]*\), *\([^() ]*\) *):\2.\1):g' \ -e 's:bb.data.\(getVar([^,()]*\), *\([^) ]*\) *):\2.\1):g' \ -i `grep -ril bb.data *` (From OE-Core rev: b22831fd63164c4db9c0b72934d7d734a6585251) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate.bbclass: Ensure machine specific stamps are only wiped for the ↵Richard Purdie2011-10-071-2/+7
| | | | | | | | | | | | | | | | | current task sstate was being a little too ethusiastic about removing stamp files and was removing stamp files for other machines when it shouldn't have been. This patch teaches sstate about machine specific stamp extensions and allows it to only remove the current task's stampfiles. Based on a patch from Phil Blundell <philb@gnu.org> with some tweaks from me. (From OE-Core rev: 5e9488495401399d39fcb5012b86c313b6caca73) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate: No need to spew out a debug message per file, summarise insteadRichard Purdie2011-09-261-3/+4
| | | | | | (From OE-Core rev: c7b02c6e80819e30a0818282ab8d960243a2d0e8) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate: Avoid contention between sstate packagesRichard Purdie2011-09-071-0/+3
| | | | | | | | | | | If several sstate packages are decompressing at the same time, they can conflict over the "fixmepath". If two packages try to write to this at the same time it results in an error. To avoid this we remove the file once we've finished processing it. (From OE-Core rev: c08d7093bf654ffedb155c5627972e9ecfeb0b60) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate: Add level 2 debug so its possible to see what sstate is doingRichard Purdie2011-08-111-2/+8
| | | | | | | | | | | | Currently its hard to figure out if/when sstate is checking for possible packages to speed up builds. This patch adds level 2 debug output which better indicates what files are being searched for an why. [YOCTO #1259] (From OE-Core rev: a752b23767189f2678367e47ca0b41f49c56a631) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf/classes: Variable cleanupRichard Purdie2011-07-251-3/+3
| | | | | | | | | | | | | This patch removes the variables BASE_PACKAGE_ARCH, BASEPKG_HOST_SYS, BASEPKG_TARGET_SYS and also removes the immediate assignments in several core classes as these are no longer required. This should make it clearer what some of the core variables do and simplfy some overly complex and confusing class code. (From OE-Core rev: d5521be2dcbaf213c140b0d12a4176380874426b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate: Improve performance by moving files rather than using copy and deleteRichard Purdie2011-07-121-5/+11
| | | | | | | Acked-by: Joshua Lock <josh@linux.intel.com> (From OE-Core rev: c5913c644d10470e2c3c8b55cf044995fc109d87) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate.bbclass: Fix an issue if the config changesMark Hatle2011-06-291-0/+2
| | | | | | | | | | | | | | | | | | We need to check if we know of the task type, before we attempt to process it. In order to reproduce the problem build with: PACKAGE_CLASSES = "package_ipk" Then change it to: PACKAGE_CLASSES = "package_rpm" Build again -- and then try bitbake -c cleansstate <recipe> (From OE-Core rev: 8870ba9d261d3cacbe5d1219fdd95840c05ecf9e) Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/conf: Drop MULTIMACH_ARCH variable, it adds unused complexity and ↵Richard Purdie2011-06-281-2/+2
| | | | | | | | | serves no useful purpose (From OE-Core rev: e623d3015bbdeb2b42b9763937be899a1fa9c0ca) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate.bbclass: When removing files, take an exclusive lock, even for shared ↵Richard Purdie2011-06-091-1/+1
| | | | | | | | | lockfiles (From OE-Core rev: 4a3e94c2ec014a8aef5e8ebb21bdbdf8d28416b3) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate.bbclass: Reduce SSTATE_MANIFESTS assignment to be weakKhem Raj2011-04-281-1/+1
| | | | | | | | | | | Distributions can then override this variable if needed useful e.g. when building uclibc/eglibc both using same tmpdir (From OE-Core rev: 839e6e7f3717cc69cf8fc5b1c51bac63ec00655e) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate: ensure an ordered mapping between SSTATETASKS and SSTATETASKNAMESDexuan Cui2011-04-081-2/+4
| | | | | | | | | | | | | | | | Fix [YOCTO #964] A recent commit 25a6e5f9(sstate: use only unique set of SSTATETASK) breaks the ordered mapping between SSTATETASKS and SSTATETASKNAMES. As a result, in sstate_cleanall, the line taskname = tasks[namemap.index(name)] gets an incorrect result, and "bitbake -c cleanall" doesn't really remove the files populalted by do_populate_sysroot. (From OE-Core rev: 2f6505f0e795b6c8cad641a6918739c3faac1f99) Signed-off-by: Dexuan Cui <dexuan.cui@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate: Add support for taking shared lockfilesRichard Purdie2011-03-291-0/+7
| | | | | | (From OE-Core rev: c411a10e06f479ff364c07766f7c77907b7b4a16) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate: use only unique set of SSTATETASKMartin Jansa2011-03-241-2/+2
| | | | | | | | | | | | | | | | | | | * otherwise strange error like this: ERROR: Logfile of failure stored in: /OE/shr-core/tmp/work/armv7a-oe-linux-gnueabi/libtool-cross-2.4-r1/temp/log.do_package_write_ipk.25551 Log data follows: | ERROR: Package already staged (/OE/shr-core/tmp/sstate-control/manifest-nokia900-libtool-cross.deploy-ipk)?! | ERROR: Function 'sstate_task_postfunc' failed NOTE: package libtool-cross-2.4-r1: task do_package_write_ipk: Failed ERROR: Task 11 (/OE/shr-core/openembedded-core/meta/recipes-devtools/libtool/libtool-cross_2.4.bb, do_package_write_ipk) failed with exit code '1' is shown in this case with package_ipk twice in INHERIT * Thanks to Richard for fix (From OE-Core rev: f2fe5e840b8aa0558b5462ef2c7517b2f14ec2ea) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate: Ensure a clean removes setscene stamps as well as the main task stampsRichard Purdie2011-03-191-0/+2
| | | | | | (From OE-Core rev: d07fe8aef537a8bcb96a802e18d7c980ff4c5ce2) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate.bbclass: Turn absolute symbolic links into relative ones for sstate ↵Richard Purdie2011-03-181-1/+28
| | | | | | | | packages (From OE-Core rev: 655139c2644d085331f4f6814119fbd904ff244b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate.bbclass: always delete stamp files in sstate_cleanPaul Eggleton2011-03-151-9/+7
| | | | | | | | | | For safety, always delete the stamp files in sstate_clean regardless of whether the manifest file exists or not. (From OE-Core rev: f781c35da9a11eefdb06bda72ca89753df863efa) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate.bbclass: avoid deleting unrelated stamp filesPaul Eggleton2011-03-151-1/+3
| | | | | | | | | | | | Avoid deleting stamp files whose names contain the current task's name as a substring. This will be especially important for example if do_package_write is ever made an sstate task (as it would previously have deleted the stamps here for do_package_write_ipk etc.) (From OE-Core rev: ea743ea30e2289733d27979e8ec921648342da0e) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate: Ensure the SRCURI fetcher cache is not used for sstateRichard Purdie2011-03-081-1/+1
| | | | | | (From OE-Core rev: 115b3b95e87320b4a6a678df45fece06469dfaeb) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate.bbclass: add SSTATEPOSTINSTFUNCSScott Garman2011-02-231-0/+5
| | | | | | | | | | | | | | When doing builds using sstate cache, there was no way to run the equivalent of a pkg_postinst function. This is needed by the SGML-related documentation recipes to properly update the catalog files when new DTDs and stylesheets are installed. SSTATEPOSTINSTFUNCS is a new variable you can set to function(s) in your recipe to run after install is completed from sstate. Thanks to Richard Purdie for suggesting this solution. Signed-off-by: Scott Garman <scott.a.garman@intel.com>
* sstate: Fix bugs after new fetcherZhai Edwin2011-02-111-3/+3
| | | | | | | | | | | | | Current sstate's fetch code doesn't reflect latest fetcher changes, so old fetch style cause exception and fail silently. [BUGID #708] got fixed. Another issue is "import xxx" in python function from sstate.bbclass can only sit in the head of the function, else have UnboundLocalError: "local variable XXX referenced before assignment". Signed-off-by: Zhai Edwin <edwin.zhai@intel.com>
* meta/classes: Update classes to use new fetcher APIRichard Purdie2011-02-071-28/+28
| | | | Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-11-15 17:24:37 +0000