diff options
| author | Sam Thursfield <sam.thursfield@codethink.co.uk> | 2017-06-14 22:58:52 +0100 |
|---|---|---|
| committer | Sam Thursfield <sam.thursfield@codethink.co.uk> | 2017-07-07 11:44:36 +0000 |
| commit | 23a3a3c746261c3ecb2aa961d91f988f0602a032 (patch) | |
| tree | a98e6f2d5451025f6ebd0c660c03db1bf306d19e /elements/gnu-toolchain/gcc.bst | |
| parent | aaefeb1e22579deef6a7829d055eee70c8a7a4f0 (diff) | |
| download | definitions-23a3a3c746261c3ecb2aa961d91f988f0602a032.tar.gz | |
Support cross-building the stage1 and stage2 components
This requires a feature recently added to BuildStream (in commit
03906221) that adds a framework for elements to support being
cross-compiled.
To build an armv8l64 native toolchain and sysroot on an x86_64 build
machine, for example, you can do this:
bst build --target-arch=armv8l64 gnu-toolchain/stage2.bst
You can then run `bst checkout` to get at the resulting binaries and
copy them onto an armv8l64 machine where they can be executed.
Diffstat (limited to 'elements/gnu-toolchain/gcc.bst')
| -rw-r--r-- | elements/gnu-toolchain/gcc.bst | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/elements/gnu-toolchain/gcc.bst b/elements/gnu-toolchain/gcc.bst index 5815cf01..e9a54834 100644 --- a/elements/gnu-toolchain/gcc.bst +++ b/elements/gnu-toolchain/gcc.bst @@ -30,7 +30,7 @@ config: # 2. Avoid having more than one copy of ZLib in use on the system # 3. Multilib does not make sense in Baserock. - | - case "%{bst-arch}" in + case "%{bst-target-arch}" in armv7lhf) ARCH_FLAGS="--with-arch=armv7-a \ --with-cpu=cortex-a9 \ --with-tune=cortex-a9 \ @@ -50,7 +50,7 @@ config: build-commands: - | - case "%{bst-arch}" in + case "%{bst-target-arch}" in armv5*) sed -i "s/--host=none/--host=armv5/" o/Makefile sed -i "s/--target=none/--target=armv5/" o/Makefile ;; armv7*) sed -i "s/--host=none/--host=armv7a/" o/Makefile |