| /openbmc/u-boot/tools/buildman/ |
| H A D | toolchain.py | 47 class Toolchain: class
48 """A single toolchain
54 arch: Architecture of toolchain as determined from the first
56 priority: Toolchain priority (0=highest, 20=lowest)
57 override_toolchain: Toolchain to use for sandbox, overriding the normal
62 """Create a new toolchain object.
66 test: True to run the toolchain to test it
68 priority: Priority to use for this toolchain, or PRIORITY_CALC to
116 """Return the priority of the toolchain.
122 fname: Filename of toolchain
[all …]
|
| H A D | builderthread.py | 178 # We are going to have to build it. First, get a toolchain
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:
307 # Write the build result and toolchain information.
316 with open(os.path.join(build_dir, 'toolchain'), 'w') as fd:
[all …]
|
| H A D | README | 64 built (e.g. because of a toolchain update), use the -f flag.
176 [toolchain]
183 [toolchain-alias]
190 This selects the available toolchain paths. Add the base directory for
196 The toolchain-alias section indicates that the i386 toolchain should be used
199 Note that you can also specific exactly toolchain prefixes if you like:
201 [toolchain-prefix]
206 [toolchain-prefix]
209 This tells buildman that you want to use this exact toolchain for the arm
211 [toolchain] settings.
[all …]
|
| H A D | bsettings.py | 74 print >>f, '''[toolchain]
78 [toolchain-prefix]
82 [toolchain-alias]
84 # Indicates which toolchain should be used to build for that arch
|
| /openbmc/u-boot/ |
| H A D | .travis.yml | 14 - ubuntu-toolchain-r-test
15 - llvm-toolchain-trusty-7
44 - echo -e "[toolchain]\nroot = /usr" > ~/.buildman
46 - echo -e "\n[toolchain-alias]\nsh = sh2\n" >> ~/.buildman
69 # install toolchains based on TOOLCHAIN} variable
70 - if [[ "${TOOLCHAIN}" == *m68k* ]]; then ./tools/buildman/buildman --fetch-arch m68k ; fi
71 …- if [[ "${TOOLCHAIN}" == *microblaze* ]]; then ./tools/buildman/buildman --fetch-arch microblaze …
72 - if [[ "${TOOLCHAIN}" == *mips* ]]; then ./tools/buildman/buildman --fetch-arch mips ; fi
73 - if [[ "${TOOLCHAIN}" == *sh* ]]; then ./tools/buildman/buildman --fetch-arch sh2 ; fi
74 - if [[ "${TOOLCHAIN}" == *i386* ]]; then
[all …]
|
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | external-toolchain.rst | 3 Optionally Using an External Toolchain
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
[all …]
|
| /openbmc/openbmc/poky/meta/lib/oeqa/selftest/cases/ |
| H A D | gcc.py | 91 @OETestTag("toolchain-user")
96 @OETestTag("toolchain-user")
101 @OETestTag("toolchain-user")
106 @OETestTag("toolchain-user")
111 @OETestTag("toolchain-user")
116 @OETestTag("toolchain-user")
122 @OETestTag("toolchain-user")
128 @OETestTag("toolchain-system")
134 @OETestTag("toolchain-system")
140 @OETestTag("toolchain-system")
[all …]
|
| H A D | resulttooltests.py | 136 "select_tags": ["toolchain-user", "toolchain-system"],
163 … "select_tags": ["toolchain-user", "toolchain-system"],
178 … "select_tags": ["toolchain-user", "toolchain-system"],
197 "select_tags": ["toolchain-user", "toolchain-system"],
230 … "select_tags": ["toolchain-user", "toolchain-system"],
|
| /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/conf/ |
| H A D | layer.conf | 7 BBFILE_COLLECTIONS += "arm-toolchain"
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/openbmc/meta-raspberrypi/recipes-multimedia/omxplayer/omxplayer/ |
| H A D | 0001-Remove-Makefile.include-which-includes-hardcoded.patch | 52 -TOOLCHAIN :=$(BUILDROOT)/output/host/usr/
59 -TOOLCHAIN :=/home/dc4/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/
61 -#SYSROOT :=$(TOOLCHAIN)/arm-bcm2708hardfp-linux-gnueabi/sysroot
71 -LD := $(TOOLCHAIN)/bin/$(HOST)-ld --sysroot=$(SYSROOT)
72 -CC := $(TOOLCHAIN)/bin/$(HOST)-gcc --sysroot=$(SYSROOT)
73 -CXX := $(TOOLCHAIN)/bin/$(HOST)-g++ --sysroot=$(SYSROOT)
74 -OBJDUMP := $(TOOLCHAIN)/bin/$(HOST)-objdump
75 -RANLIB := $(TOOLCHAIN)/bin/$(HOST)-ranlib
76 -STRIP := $(TOOLCHAIN)/bin/$(HOST)-strip
77 -AR := $(TOOLCHAIN)/bin/$(HOST)-ar
|
| /openbmc/linux/Documentation/arch/arc/ |
| H A D | arc.rst | 13 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/openbmc/poky/meta/lib/oeqa/manual/ |
| H A D | sdk.json | 17 …toolchain tarball matching your host from public autobuilder \n \ta. Goto https://autobuilder.y…
18 "expected_results": "Toolchain gets installed successfully."
|
| /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
8 SUMMARY = "Arm GNU Toolchain - AArch32 bare-metal target (arm-none-eabi)"
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
8 SUMMARY = "Arm GNU Toolchain - AArch64 bare-metal target (aarch64-none-elf)"
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/poky/documentation/sdk-manual/ |
| H A D | working-projects.rst | 4 Using the SDK Toolchain Directly
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`
77 #. *Source the Cross-Toolchain Environment Setup File:* As described
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
[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
76 | Toolchain | Yes | Yes [1]_ |
82 | | | w/toolchain) |
97 .. [1] Extensible SDK contains the toolchain and debugger if :term:`SDK_EXT_TYPE`
107 The Cross-Development Toolchain
110 The :term:`Cross-Development Toolchain` consists
114 functionality. This toolchain is created by running a SDK installer
[all …]
|
| 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/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 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/yocto-&DISTRO;/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/openbmc/meta-openembedded/meta-python/recipes-devtools/python/ |
| H A D | python3-matplotlib_3.7.2.bb | 43 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/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/u-boot/doc/ |
| H A D | README.boston | 35 Toolchain
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/
44 The "IMG GNU Linux Toolchain" is capable of building for all current MIPS ISAs,
|
| /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/meta-openembedded/meta-oe/recipes-extended/iotop/ |
| H A D | iotop_1.27.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/linux/Documentation/arch/openrisc/ |
| H A D | openrisc_port.rst | 17 Build instructions for OpenRISC toolchain and Linux
21 toolchain and, perhaps, the architectural simulator. Steps to get these bits
24 1) Toolchain
26 Toolchain binaries can be obtained from openrisc.io or our github releases page.
28 or Stafford's toolchain build and release scripts.
33 building https://github.com/stffrdhrn/or1k-toolchain-build
|