Home
last modified time | relevance | path

Searched refs:sstate (Results 1 – 25 of 110) sorted by relevance

12345

/OK3568_Linux_fs/yocto/poky/meta/classes/
H A Dbuildstats-summary.bbclass1 # Summarize sstate usage at the end of the build
19 no_sstate, sstate = built[t]
23 sstate.add(pf)
27 no_sstate, sstate = built[t]
28 if no_sstate | sstate:
33 sstate_count = len(sstate)
36 bb.note(" {0}: {1:.1f}% sstate reuse({2} setscene, {3} scratch)".format(
H A Dsstate.bbclass5 SSTATE_MANIFESTS ?= "${TMPDIR}/sstate-control"
32 bb.fatal("Unable to reduce sstate name to less than 255 chararacters")
36 SSTATE_PKGSPEC = "sstate:${PN}:${PACKAGE_ARCH}${TARGET_VENDOR}-${TARGET_OS}:${PV}:${PR}:${SSTATE…
37 SSTATE_SWSPEC = "sstate:${PN}::${PV}:${PR}::${SSTATE_VERSION}:"
47 # We don't want the sstate to depend on things like the distro string
48 # of the system, we let the sstate paths take care of this.
104 # Check whether sstate exists for tasks that support sstate and are in the
112 # The GnuPG key ID and passphrase to use to sign sstate archives (or unset to
116 # Whether to verify the GnUPG signatures when extracting sstate archives
177 bb.fatal("sstate code running without task context?!")
[all …]
H A Ddeploy.bbclass3 do_deploy[sstate-inputdirs] = "${DEPLOYDIR}"
4 do_deploy[sstate-outputdirs] = "${DEPLOY_DIR_IMAGE}"
H A Dpackage_pkgdata.bbclass58 # This needs to match what would get restored from sstate, which is controlled
61 # condensed to inter-sstate task dependencies, similar to that used by setscene
72 # If start is an sstate task (like do_package) we need to add in its direct dependencies
106 # for ones that would be restored from sstate.
H A Dpopulate_sdk_ext.bbclass87 sstate_dir = d.expand('${SDK_OUTPUT}/${SDKPATH}/sstate-cache')
107 sstate_dir = d.expand('${SDK_OUTPUT}/${SDKPATH}/sstate-cache')
135 within the SDK basically works and required sstate artifacts are available.
145 # Force the use of sstate from the build system
152 # be different and we won't be able to find our native sstate)
172 …hould have been setscened" errors indicate this may be caused by missing sstate artifacts that wer…
347 # don't have sstate as well as the task itself. We already know
371 # Map gcc-dependent uninative sstate cache for installer usage
453 # Filter the locked signatures file to just the sstate tasks we are interested in
480 sstate_out = baseoutpath + '/sstate-cache'
[all …]
H A Dstaging.bbclass128 do_populate_sysroot[sstate-inputdirs] = "${SYSROOT_DESTDIR}"
129 do_populate_sysroot[sstate-outputdirs] = "${COMPONENTS_DIR}/${PACKAGE_ARCH}/${PN}"
130 do_populate_sysroot[sstate-fixmedir] = "${COMPONENTS_DIR}/${PACKAGE_ARCH}/${PN}"
245 # Manifests here are complicated. The main sysroot area has the unpacked sstate
246 # which us unrelocated and tracked by the main sstate manifests. Each recipe
301 # This needs to match what would get restored from sstate, which is controlled
304 # condensed to inter-sstate task dependencies, similar to that used by setscene
327 # If start is an sstate task (like do_package) we need to add in its direct dependencies
368 # for ones that would be restored from sstate.
H A Dmodule-base.bbclass4 # in sstate, so we must force do_compile to run (once).
/OK3568_Linux_fs/kernel/net/netfilter/
H A Dnf_conntrack_pptp.c292 if (info->sstate < PPTP_SESSION_REQUESTED) in pptp_inbound_pkt()
295 info->sstate = PPTP_SESSION_CONFIRMED; in pptp_inbound_pkt()
297 info->sstate = PPTP_SESSION_ERROR; in pptp_inbound_pkt()
302 if (info->sstate > PPTP_SESSION_STOPREQ) in pptp_inbound_pkt()
305 info->sstate = PPTP_SESSION_NONE; in pptp_inbound_pkt()
307 info->sstate = PPTP_SESSION_ERROR; in pptp_inbound_pkt()
312 if (info->sstate != PPTP_SESSION_CONFIRMED) in pptp_inbound_pkt()
335 if (info->sstate != PPTP_SESSION_CONFIRMED) in pptp_inbound_pkt()
346 if (info->sstate != PPTP_SESSION_CONFIRMED) in pptp_inbound_pkt()
396 msg, ntohs(cid), ntohs(pcid), info->cstate, info->sstate, in pptp_inbound_pkt()
[all …]
/OK3568_Linux_fs/yocto/poky/scripts/
H A Dsstate-cache-management.sh18 Welcome to sstate cache management utilities.
19 sstate-cache-management.sh <OPTION>
25 --cache-dir=<sstate cache dir>
26 Specify sstate cache directory, will use the environment
52 Specify the build directory's stamps directories, the sstate
54 other sstate cache files in cache-dir will be removed. Use ","
278 rm_old_list=$remove_listdir/sstate-old-filenames
H A Dsstate-diff-machines.sh37 Welcome to utility to compare sstate checksums between different MACHINEs.
110 OUTPUT=${tmpdir}/sstate-diff/`date "+%s"`
/OK3568_Linux_fs/yocto/poky/meta/recipes-core/meta/
H A Dmeta-extsdk-toolchain.bb10 # within sstate.bbclass, so if you copy or rename this and expect the same
17 do_locked_sigs[sstate-inputdirs] = "${LOCKED_SIGS_INDIR}"
18 do_locked_sigs[sstate-outputdirs] = "${STAGING_DIR}/${PACKAGE_ARCH}/${PN}/locked-sigs"
H A Dmeta-world-pkgdata.bb19 do_collect_packagedata[sstate-inputdirs] = "${WORLD_PKGDATADIR}"
20 do_collect_packagedata[sstate-outputdirs] = "${STAGING_DIR_HOST}/world-pkgdata"
/OK3568_Linux_fs/yocto/poky/bitbake/lib/toaster/tests/eventreplay/
H A DREADME13 $ rm -r tmp sstate-cache
15 $ rm -rf tmp sstate-cache
/OK3568_Linux_fs/yocto/poky/documentation/migration-guides/
H A Dmigration-1.3.rst17 .. _migration-1.3-sstate-mirrors:
22 The shared state cache (sstate-cache), as pointed to by
25 directory. Also, native sstate-cache packages, which are built to run on
27 string. If you copy the newly structured sstate-cache to a mirror
34 SSTATE_MIRRORS = "file://.* http://someserver.tld/share/sstate/PATH"
H A Drelease-notes-4.0.6.rst41 - bitbake: runqueue: Fix race issues around hash equivalence and sstate reuse
62 - gcc-source: Ensure deploy_source_date_epoch sstate hash doesn't change
142 - scripts/oe-check-sstate: cleanup
143 - scripts/oe-check-sstate: force build to run for all targets, specifically populate_sysroot
147 - sstate: Allow optimisation of do_deploy_archives task dependencies
148 - sstatesig: emit more helpful error message when not finding sstate manifest
H A Drelease-notes-4.0.2.rst81 - liberror-perl: Update sstate/equiv versions to clean cache
101 - local.conf.sample: Update sstate url to new 'all' path
109 - manuals: switch to the sstate mirror shared between all versions
139 - rust-common: Ensure sstate signatures have correct dependencues for do_rust_gen_targets
142 - rust-common: Fix sstate signatures between arm hf and non-hf
/OK3568_Linux_fs/yocto/poky/bitbake/lib/bb/tests/runqueue-tests/classes/
H A Dbase.bbclass243 bb.note("SState: Found valid sstate for %s" % n)
246 bb.note("SState: Found valid sstate for %s" % n)
252 bb.note("SState: Found valid sstate for %s (already run)" % n)
255 …bb.note("SState: sstate hash didn't match previous run for %s (%s vs %s)" % (n, sq_data['hash'][ti…
259 bb.note("SState: Found no valid sstate for %s (%s)" % (n, sq_data['hash'][tid]))
/OK3568_Linux_fs/yocto/poky/documentation/ref-manual/
H A Dtasks.rst84 ``do_deploy`` as a shared state (sstate) task that can be accelerated
85 through sstate use. The sstate mechanism takes care of copying the
91 the sstate mechanism to malfunction.
395 The ``do_populate_sysroot`` task is a shared state (sstate) task, which
396 means that the task can be accelerated through sstate use. Realize also
461 :ref:`sstate <overview-manual/concepts:shared state cache>` cache files.
463 after cleaning, output files are simply restored from the sstate cache.
464 If you want to remove the sstate cache files for the recipe, you need to
474 (:ref:`sstate <overview-manual/concepts:shared state cache>`) cache, and
494 (:ref:`sstate <overview-manual/concepts:shared state cache>`) cache for a
[all …]
/OK3568_Linux_fs/yocto/poky/meta-poky/conf/
H A Dlocal.conf.sample65 # The default is a sstate-cache directory under TOPDIR.
67 #SSTATE_DIR ?= "${TOPDIR}/sstate-cache"
211 # would contain the sstate-cache results from previous builds (possibly from other
218 #file://.* https://someserver.tld/share/sstate/PATH;downloadfilename=PATH \
219 #file://.* file:///some/local/dir/sstate/PATH"
233 #SSTATE_MIRRORS ?= "file://.* http://sstate.yoctoproject.org/all/PATH;downloadfilename=PATH"
254 # equivalence improves reuse of sstate by detecting when a given sstate
/OK3568_Linux_fs/yocto/poky/meta/recipes-devtools/gcc/
H A Dgcc-cross.inc155 do_gcc_stash_builddir[sstate-inputdirs] = "${BUILDDIRSTASH}"
156 do_gcc_stash_builddir[sstate-outputdirs] = "${COMPONENTS_DIR}/${BUILD_ARCH}/gcc-stashed-builddir-${…
157 do_gcc_stash_builddir[sstate-fixmedir] = "${COMPONENTS_DIR}/${BUILD_ARCH}/gcc-stashed-builddir-${TA…
/OK3568_Linux_fs/yocto/poky/scripts/contrib/bb-perf/
H A Dbb-matrix.sh54 rm -rf pseudodone tmp sstate-cache tmp-eglibc &> /dev/null
/OK3568_Linux_fs/yocto/poky/meta/recipes-devtools/libtool/libtool/
H A Dnohardcodepaths.patch1 If for example you build on a machine with /bin/grep, then restore that sstate
/OK3568_Linux_fs/yocto/poky/meta/conf/distro/include/
H A Dyocto-uninative.inc4 # want to use/maintain a unified sstate feed for native/cross artefacts
/OK3568_Linux_fs/yocto/meta-openembedded/meta-oe/recipes-support/serial-utils/
H A Dpty-forward-native.bb14 do_deploy[sstate-outputdirs] = "${DEPLOY_DIR_IMAGE}"
/OK3568_Linux_fs/yocto/poky/documentation/overview-manual/
H A Dconcepts.rst1153 The stamp mechanism is more general than the shared state (sstate)
1157 tasks that can be accelerated through the sstate cache.
1164 the sstate cache mechanism adds is a way to cache task output that
1186 usually made available in the form of a shared state (sstate) cache.
1190 For information on variables affecting sstate, see the
1223 It becomes more complicated if everything can come from an sstate cache
1227 from sstate, BitBake does not need the ``do_package`` task data.
1231 sstate cache for any targets it is planning to build. BitBake does a
1236 If objects are found in the sstate cache, the build system works
1245 The availability of objects in the sstate cache is handled by the
[all …]

12345