Home
last modified time | relevance | path

Searched refs:multiconfig (Results 1 – 22 of 22) sorted by relevance

/OK3568_Linux_fs/yocto/poky/meta-selftest/recipes-test/multiconfig/
H A Dmulticonfig-image-packager_0.1.bb22 raise bb.parse.SkipRecipe("Not a multiconfig target")
25 raise bb.parse.SkipRecipe("multiconfig target %s not enabled" % mcname)
/OK3568_Linux_fs/yocto/poky/meta/lib/oeqa/selftest/
H A Dcase.py168 def write_config(self, data, multiconfig=None): argument
170 if multiconfig:
173 dest_path = '%s/%s.conf' % (multiconfigdir, multiconfig)
181 if not multiconfig and self.tc.custommachine and 'MACHINE' in data:
/OK3568_Linux_fs/yocto/poky/bitbake/lib/bb/tests/runqueue-tests/conf/
H A Dbitbake.conf17 include conf/multiconfig/${BB_CURRENT_MC}.conf
/OK3568_Linux_fs/yocto/poky/bitbake/doc/bitbake-user-manual/
H A Dbitbake-user-manual-intro.rst557 referred to as a "multiconfig".
561 the build directory. The location for these multiconfig configuration
563 sub-directory of ``conf`` named ``multiconfig``. Following is an example
610 words, the image for the first multiconfig depends on the root
611 filesystem of the second multiconfig. This dependency is essentially
612 that the task in the recipe that builds one multiconfig is dependent on
614 multiconfig.
631 associated with the "target2" multiconfig.
633 Once you set up this dependency, you can build the "target1" multiconfig
639 multiconfig. Because of the dependency, BitBake also executes through
[all …]
H A Dbitbake-user-manual-ref-variables.rst829 each separate configuration (multiconfig). You can use this variable
840 build directory within a directory named ``conf/multiconfig`` (e.g.
841 build_directory\ ``/conf/multiconfig/configA.conf``).
H A Dbitbake-user-manual-metadata.rst1641 multiple configuration (multiconfig) is enabled.
/OK3568_Linux_fs/yocto/poky/scripts/
H A Drunqemu1580 multiconfig = self.get('MULTICONFIG')
1581 if multiconfig:
1582 multiconfig = "mc:%s" % multiconfig
1585 cmd = 'MACHINE=%s bitbake -e %s' % (mach, multiconfig)
1587 cmd = 'bitbake -e %s' % multiconfig
1613 multiconfig = self.get('MULTICONFIG')
1614 if multiconfig:
1615 cmd.append('mc:%s:qemu-helper-native' % multiconfig)
/OK3568_Linux_fs/yocto/poky/bitbake/lib/bb/
H A Dcookerdata.py284 multiconfig = (self.data.getVar("BBMULTICONFIG") or "").split()
285 for config in multiconfig:
292 if multiconfig:
/OK3568_Linux_fs/yocto/poky/documentation/migration-guides/
H A Dmigration-3.0.rst168 - The "multiconfig" prefix is now shortened to "mc". "multiconfig" will
220 used. You must fix the issue regardless of whether multiconfig or
H A Drelease-notes-4.0.5.rst24 - bitbake: runqueue: Ensure deferred tasks are sorted by multiconfig
H A Drelease-notes-3.4.1.rst28 - bitbake: cooker: Fix task-depends.dot for multiconfig targets
H A Drelease-notes-4.0.6.rst36 - archiver: avoid using machine variable as it breaks multiconfig
H A Drelease-notes-4.0.2.rst147 - selftest/multiconfig: Test that multiconfigs in separate layers works
H A Dmigration-2.4.rst287 - BitBake fires multiple "BuildStarted" events when multiconfig is
H A Drelease-notes-3.4.rst72 - eSDK: Error if trying to generate an eSDK from a multiconfig
H A Drelease-notes-4.0.rst171 - Allow initramfs to be built from a separate multiconfig
/OK3568_Linux_fs/yocto/poky/meta/classes/
H A Dpopulate_sdk_ext.bbclass398 bb.utils.mkdirhier(os.path.join(baseoutpath, 'conf', 'multiconfig'))
400 dest_stub = "/conf/multiconfig/%s.conf" % (mc,)
564 manifest_file_list.append('conf/multiconfig/*')
750 # can only be built for the primary (default) multiconfig
752 …bb.fatal('The extensible SDK can currently only be built for the default multiconfig. Currently t…
H A Darchiver.bbclass104 # TARGET_SYS in ARCHIVER_ARCH will break the stamp for gcc-source in multiconfig
H A Dbase.bbclass284 # We need to expand SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS in each of the multiconfig data stores
/OK3568_Linux_fs/yocto/poky/meta/conf/
H A Dbitbake.conf817 require conf/multiconfig/${BB_CURRENT_MC}.conf
/OK3568_Linux_fs/yocto/poky/documentation/dev-manual/
H A Dcommon-tasks.rst3713 configuration file for each build target (each multiconfig).
3732 The location for these multiconfig configuration files is specific.
3734 ``conf`` named ``multiconfig``. Following is an example that defines
3750 each multiconfig. Continuing with the example from the previous
3794 build a ``core-image-sato`` image for an "x86" multiconfig, the root
3795 filesystem of an "arm" multiconfig must exist. This dependency is
3817 with the "arm" multiconfig.
3819 Once you set up this dependency, you can build the "x86" multiconfig
3825 ``core-image-sato`` image for the "x86" multiconfig. Because of the
3827 "arm" multiconfig build.
[all …]
/OK3568_Linux_fs/yocto/poky/documentation/ref-manual/
H A Dvariables.rst723 ``conf/multiconfig`` directory (e.g.
724 ``build_directory/conf/multiconfig/configA.conf``).
3654 … when building an initramfs image from a separate multiconfig via :term:`INITRAMFS_MULTICONFIG`.
3776 …Defines the multiconfig to create a multiconfig dependency to be used by the :ref:`kernel <ref-cla…
3779 …a separate multiconfig, this is meant to be used in addition to :term:`INITRAMFS_DEPLOY_DIR_IMAGE`.
3782 …multiconfig see the ":ref:`dev-manual/common-tasks:Bundling an Initramfs Image From a Separate Mul…