Home
last modified time | relevance | path

Searched refs:toolchain (Results 1 – 25 of 329) sorted by relevance

12345678910>>...14

/openbmc/openbmc/meta-arm/meta-arm-toolchain/conf/distro/include/
H A Dtcmode-external-arm.inc2 # Configuration to use an external Arm binary toolchain
24 # Blacklist toolchain recipes as a belt-and-suspenders way to use the external toolchain
25 SKIP_RECIPE[glibc] = "Using external toolchain"
26 SKIP_RECIPE[libgcc] = "Using external toolchain"
27 SKIP_RECIPE[gcc-cross] = "Using external toolchain"
28 SKIP_RECIPE[gcc-cross-aarch64] = "Using external toolchain"
29 SKIP_RECIPE[gcc-cross-arm] = "Using external toolchain"
30 SKIP_RECIPE[gcc-runtime] = "Using external toolchain"
31 SKIP_RECIPE[gcc-sanitizers] = "Using external toolchain"
41 PREFERRED_PROVIDER_glibc = "external-arm-toolchain"
[all …]
/openbmc/openbmc/meta-arm/meta-arm-toolchain/
H A DREADME.md1 meta-arm-toolchain Yocto Layer
9 Recipes for pre-built GNU Arm toolchain for Linux development are provided under
10 ``recipes-devtools/external-arm-toolchain/``.
12 external-arm-toolchain.bb
21 In order to use any of pre-built Arm toolchain versions (8.2, 8.3, 9.2 and so
25 toolchain:
28 EXTERNAL_TOOLCHAIN = "<path-to-the-toolchain>"
43 Since this pre-built GNU-A tool-set simply replaces OE toolchain, so it is
71 most of the components from pre-built toolchain instead.
73 Pre-built Arm toolchain for bare-metal development
[all …]
/openbmc/openbmc/poky/documentation/dev-manual/
H A Dexternal-toolchain.rst6 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/qemu/tests/docker/dockerfiles/
H A Ddebian-toolchain.docker2 # 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.
28 ADD build-toolchain.sh /root/build-toolchain.sh
30 RUN cd /root && ./build-toolchain.sh
32 # Throw away the extra toolchain build deps, the downloaded source,
34 # then copying the built toolchain from stage 0.
/openbmc/openbmc/meta-arm/meta-arm-toolchain/conf/
H A Dlayer.conf8 BBFILE_PATTERN_arm-toolchain := "^${LAYERDIR}/"
9 BBFILE_PRIORITY_arm-toolchain = "5"
11 LAYERDEPENDS_arm-toolchain = "core"
12 LAYERSERIES_COMPAT_arm-toolchain = "nanbield scarthgap"
/openbmc/u-boot/tools/buildman/
H A Dbuilderthread.py179 if not self.toolchain:
189 if self.toolchain:
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
320 print >>fd, 'arch', result.toolchain.arch
355 cmd = ['%ssize' % self.toolchain.cross, fname]
[all …]
H A Dtoolchain.py266 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-arm/meta-arm-toolchain/recipes-devtools/external-arm-toolchain/
H A Dgcc-arm-none-eabi_13.2.Rel1.bb4 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 Dgcc-aarch64-none-elf_13.2.Rel1.bb4 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/openbmc/meta-openembedded/meta-python/recipes-devtools/python/
H A Dpython3-matplotlib_3.7.2.bb43 LDFLAGS:append:toolchain-clang = " -fuse-ld=lld"
44 LDFLAGS:remove:toolchain-clang:mips = "-fuse-ld=lld"
45 LDFLAGS:remove:toolchain-clang:riscv64 = "-fuse-ld=lld"
46 LDFLAGS:remove:toolchain-clang:riscv32 = "-fuse-ld=lld"
60 ENABLELTO:toolchain-clang:riscv64 = "echo enable_lto = False >> ${S}/mplsetup.cfg"
61 ENABLELTO:toolchain-clang:riscv32 = "echo enable_lto = False >> ${S}/mplsetup.cfg"
62 ENABLELTO:toolchain-clang:mips = "echo enable_lto = False >> ${S}/mplsetup.cfg"
/openbmc/linux/Documentation/arch/arc/
H A Darc.rst13 Good place to start to find relevant FOSS projects, toolchain releases,
62 (GNU toolchain, dtc, make etc) installed on the platform.
64 In both cases, up-to-date GNU toolchain for ARC for the host is needed.
65 Synopsys offers prebuilt toolchain releases which can be used for this purpose,
68 - Synopsys GNU toolchain releases:
69 `<https://github.com/foss-for-synopsys-dwc-arc-processors/toolchain/releases>`_
74 - Bootlin's toolchain collection: `<https://toolchains.bootlin.com>`_
76 Once the toolchain is installed in the system, make sure its "bin" folder
78 ``CROSS_COMPILE=arc-linux`` (or whatever matches installed ARC toolchain prefix)
/openbmc/qemu/tests/docker/
H A DMakefile.include94 debian-toolchain-run = \
100 $(DOCKER_FILES_DIR)/$1.d/build-toolchain.sh, \
111 debian-toolchain = $(call debian-toolchain-run,$(patsubst docker-image-%,%,$1))
113 docker-image-debian-microblaze-cross: $(DOCKER_FILES_DIR)/debian-toolchain.docker \
114 $(DOCKER_FILES_DIR)/debian-microblaze-cross.d/build-toolchain.sh
115 $(call debian-toolchain, $@)
123 DOCKER_VIRTUAL_IMAGES := debian-bootstrap debian-toolchain
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/nodejs/nodejs/
H A D0004-v8-don-t-override-ARM-CFLAGS.patch27 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/meta-openembedded/meta-oe/recipes-extended/iotop/
H A Diotop_1.26.bb16 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/openbmc/poky/documentation/sdk-manual/
H A Dusing.rst19 ":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/yocto-&DISTRO;/toolchain/>` directory within
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 Dworking-projects.rst7 You can use the SDK toolchain directly with Makefile and Autotools-based
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::
148 architecture that the installed cross-toolchain supports::
164 environment variables established when you run the cross-toolchain
169 example that lets you see how you can use cross-toolchain environment
270 earlier in the manual, installing the cross-toolchain creates a
[all …]
H A Dintro.rst17 - *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 Dappendix-obtain.rst27 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/yocto-&DISTRO;/toolchain/`
43 ``poky-glibc-host_system-core-image-type-arch-toolchain[-ext]-release.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
179 toolchain. See the
188 After installing the toolchain, for some use cases you might need to
236 installed the toolchain (e.g. ``poky_sdk``).
[all …]
/openbmc/linux/arch/mips/
H A DMakefile246 cflags-$(toolchain-msa) += -DTOOLCHAIN_SUPPORTS_MSA
248 toolchain-virt := $(call cc-option-yn,$(mips-cflags) -mvirt)
249 cflags-$(toolchain-virt) += -DTOOLCHAIN_SUPPORTS_VIRT
254 toolchain-xpa := $(call cc-option-yn,$(xpa-cflags-y) -mxpa)
255 cflags-$(toolchain-xpa) += -DTOOLCHAIN_SUPPORTS_XPA
256 toolchain-crc := $(call cc-option-yn,$(mips-cflags) -Wa$(comma)-mcrc)
257 cflags-$(toolchain-crc) += -DTOOLCHAIN_SUPPORTS_CRC
258 toolchain-dsp := $(call cc-option-yn,$(mips-cflags) -Wa$(comma)-mdsp)
259 cflags-$(toolchain-dsp) += -DTOOLCHAIN_SUPPORTS_DSP
260 toolchain-ginv := $(call cc-option-yn,$(mips-cflags) -Wa$(comma)-mginv)
[all …]
/openbmc/openbmc/poky/meta/recipes-core/meta/
H A Dmeta-extsdk-toolchain.bb1 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')
/openbmc/openbmc/meta-arm/meta-arm-toolchain/recipes-bsp/grub/
H A Dgrub-external-arm.inc2 # Since external-arm toolchain uses aarch64-none-linux-gnu triplet,
4 # toolchain, grub needs passing the correct --target to configure script
/openbmc/openbmc/meta-arm/ci/
H A Dexternal-gccarm.yml6 SKIP_RECIPE[gcc-cross-arm] = "Using external toolchain"
10 …# This must be done here instead of the recipe because of all the libraries in the toolchain have …
/openbmc/u-boot/board/keymile/scripts/
H A Ddevelop-common.txt5 nfsargs=setenv bootargs root=/dev/nfs rw nfsroot=${serverip}:${toolchain}/${arch}
8 toolchain=/opt/eldk
/openbmc/openbmc/meta-arm/meta-arm/recipes-security/trusted-services/
H A Dtrusted-services.inc43 # Use the Yocto cmake toolchain for arm-linux TS deployments and
44 # the TS opteesp toolchain for opteesp TS deployments
47 '-DTS_EXTERNAL_LIB_TOOLCHAIN_FILE=${WORKDIR}/toolchain.cmake', \
/openbmc/openbmc/meta-openembedded/meta-gnome/recipes-gimp/gegl/
H A Dgegl_0.4.48.bb16 DEPENDS:append:toolchain-clang = " openmp"
17 DEPENDS:remove:toolchain-clang:riscv32 = "openmp"
18 DEPENDS:remove:toolchain-clang:powerpc = "openmp"

12345678910>>...14