| /openbmc/qemu/.gitlab-ci.d/ |
| H A D | buildtest.yml | 2 - local: '/.gitlab-ci.d/buildtest-template.yml'
4 build-system-alpine:
6 - .native_build_job_template
7 - .native_build_artifact_template
9 - job: amd64-alpine-container
12 TARGETS: avr-softmmu loongarch64-softmmu mips64-softmmu mipsel-softmmu
13 MAKE_CHECK_ARGS: check-build
14 CONFIGURE_ARGS: --enable-docs --enable-trace-backends=log,simple,syslog
16 check-system-alpine:
19 - job: build-system-alpine
[all …]
|
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | gobject-introspection.rst | 1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
7 is the standard mechanism for accessing GObject-based software from
20 GObject Introspection Repository (GIR) files go to ``-dev`` packages,
28 Generating this data in a cross-compilation environment is difficult
30 code needs to be executed on the build host. This problem is solved with
31 the OpenEmbedded build system by running the code through QEMU, which
32 allows precisely that. Unfortunately, QEMU does not always work
33 perfectly as mentioned in the ":ref:`dev-manual/gobject-introspection:known issues`"
42 #. Inherit the :ref:`ref-classes-gobject-introspection` class.
46 "gobject-introspection-data" is not in
[all …]
|
| H A D | wic.rst | 1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
7 OpenEmbedded build system does not necessarily mean you can boot that
16 OpenEmbedded build artifacts. Image generation is driven by partitioning
21 ":ref:`dev-manual/wic:generate an image using an existing kickstart file`"
22 section. When you apply the command to a given set of build artifacts, the
29 ":ref:`ref-manual/kickstart:openembedded kickstart (\`\`.wks\`\`) reference`"
36 ":ref:`dev-manual/wic:using the wic plugin interface`" section
50 - The name "Wic" is derived from OpenEmbedded Image Creator (oeic). The
54 - Wic is loosely based on the Meego Image Creator (``mic``) framework.
56 of OpenEmbedded build artifacts instead of package installation and
[all …]
|
| /openbmc/qemu/docs/about/ |
| H A D | build-platforms.rst | 1 .. _Supported-build-platforms:
3 Supported build platforms
6 QEMU aims to support building and executing on multiple host OS
7 platforms. This appendix outlines which platforms are the major build
9 minimum required versions of 3rd party software QEMU depends on. The
14 If a platform is not listed here, it does not imply that QEMU won't
21 support targets, QEMU considers only the version number, and assumes the
24 software in their distro, QEMU upstream code will not add explicit
25 support for those backports, unless the feature is auto-detectable in a
32 You can find how to install build dependencies for different systems on the
[all …]
|
| /openbmc/docs/development/ |
| H A D | devtool-hello-world.md | 4 in QEMU.
7 [Document](https://github.com/openbmc/docs/blob/master/development/dev-environment.md)
9 ## Clone and Build a Repo
16 [phosphor-state-manager](https://github.com/openbmc/phosphor-state-manager.git)
25 devtool modify phosphor-state-manager
33 vi workspace/sources/phosphor-state-manager/bmc_state_manager_main.cpp
43 @@ -17,6 +18,8 @@ int main(int argc, char**)
55 This will be a much faster build as bitbake will utilize all of the cache
56 from your previous build, only building what is new.
59 bitbake obmc-phosphor-image
[all …]
|
| H A D | web-ui.md | 3 **Document Purpose:** How to customize, build, and run the OpenBMC Web UI
9 ## Webui-vue
11 The [webui-vue](https://github.com/openbmc/webui-vue) repository will replace
12 phosphor-webui once it is deprecated. Webui-vue uses the
16 Visit [README.md](https://github.com/openbmc/webui-vue/blob/master/README.md) to
21 [CONTRIBUTING.md](https://github.com/openbmc/webui-vue/blob/master/CONTRIBUTING.md)
22 to find information on project set-up, design information, and contributing
25 Visit the [OpenBMC Web UI Style Guide](https://openbmc.github.io/webui-vue/) to
28 - Coding Standards
29 - Guidelines
[all …]
|
| /openbmc/openbmc/poky/documentation/brief-yoctoprojectqs/ |
| H A D | index.rst | 1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
4 Yocto Project Quick Build
11 image build using the Yocto Project. The document also introduces how to
12 configure a build for specific hardware. You will use Yocto Project to
13 build a reference embedded OS called Poky.
17 - The examples in this paper assume you are using a native Linux
19 you want to use Yocto Project on to build an image
20 (:term:`Build Host`) is not
23 :ref:`dev-manual/start:setting up to use cross platforms (crops)`
28 - You may use version 2 of Windows Subsystem For Linux (WSL 2) to set
[all …]
|
| /openbmc/openbmc/poky/documentation/migration-guides/ |
| H A D | migration-1.7.rst | 1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
9 .. _migration-1.7-changes-to-setting-qemu-packageconfig-options:
11 Changes to Setting QEMU ``PACKAGECONFIG`` Options in ``local.conf``
12 -------------------------------------------------------------------
14 The QEMU recipe now uses a number of
18 append to :term:`PACKAGECONFIG` for ``qemu-native`` and ``nativesdk-qemu``
20 QEMU, you should now have these lines in ``local.conf``::
22 PACKAGECONFIG_append_pn-qemu-native = " sdl"
23 PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl"
25 .. _migration-1.7-minimum-git-version:
[all …]
|
| /openbmc/openbmc/poky/documentation/ref-manual/ |
| H A D | system-requirements.rst | 1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
18 ":ref:`overview-manual/development-environment:the yocto project development environment`"
21 If you want to use the Yocto Project to quickly build an image without
23 :doc:`/brief-yoctoprojectqs/index` document. You can find "how-to"
24 information in the :doc:`/dev-manual/index`. You can find Yocto Project overview
25 and conceptual information in the :doc:`/overview-manual/index`.
30 the :ref:`ref-manual/resources:links and related documentation` section.
35 To build an image such as ``core-image-sato`` for the ``qemux86-64`` machine,
37 However, much more disk space will be necessary to build more complex images,
38 to run multiple builds and to cache build artifacts, improving build efficiency.
[all …]
|
| /openbmc/openbmc/meta-ampere/meta-mitchell/conf/templates/default/ |
| H A D | local.conf.sample | 15 MACHINE ??= "mtmitchell-dcscm"
20 # During a first build the system will download many different source code tarballs
26 # The default is a downloads directory under TOPDIR which is the build directory.
31 # Where to place shared-state files
37 # You can wipe out TMPDIR leaving this directory intact and the build would regenerate
42 # The default is a sstate-cache directory under TOPDIR.
44 #SSTATE_DIR ?= "${TOPDIR}/sstate-cache"
47 # Where to place the build output
66 DISTRO ?= "openbmc-phosphor"
71 # DISTRO ?= "poky-bleeding"
[all …]
|
| /openbmc/openbmc/meta-ampere/meta-jefferson/conf/templates/default/ |
| H A D | local.conf.sample | 20 # During a first build the system will download many different source code tarballs
26 # The default is a downloads directory under TOPDIR which is the build directory.
31 # Where to place shared-state files
37 # You can wipe out TMPDIR leaving this directory intact and the build would regenerate
42 # The default is a sstate-cache directory under TOPDIR.
44 #SSTATE_DIR ?= "${TOPDIR}/sstate-cache"
47 # Where to place the build output
66 DISTRO ?= "openbmc-phosphor"
71 # DISTRO ?= "poky-bleeding"
80 # - 'package_deb' for debian style deb files
[all …]
|
| /openbmc/openbmc/meta-ampere/meta-jade/conf/templates/default/ |
| H A D | local.conf.sample | 20 # During a first build the system will download many different source code tarballs
26 # The default is a downloads directory under TOPDIR which is the build directory.
31 # Where to place shared-state files
37 # You can wipe out TMPDIR leaving this directory intact and the build would regenerate
42 # The default is a sstate-cache directory under TOPDIR.
44 #SSTATE_DIR ?= "${TOPDIR}/sstate-cache"
47 # Where to place the build output
66 DISTRO ?= "openbmc-phosphor"
71 # DISTRO ?= "poky-bleeding"
80 # - 'package_deb' for debian style deb files
[all …]
|
| /openbmc/openbmc/meta-hpe/meta-dl385-g11/conf/templates/default/ |
| H A D | local.conf.sample | 16 # You need to select a specific machine to target the build with. There are a selection
17 # of emulated machines available which can boot and run in the QEMU emulator:
25 #MACHINE ?= "qemux86-64"
30 #MACHINE ?= "beaglebone-yocto"
32 #MACHINE ?= "genericx86-64"
33 #MACHINE ?= "mpc8315e-rdb"
36 # This sets the default machine to be qemux86-64 if no other machine is selected:
37 MACHINE ??= "dl385-g11"
42 # During a first build the system will download many different source code tarballs
48 # The default is a downloads directory under TOPDIR which is the build directory.
[all …]
|
| /openbmc/openbmc/meta-amd/meta-daytonax/conf/templates/default/ |
| H A D | local.conf.sample | 17 # You need to select a specific machine to target the build with. There are a selection
18 # of emulated machines available which can boot and run in the QEMU emulator:
25 #MACHINE ?= "qemux86-64"
32 #MACHINE ?= "genericx86-64"
33 #MACHINE ?= "mpc8315e-rdb"
42 # During a first build the system will download many different source code tarballs
48 # The default is a downloads directory under TOPDIR which is the build directory.
53 # Where to place shared-state files
59 # You can wipe out TMPDIR leaving this directory intact and the build would regenerate
64 # The default is a sstate-cache directory under TOPDIR.
[all …]
|
| /openbmc/openbmc/meta-amd/meta-ethanolx/conf/templates/default/ |
| H A D | local.conf.sample | 17 # You need to select a specific machine to target the build with. There are a selection
18 # of emulated machines available which can boot and run in the QEMU emulator:
25 #MACHINE ?= "qemux86-64"
32 #MACHINE ?= "genericx86-64"
33 #MACHINE ?= "mpc8315e-rdb"
42 # During a first build the system will download many different source code tarballs
48 # The default is a downloads directory under TOPDIR which is the build directory.
53 # Where to place shared-state files
59 # You can wipe out TMPDIR leaving this directory intact and the build would regenerate
64 # The default is a sstate-cache directory under TOPDIR.
[all …]
|
| /openbmc/openbmc/meta-ibm/meta-palmetto/conf/templates/default/ |
| H A D | local.conf.sample | 17 # You need to select a specific machine to target the build with. There are a selection
18 # of emulated machines available which can boot and run in the QEMU emulator:
26 #MACHINE ?= "qemux86-64"
31 #MACHINE ?= "beaglebone-yocto"
33 #MACHINE ?= "genericx86-64"
42 # During a first build the system will download many different source code tarballs
48 # The default is a downloads directory under TOPDIR which is the build directory.
53 # Where to place shared-state files
59 # You can wipe out TMPDIR leaving this directory intact and the build would regenerate
64 # The default is a sstate-cache directory under TOPDIR.
[all …]
|
| /openbmc/qemu/docs/system/arm/ |
| H A D | orangepi.rst | 1 Orange Pi PC (``orangepi-pc``)
5 based embedded computer with mainline support in both U-Boot
6 and Linux. The board comes with a Quad Core Cortex-A7 @ 1.3GHz,
15 * SMP (Quad Core Cortex-A7)
20 * Timer device (re-used from Allwinner A10)
36 - Graphical output via HDMI, GPU and/or the Display Engine
37 - Audio output
38 - Hardware Watchdog
41 for a complete list of unimplemented I/O devices: ``./hw/arm/allwinner-h3.c``
46 The Orange Pi PC machine can start using the standard -kernel functionality
[all …]
|
| /openbmc/openbmc/meta-yadro/meta-vegman/conf/templates/default/ |
| H A D | local.conf.sample | 22 # During a first build the system will download many different source code tarballs
28 # The default is a downloads directory under TOPDIR which is the build directory.
33 # Where to place shared-state files
39 # You can wipe out TMPDIR leaving this directory intact and the build would regenerate
44 # The default is a sstate-cache directory under TOPDIR.
46 #SSTATE_DIR ?= "${TOPDIR}/sstate-cache"
49 # Where to place the build output
68 DISTRO ?= "openbmc-phosphor"
73 # DISTRO ?= "poky-bleeding"
82 # - 'package_deb' for debian style deb files
[all …]
|
| /openbmc/openbmc/meta-facebook/meta-bletchley/conf/templates/default/ |
| H A D | local.conf.sample | 22 # During a first build the system will download many different source code tarballs
28 # The default is a downloads directory under TOPDIR which is the build directory.
33 # Where to place shared-state files
39 # You can wipe out TMPDIR leaving this directory intact and the build would regenerate
44 # The default is a sstate-cache directory under TOPDIR.
46 #SSTATE_DIR ?= "${TOPDIR}/sstate-cache"
49 # Where to place the build output
68 DISTRO ?= "openbmc-phosphor"
73 # DISTRO ?= "poky-bleeding"
82 # - 'package_deb' for debian style deb files
[all …]
|
| /openbmc/openbmc/meta-facebook/meta-catalina/conf/templates/default/ |
| H A D | local.conf.sample | 22 # During a first build the system will download many different source code tarballs
28 # The default is a downloads directory under TOPDIR which is the build directory.
33 # Where to place shared-state files
39 # You can wipe out TMPDIR leaving this directory intact and the build would regenerate
44 # The default is a sstate-cache directory under TOPDIR.
46 #SSTATE_DIR ?= "${TOPDIR}/sstate-cache"
49 # Where to place the build output
68 DISTRO ?= "openbmc-phosphor"
73 # DISTRO ?= "poky-bleeding"
82 # - 'package_deb' for debian style deb files
[all …]
|
| /openbmc/openbmc/meta-facebook/meta-tiogapass/conf/templates/default/ |
| H A D | local.conf.sample | 22 # During a first build the system will download many different source code tarballs
28 # The default is a downloads directory under TOPDIR which is the build directory.
33 # Where to place shared-state files
39 # You can wipe out TMPDIR leaving this directory intact and the build would regenerate
44 # The default is a sstate-cache directory under TOPDIR.
46 #SSTATE_DIR ?= "${TOPDIR}/sstate-cache"
49 # Where to place the build output
68 DISTRO ?= "openbmc-phosphor"
73 # DISTRO ?= "poky-bleeding"
82 # - 'package_deb' for debian style deb files
[all …]
|
| /openbmc/openbmc/meta-facebook/meta-yosemite4/meta-yosemite4n/conf/templates/default/ |
| H A D | local.conf.sample | 22 # During a first build the system will download many different source code tarballs
28 # The default is a downloads directory under TOPDIR which is the build directory.
33 # Where to place shared-state files
39 # You can wipe out TMPDIR leaving this directory intact and the build would regenerate
44 # The default is a sstate-cache directory under TOPDIR.
46 #SSTATE_DIR ?= "${TOPDIR}/sstate-cache"
49 # Where to place the build output
68 DISTRO ?= "openbmc-phosphor"
73 # DISTRO ?= "poky-bleeding"
82 # - 'package_deb' for debian style deb files
[all …]
|
| /openbmc/openbmc/meta-facebook/meta-yosemite4/conf/templates/default/ |
| H A D | local.conf.sample | 22 # During a first build the system will download many different source code tarballs
28 # The default is a downloads directory under TOPDIR which is the build directory.
33 # Where to place shared-state files
39 # You can wipe out TMPDIR leaving this directory intact and the build would regenerate
44 # The default is a sstate-cache directory under TOPDIR.
46 #SSTATE_DIR ?= "${TOPDIR}/sstate-cache"
49 # Where to place the build output
68 DISTRO ?= "openbmc-phosphor"
73 # DISTRO ?= "poky-bleeding"
82 # - 'package_deb' for debian style deb files
[all …]
|
| /openbmc/openbmc/meta-facebook/meta-minerva/conf/templates/default/ |
| H A D | local.conf.sample | 22 # During a first build the system will download many different source code tarballs
28 # The default is a downloads directory under TOPDIR which is the build directory.
33 # Where to place shared-state files
39 # You can wipe out TMPDIR leaving this directory intact and the build would regenerate
44 # The default is a sstate-cache directory under TOPDIR.
46 #SSTATE_DIR ?= "${TOPDIR}/sstate-cache"
49 # Where to place the build output
68 DISTRO ?= "openbmc-phosphor"
73 # DISTRO ?= "poky-bleeding"
82 # - 'package_deb' for debian style deb files
[all …]
|
| /openbmc/openbmc/meta-quanta/meta-s6q/conf/templates/default/ |
| H A D | local.conf.sample | 22 # During a first build the system will download many different source code tarballs
28 # The default is a downloads directory under TOPDIR which is the build directory.
33 # Where to place shared-state files
39 # You can wipe out TMPDIR leaving this directory intact and the build would regenerate
44 # The default is a sstate-cache directory under TOPDIR.
46 #SSTATE_DIR ?= "${TOPDIR}/sstate-cache"
49 # Where to place the build output
68 DISTRO ?= "openbmc-phosphor"
73 # DISTRO ?= "poky-bleeding"
82 # - 'package_deb' for debian style deb files
[all …]
|