/openbmc/openbmc/poky/meta/recipes-devtools/python/python3-installer/ |
H A D | interpreter.patch | 4 Subject: [PATCH] python3-installer: add installer module 15 src/installer/__main__.py | 9 ++++++++- 16 src/installer/scripts.py | 15 +-------------- 19 diff --git a/src/installer/__main__.py b/src/installer/__main__.py 21 --- a/src/installer/__main__.py 22 +++ b/src/installer/__main__.py 46 diff --git a/src/installer/scripts.py b/src/installer/scripts.py 48 --- a/src/installer/scripts.py 49 +++ b/src/installer/scripts.py 63 - # https://github.com/pradyunsg/installer/pull/4#issuecomment-623668717
|
H A D | 0001-src-installer-utils.py-sort-entries-before-writing-o.patch | 4 Subject: [PATCH] src/installer/utils.py: sort entries before writing out 9 Upstream-Status: Submitted [https://github.com/pypa/installer/pull/245] 12 src/installer/utils.py | 2 +- 15 diff --git a/src/installer/utils.py b/src/installer/utils.py 17 --- a/src/installer/utils.py 18 +++ b/src/installer/utils.py
|
/openbmc/openbmc/poky/documentation/sdk-manual/ |
H A D | appendix-obtain.rst | 25 SDK installer script that ships with the Yocto Project. Using this 26 method, you select and download an architecture-specific SDK installer 38 #. *Locate and Download the SDK Installer:* You need to find and 39 download the installer appropriate for your build host, target 42 The installer files (``*.sh``) follow this naming convention: 54 The standard SDK installer does not have the ``-ext`` string as 64 folder and download the following installer:: 68 #. *Run the Installer:* Be sure you have execution privileges and run 69 the installer. Here is an example from the ``Downloads`` 81 Building an SDK Installer [all …]
|
H A D | using.rst | 44 You can download a tarball installer, which includes the pre-built 53 The names of the tarball installer scripts are such that a string 76 For example, the following SDK installer is for a 64-bit 85 installer. For information on building the installer, see the 86 ":ref:`sdk-manual/appendix-obtain:building an sdk installer`" 91 install the extensible SDK in any location when you run the installer. 96 The following command shows how to run the installer given a toolchain 98 architecture. The example assumes the SDK installer is located in 102 Poky (Yocto Project Reference Distro) SDK installer version &DISTRO; 115 are installing the SDK, the installer notifies you and exits. For [all …]
|
H A D | appendix-customizing.rst | 4 Customizing the Extensible SDK standalone installer 8 SDK when using in the standalone installer version. 13 Yocto build, avoiding separate installer artefacts. Please refer to 133 Changing the Extensible SDK Installer Title 136 You can change the displayed title for the SDK installer by setting the 138 rebuilding the SDK installer. For information on how to build an SDK 139 installer, see the ":ref:`sdk-manual/appendix-obtain:building an sdk installer`" 156 creates an SDK installer title that applies across your distribution. As 194 $ oe-publish-sdk some_path/sdk-installer.sh path_to_shared_http_directory 209 When you build the installer for the Extensible SDK, the default [all …]
|
H A D | extensible.rst | 52 installer archives, which can get very large. There is only one environment 60 #. *Setting up the Extensible SDK from a standalone installer*. This has the 81 Setting up the Extensible SDK from a standalone installer 87 You can download a tarball installer, which includes the pre-built 97 The names of the tarball installer scripts are such that a string 122 For example, the following SDK installer is for a 64-bit 131 installer. For information on building the installer, see the 132 :ref:`sdk-manual/appendix-obtain:building an sdk installer` 137 install the extensible SDK in any location when you run the installer. 142 The following command shows how to run the installer given a toolchain [all …]
|
/openbmc/openbmc/meta-arm/meta-arm-systemready/recipes-test/arm-systemready-linux-distros/files/unattended-boot-conf/Debian/ |
H A D | preseed.cfg | 8 d-i debian-installer/language string en 9 d-i debian-installer/country string GB 10 d-i debian-installer/locale string en_GB.UTF-8 18 d-i base-installer/install-recommends boolean false 58 d-i grub-installer/only_debian boolean true 59 d-i grub-installer/bootdev string /dev/vda 60 d-i grub-installer/bootloader-id string debian 61 d-i grub-installer/efi-directory string /boot/efi 64 d-i debian-installer/exit-on-error boolean true
|
/openbmc/qemu/.gitlab-ci.d/ |
H A D | windows.yml | 31 - Write-Output "Acquiring msys2.exe installer at $(Get-Date -Format u)" 39 Write-Output "Cached installer sig" ; 41 Write-Output "Mis-matched installer sig, new installer download required" ; 47 Write-Output "Matched installer sig, cached installer still valid" 50 Write-Output "No cached installer sig, new installer download required" ; 56 Write-Output "Fetching latest installer" ; 62 Write-Output "Using cached installer" 64 - Write-Output "Invoking msys2.exe installer at $(Get-Date -Format u)"
|
H A D | crossbuild-template.yml | 42 - section_start installer "Building the installer" 44 then make installer; 48 - section_end installer
|
/openbmc/openbmc/poky/scripts/ |
H A D | install-buildtools | 3 # Buildtools and buildtools extended installer helper script 16 # (2) using --base-url, --release, --installer-version and --build-date 20 # --installer-version 3.0+snapshot 28 # (4) using --base-url, --release and --installer-version 32 # --installer-version 3.0.2 133 help='URL from where to fetch buildtools SDK installer, not ' 138 help='filename for the buildtools SDK installer to be installed ' 150 parser.add_argument('-V', '--installer-version', 196 "--release --installer-version arguments.") 240 # Fetch installer [all …]
|
H A D | oe-publish-sdk | 46 logger.error("%s is a directory - expected path to SDK installer file" % target_sdk) 125 …nt('-k', '--keep-orig', help='When published to a remote host, the eSDK installer gets deleted by … 127 parser.add_argument('sdk', help='Extensible SDK to publish (path to .sh installer file)')
|
/openbmc/openbmc/poky/meta/recipes-devtools/python/ |
H A D | python3-installer_0.7.0.bb | 3 HOMEPAGE = "https://installer.readthedocs.io/" 4 BUGTRACKER = "https://github.com/pypa/installer/issues" 10 file://0001-src-installer-utils.py-sort-entries-before-writing-o.patch" 17 DEPENDS:remove:class-native = "python3-build-native python3-installer-native"
|
H A D | python3-flit-core_3.10.1.bb | 16 DEPENDS:remove:class-native = " python3-build-native python3-installer-native"
|
/openbmc/openbmc/poky/documentation/ref-manual/ |
H A D | system-requirements.rst | 325 installer and automatically installs the tools for you: 334 --installer-version &DISTRO; 337 checksum of the download will be verified, the installer will be run 342 script will by default tell the installer to install in:: 377 download and run a pre-built :term:`buildtools` installer yourself with the following 385 traditional installer:: 389 Here is an example for the extended installer:: 393 An example for the make-only installer:: 401 #. As instructed by the installer script, you will have to source the tools 417 Building and running your own :term:`buildtools` installer applies only when you [all …]
|
/openbmc/openbmc/poky/meta/classes-recipe/ |
H A D | python_pep517.bbclass | 10 # This class will build a wheel in do_compile, and use pypa/installer to install 13 DEPENDS:append = " python3-build-native python3-installer-native" 28 # pypa/installer option to control the bytecode compilation 52 …nativepython3 -m installer ${INSTALL_WHEEL_COMPILE_BYTECODE} --interpreter "${USRBINPATH}/env ${PE…
|
/openbmc/openbmc/poky/meta/lib/oeqa/buildperf/ |
H A D | test_basic.py | 104 installer = os.path.join( 107 # Measure installer size 108 self.measure_disk_usage(installer, 'installer_bin', 'eSDK installer', 115 self.measure_cmd_resources([installer, '-y', '-d', deploy_dir],
|
/openbmc/qemu/python/ |
H A D | setup.py | 3 QEMU tooling installer script 30 QEMU tooling installer
|
/openbmc/u-boot/doc/ |
H A D | README.distro | 32 board-specific installer/boot-configuration support in a distro. 36 flash before running the distro installer. Even on boards that do not conform 38 distro installer logic would be to install a board-specific U-Boot package to 90 One example extlinux.conf generated by the Fedora installer is: 150 LABEL fedora-installer-fk 151 MENU LABEL Fedora installer w/ Fedora kernel 152 LINUX fedora-installer/vmlinuz 153 INITRD fedora-installer/initrd.img.orig 154 FDTDIR fedora-installer/dtb
|
/openbmc/openbmc/poky/meta/recipes-devtools/syslinux/ |
H A D | syslinux_6.04-pre2.bb | 45 # When building the installer, CC is used to link. When building the bootloader, 72 # Tasks for native/nativesdk which just build the installer. 79 oe_runmake firmware="bios" installer 97 # Tasks for target which ship the precompiled bootloader and installer
|
/openbmc/openbmc/poky/meta/files/ |
H A D | toolchain-shar-extract.sh | 49 …echo "Error: Incompatible SDK installer! Your host is $INST_ARCH and this SDK was built for $SDK_A… 130 titlestr="@SDK_TITLE@ installer version @SDK_VERSION@" 145 …echo "Error: Incompatible SDK installer! Your host gcc version is $INST_GCC_VER and this SDK was b… 292 # delete the relocating script, so that user is forced to re-run the installer
|
/openbmc/qemu/ |
H A D | qemu.nsi | 3 ; This NSIS script creates an installer for QEMU on Windows. 40 ; Build a unicode installer 48 ; The name of the installer.
|
/openbmc/qemu/docs/system/ppc/ |
H A D | amigang.rst | 48 https://sourceforge.net/projects/amigaone-linux/files/debian-installer/. 54 -cdrom "A1 Linux Net Installer.iso" \ 63 installer becomes visible. The ``ati-vga`` RV100 emulation is not
|
/openbmc/qemu/tests/docker/ |
H A D | test-mingw | 31 make installer
|
/openbmc/openpower-inventory-upload/ |
H A D | .gitignore | 33 # Installer logs
|
/openbmc/qemu/tests/functional/ |
H A D | test_alpha_clipper.py | 18 'installer-alpha/20090123lenny10/images/cdrom/vmlinuz'),
|