/openbmc/openbmc/poky/meta-selftest/recipes-test/multiconfig/ |
H A D | multiconfig-image-packager_0.1.bb | 26 raise bb.parse.SkipRecipe("Not a multiconfig target") 29 raise bb.parse.SkipRecipe("multiconfig target %s not enabled" % mcname) 31 …# these will most likely start with my BPN multiconfig-image-packager, but I want them from core-i…
|
/openbmc/openbmc/poky/bitbake/lib/bb/tests/runqueue-tests/conf/ |
H A D | bitbake.conf | 17 include conf/multiconfig/${BB_CURRENT_MC}.conf
|
/openbmc/openbmc/poky/meta/lib/oeqa/selftest/ |
H A D | case.py | 164 def write_config(self, data, multiconfig=None): argument 166 if multiconfig: 169 dest_path = '%s/%s.conf' % (multiconfigdir, multiconfig)
|
/openbmc/openbmc/poky/bitbake/lib/bb/ |
H A D | cookerdata.py | 261 multiconfig = (self.data.getVar("BBMULTICONFIG") or "").split() 262 for config in multiconfig: 292 multiconfig = (self.data.getVar("BBMULTICONFIG") or "").split() 293 for config in multiconfig: 299 if multiconfig:
|
/openbmc/openbmc/poky/scripts/esdk-tools/ |
H A D | runqemu | 1675 multiconfig = self.get('MULTICONFIG') 1676 if multiconfig: 1677 multiconfig = "mc:%s" % multiconfig 1680 cmd = 'MACHINE=%s bitbake -e %s %s' % (mach, multiconfig, target) 1682 cmd = 'bitbake -e %s %s' % (multiconfig, target) 1692 cmd = 'MACHINE=%s bitbake -e %s %s' % (mach, multiconfig, target) 1694 cmd = 'bitbake -e %s %s' % (multiconfig, target) 1719 multiconfig = self.get('MULTICONFIG') 1720 if multiconfig: 1721 cmd.append('mc:%s:qemu-helper-native' % multiconfig)
|
/openbmc/openbmc/poky/scripts/ |
H A D | runqemu | 1675 multiconfig = self.get('MULTICONFIG') 1676 if multiconfig: 1677 multiconfig = "mc:%s" % multiconfig 1680 cmd = 'MACHINE=%s bitbake -e %s %s' % (mach, multiconfig, target) 1682 cmd = 'bitbake -e %s %s' % (multiconfig, target) 1692 cmd = 'MACHINE=%s bitbake -e %s %s' % (mach, multiconfig, target) 1694 cmd = 'bitbake -e %s %s' % (multiconfig, target) 1719 multiconfig = self.get('MULTICONFIG') 1720 if multiconfig: 1721 cmd.append('mc:%s:qemu-helper-native' % multiconfig)
|
/openbmc/openbmc/poky/bitbake/doc/bitbake-user-manual/ |
H A D | bitbake-user-manual-intro.rst | 583 referred to as a "multiconfig". 587 the build directory. The location for these multiconfig configuration 589 sub-directory of ``conf`` named ``multiconfig``. Following is an example 636 words, the image for the first multiconfig depends on the root 637 filesystem of the second multiconfig. This dependency is essentially 638 that the task in the recipe that builds one multiconfig is dependent on 640 multiconfig. 657 associated with the "target2" multiconfig. 659 Once you set up this dependency, you can build the "target1" multiconfig 665 multiconfig. Because of the dependency, BitBake also executes through [all …]
|
H A D | bitbake-user-manual-ref-variables.rst | 904 each separate configuration (multiconfig). You can use this variable 915 build directory within a directory named ``conf/multiconfig`` (e.g. 916 build_directory\ ``/conf/multiconfig/configA.conf``).
|
/openbmc/openbmc/poky/documentation/dev-manual/ |
H A D | building.rst | 138 configuration file for each build target (each multiconfig). 160 The location for these multiconfig configuration files is specific. 162 ``conf`` named ``multiconfig`` or within a layer's ``conf`` directory 163 under a directory named ``multiconfig``. Here is an example that defines 170 The usual :term:`BBPATH` search path is used to locate multiconfig files in 177 each multiconfig. Continuing with the example from the previous 221 build a ``core-image-sato`` image for an "x86" multiconfig, the root 222 filesystem of an "arm" multiconfig must exist. This dependency is 244 with the "arm" multiconfig. 246 Once you set up this dependency, you can build the "x86" multiconfig [all …]
|
/openbmc/openbmc/poky/documentation/migration-guides/ |
H A D | migration-3.0.rst | 170 - The "multiconfig" prefix is now shortened to "mc". "multiconfig" will 222 used. You must fix the issue regardless of whether multiconfig or
|
H A D | release-notes-4.0.5.rst | 26 - bitbake: runqueue: Ensure deferred tasks are sorted by multiconfig
|
H A D | release-notes-4.0.9.rst | 103 - staging: Separate out different multiconfig manifests
|
H A D | release-notes-4.1.4.rst | 119 - staging: Separate out different multiconfig manifests
|
H A D | release-notes-4.1.2.rst | 28 - archiver: avoid using machine variable as it breaks multiconfig
|
H A D | release-notes-4.0.12.rst | 42 - bitbake: runqueue: Fix deferred task/multiconfig race issue
|
H A D | release-notes-3.4.1.rst | 30 - bitbake: cooker: Fix task-depends.dot for multiconfig targets
|
H A D | release-notes-4.0.2.rst | 149 - selftest/multiconfig: Test that multiconfigs in separate layers works
|
H A D | migration-4.1.rst | 164 to avoid the archive task running multiple times in a multiconfig setup. If you
|
H A D | release-notes-4.0.6.rst | 36 - archiver: avoid using machine variable as it breaks multiconfig
|
H A D | release-notes-4.2.2.rst | 39 - bitbake: runqueue: Fix deferred task/multiconfig race issue
|
H A D | migration-2.4.rst | 279 - BitBake fires multiple "BuildStarted" events when multiconfig is
|
H A D | release-notes-3.4.rst | 76 - eSDK: Error if trying to generate an eSDK from a multiconfig
|
/openbmc/openbmc/poky/meta/classes-recipe/ |
H A D | populate_sdk_ext.bbclass | 410 bb.utils.mkdirhier(os.path.join(baseoutpath, 'conf', 'multiconfig')) 412 dest_stub = "/conf/multiconfig/%s.conf" % (mc,) 573 manifest_file_list.append('conf/multiconfig/*') 770 # can only be built for the primary (default) multiconfig 772 …bb.fatal('The extensible SDK can currently only be built for the default multiconfig. Currently t…
|
/openbmc/openbmc/poky/meta/classes/ |
H A D | archiver.bbclass | 114 # TARGET_SYS in ARCHIVER_ARCH will break the stamp for gcc-source in multiconfig
|
/openbmc/openbmc/poky/meta/classes-global/ |
H A D | base.bbclass | 290 # We need to expand SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS in each of the multiconfig data stores
|