| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | external-toolchain.rst | 6 You might want to use an external toolchain as part of your development. 10 - Understand where the installed toolchain resides. For cases where you 11 need to build the external toolchain, you would need to take separate 12 steps to build and install the toolchain. 14 - Make sure you add the layer that contains the toolchain to your 19 to the location in which you installed the toolchain. 21 The toolchain configuration is very flexible and customizable. It 27 OpenEmbedded build system to use its internally built toolchain (i.e. 30 the Mentor Graphics Sourcery G++ Toolchain. Support for this toolchain resides 35 Another example of external toolchain layer is [all …]
|
| /openbmc/openbmc/meta-arm/meta-arm-toolchain/conf/ |
| H A D | layer.conf | 8 BBFILE_PATTERN_arm-toolchain := "^${LAYERDIR}/" 9 BBFILE_PRIORITY_arm-toolchain = "5" 11 LAYERDEPENDS_arm-toolchain = "core" 12 LAYERSERIES_COMPAT_arm-toolchain = "styhead walnascar"
|
| /openbmc/qemu/tests/docker/dockerfiles/ |
| H A D | debian-toolchain.docker | 2 # Docker toolchain cross-compiler 4 # This dockerfile is used for building a cross-compiler toolchain. 5 # The script for building the toolchain is supplied via extra-files. 30 ADD build-toolchain.sh /root/build-toolchain.sh 32 RUN cd /root && ./build-toolchain.sh 34 # Throw away the extra toolchain build deps, the downloaded source, 36 # then copying the built toolchain from stage 0.
|
| /openbmc/openbmc/meta-arm/meta-arm-toolchain/ |
| H A D | README.md | 1 meta-arm-toolchain Yocto Layer 9 Pre-built Arm toolchain for bare-metal development 12 Recipes for pre-built GNU Arm toolchain for bare-metal development are provided 13 under ``recipes-devtools/external-arm-toolchain/``. 18 This recipe provides support for pre-built GNU Arm Embedded toolchain for 27 This recipe provides support for pre-built GNU Arm toolchain for bare-metal
|
| /openbmc/openbmc/meta-arm/meta-arm-toolchain/recipes-devtools/external-arm-toolchain/ |
| H A D | gcc-arm-none-eabi_13.3.rel1.bb | 4 require arm-binary-toolchain.inc 14 SRC_URI = "https://developer.arm.com/-/media/Files/downloads/gnu/${PV}/binrel/arm-gnu-toolchain-${P… 18 S = "${WORKDIR}/arm-gnu-toolchain-${PV}-${HOST_ARCH}-${BINNAME}" 20 UPSTREAM_CHECK_URI = "https://developer.arm.com/downloads/-/arm-gnu-toolchain-downloads" 21 UPSTREAM_CHECK_REGEX = "arm-gnu-toolchain-(?P<pver>\d+\.\d*\.[A-z]*\d*).*-${HOST_ARCH}-${BINNAME}\.…
|
| H A D | gcc-aarch64-none-elf_13.3.rel1.bb | 4 require arm-binary-toolchain.inc 14 SRC_URI = "https://developer.arm.com/-/media/Files/downloads/gnu/${PV}/binrel/arm-gnu-toolchain-${P… 18 S = "${WORKDIR}/arm-gnu-toolchain-${PV}-${HOST_ARCH}-${BINNAME}" 20 UPSTREAM_CHECK_URI = "https://developer.arm.com/downloads/-/arm-gnu-toolchain-downloads" 21 UPSTREAM_CHECK_REGEX = "arm-gnu-toolchain-(?P<pver>\d+\.\d*\.[A-z]*\d*).*-${HOST_ARCH}-${BINNAME}\.…
|
| /openbmc/u-boot/tools/buildman/ |
| H A D | builderthread.py | 179 if not self.toolchain: 181 self.toolchain = self.builder.toolchains.Select(brd.arch) 189 if self.toolchain: 201 env = self.toolchain.MakeEnvironment(self.builder.full_path) 232 args.extend(self.toolchain.MakeArgs()) 258 result.toolchain = self.toolchain 306 if result.toolchain: 317 print >>fd, 'gcc', result.toolchain.gcc 318 print >>fd, 'path', result.toolchain.path 319 print >>fd, 'cross', result.toolchain.cross [all …]
|
| H A D | toolchain.py | 266 toolchain = Toolchain(fname, test, verbose, priority, arch, 268 add_it = toolchain.ok 269 if toolchain.arch in self.toolchains: 270 add_it = (toolchain.priority < 271 self.toolchains[toolchain.arch].priority) 273 self.toolchains[toolchain.arch] = toolchain 277 (toolchain.gcc, toolchain.priority, toolchain.arch, 278 self.toolchains[toolchain.arch].priority)) 600 toolchain = Toolchain(compiler_fname_list[0], True, True)
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/iotop/ |
| H A D | iotop_1.29.bb | 16 EXTRA_OEMAKE:append:toolchain-clang:riscv64 = " NO_FLTO=1" 17 EXTRA_OEMAKE:append:toolchain-clang:riscv32 = " NO_FLTO=1" 21 LDFLAGS:append:toolchain-clang:arm = " -fuse-ld=lld"
|
| /openbmc/qemu/tests/docker/ |
| H A D | Makefile.include | 103 debian-toolchain-run = \ 109 $(DOCKER_FILES_DIR)/$1.d/build-toolchain.sh, \ 120 debian-toolchain = $(call debian-toolchain-run,$(patsubst docker-image-%,%,$1)) 122 docker-image-debian-microblaze-cross: $(DOCKER_FILES_DIR)/debian-toolchain.docker \ 123 $(DOCKER_FILES_DIR)/debian-microblaze-cross.d/build-toolchain.sh 124 $(call debian-toolchain, $@) 131 DOCKER_VIRTUAL_IMAGES := debian-bootstrap debian-toolchain
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/nodejs/nodejs/ |
| H A D | 0004-v8-don-t-override-ARM-CFLAGS.patch | 27 tools/v8_gypfiles/toolchain.gypi | 52 ++------------------------------ 30 diff --git a/tools/v8_gypfiles/toolchain.gypi b/tools/v8_gypfiles/toolchain.gypi 32 --- a/tools/v8_gypfiles/toolchain.gypi 33 +++ b/tools/v8_gypfiles/toolchain.gypi
|
| /openbmc/openbmc/poky/meta/recipes-core/meta/ |
| H A D | meta-extsdk-toolchain.bb | 1 SUMMARY = "Extensible SDK toolchain meta-recipe" 2 DESCRIPTION = "Meta-recipe for ensuring the build directory contains all appropriate toolchain pack… 27 sigfile = os.path.join(outdir, 'locked-sigs-extsdk-toolchain.inc')
|
| H A D | meta-ide-support.bb | 2 DESCRIPTION = "Meta package for ensuring the build directory contains all appropriate toolchain pac… 9 inherit toolchain-scripts nopackages deploy testsdk
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-kernel/drgn/ |
| H A D | python3-drgn_0.0.31.bb | 20 DEPENDS:append:toolchain-clang:class-target = "\ 25 OPENMP_LIB:toolchain-clang:class-target = "openmp" 52 OPENMP_LIB_NAME:toolchain-clang:class-target = "omp"
|
| /openbmc/openbmc/poky/documentation/sdk-manual/ |
| H A D | using.rst | 19 ":ref:`sdk-manual/working-projects:using the sdk toolchain directly`" chapter 25 The Standard SDK provides a cross-development toolchain and libraries 27 SDK if you want a more traditional toolchain experience as compared to 45 toolchain, the ``runqemu`` script, and support files from the 46 appropriate :yocto_dl:`toolchain </releases/yocto/&DISTRO_REL_LATEST_TAG;/toolchain/>` directory wi… 57 poky-glibc-host_system-image_type-arch-toolchain-release_version.sh 80 poky-glibc-x86_64-core-image-sato-i586-toolchain-DISTRO.sh 96 The following command shows how to run the installer given a toolchain 101 $ ./Downloads/poky-glibc-x86_64-core-image-sato-i586-toolchain-&DISTRO;.sh
|
| H A D | working-projects.rst | 7 You can use the SDK toolchain directly with Makefile and Autotools-based 13 Once you have a suitable :ref:`sdk-manual/intro:the cross-development toolchain` 78 earlier in the manual, installing the cross-toolchain creates a 79 cross-toolchain environment setup script in the directory that the 120 project, you can use the cross-toolchain by just passing the 123 directory in which you installed the cross-toolchain. For example, 128 the appropriate cross-toolchain tools:: 141 cross-toolchain environment setup script and how they are used or 148 architecture that the installed cross-toolchain supports:: 163 Simple Makefile-based projects use and interact with the cross-toolchain [all …]
|
| H A D | intro.rst | 17 - *Cross-Development Toolchain*: This toolchain contains a compiler, 43 toolchain binaries are produced for any given architecture. This feature 55 cross-toolchain and matching sysroots (target and native) all built 56 by the OpenEmbedded build system (e.g. the SDK). The toolchain and 82 | | | w/toolchain) | 97 .. [1] Extensible SDK contains the toolchain and debugger if :term:`SDK_EXT_TYPE` 114 functionality. This toolchain is created by running a SDK installer 117 cross-toolchain works with a matching target sysroot. 126 used to build the cross-toolchain. 143 - installed the cross-toolchain tarball and [all …]
|
| H A D | appendix-obtain.rst | 27 and then run the script to hand-install the toolchain. 29 Follow these steps to locate and hand-install the toolchain: 32 :yocto_dl:`/releases/yocto/&DISTRO_REL_LATEST_TAG;/toolchain/` 43 ``poky-glibc-host_system-core-image-type-arch-toolchain[-ext]-release.sh``: 66 poky-glibc-x86_64-core-image-sato-core2-64-qemux86-64-toolchain-&DISTRO;.sh 72 $ ~/Downloads/poky-glibc-x86_64-core-image-sato-core2-64-qemux86-64-toolchain-&DISTRO;.sh 75 toolchain. See the 122 toolchain designed to run on an architecture that differs from your 161 binaries. If you want to use the toolchain to build these types 176 $ ./poky-glibc-x86_64-core-image-sato-core2-64-toolchain-ext-&DISTRO;.sh [all …]
|
| /openbmc/u-boot/board/keymile/scripts/ |
| H A D | develop-common.txt | 5 nfsargs=setenv bootargs root=/dev/nfs rw nfsroot=${serverip}:${toolchain}/${arch} 8 toolchain=/opt/eldk
|
| /openbmc/openbmc/poky/meta/recipes-graphics/xorg-lib/libxt/ |
| H A D | libxt_fix_for_x32.patch | 4 Subject: [PATCH] libxt: fix compilatoin with x32 toolchain 8 This fixes compilation with x32 toolchain.
|
| /openbmc/openbmc/meta-openembedded/meta-gnome/recipes-gimp/gegl/ |
| H A D | gegl_0.4.62.bb | 18 DEPENDS:append:toolchain-clang = " openmp" 19 DEPENDS:remove:toolchain-clang:riscv32 = "openmp" 20 DEPENDS:remove:toolchain-clang:powerpc = "openmp"
|
| /openbmc/openbmc/meta-openembedded/meta-initramfs/recipes-devtools/mtd/ubi-utils-klibc-2.0.2/ |
| H A D | 0001-libmissing.h-fix-klibc-build-when-using-glibc-toolch.patch | 4 Subject: [PATCH] libmissing.h: fix klibc build when using glibc toolchain 7 Note: build with musl toolchain is ok even without this patch.
|
| /openbmc/openbmc/poky/meta/conf/distro/include/ |
| H A D | tcmode-default.inc | 2 # Default toolchain configuration 39 # Rust toolchain preferred versions:
|
| /openbmc/openbmc/meta-arm/meta-arm/recipes-security/trusted-services/ |
| H A D | trusted-services.inc | 42 # Use the Yocto cmake toolchain for external components of the arm-linux TS deployments, 43 # and the TS toolchain for opteesp and sp deployments 49 return '-DTS_EXTERNAL_LIB_TOOLCHAIN_FILE=${WORKDIR}/toolchain.cmake'
|
| /openbmc/u-boot/doc/ |
| H A D | README.boston | 38 If building for MIPSr6 then you will need a toolchain including GCC 5.x or 39 newer, or the Codescape toolchain available for download from Imagination 42 http://codescape-mips-sdk.imgtec.com/components/toolchain/2015.06-05/
|