diff options
author | Richard Maw <richard.maw@codethink.co.uk> | 2014-08-18 17:05:22 +0000 |
---|---|---|
committer | Richard Maw <richard.maw@codethink.co.uk> | 2014-08-18 17:05:22 +0000 |
commit | 2b10a9677817377618e33d2b07ab7caefe316633 (patch) | |
tree | 843ba74b9480f36da273cba79182e3c38b28881b /sdk-example-cluster.morph | |
parent | e424935744d9faf27327ee40987620412c41716f (diff) | |
download | definitions-2b10a9677817377618e33d2b07ab7caefe316633.tar.gz |
Re-organise definitions with scripts/organise-morphologies.pyGENIVI-I0.1baserock/release/GENIVI-I0.1
Diffstat (limited to 'sdk-example-cluster.morph')
-rw-r--r-- | sdk-example-cluster.morph | 46 |
1 files changed, 0 insertions, 46 deletions
diff --git a/sdk-example-cluster.morph b/sdk-example-cluster.morph deleted file mode 100644 index da0a6fff..00000000 --- a/sdk-example-cluster.morph +++ /dev/null @@ -1,46 +0,0 @@ -name: sdk -kind: cluster -description: | - An example of creating a cross-compile SDK for an embedded Baserock system. - - This cluster demonstrates how you can use the 'sdk' write extension to - produce a cross-compile SDK tarball for an Baserock applicance. In this - example the system is assumed to run on ARMv7, and the SDK is built to - run on any x86_32 GNU/Linux system. - - The SDK is a Baserock system itself, containing just 'build-essential' and a - 'cross-toolchain' stratum. The SDK system also includes the target - appliance's system, as a 'subsystem', so that the libraries and headers are - available when building. - - This cluster deploys the SDK system using the 'sdk' write extension, which - produces a tarball with a small shell header. When the shell header is - executed, and passed a directory name on the commandline, it extracts the SDK - to that path and patches the binaries so that they execute correctly from - that directory. - - Deploying the applicate system artifact to the target device should be - done with a separate cluster morphology, because you will often want to - do this without rebuilding the SDK. - - You must build each system with `morph build` before deploying. We recommend - doing this all from your Baserock development machine, using a Baserock - ARM distributed build network to produce the system artifact. Once both - system artifacts are cached locally, the `morph deploy` command will produce - a self-extracting shell script/tarball following the 'location' field. - - See the documentation of the sdk.write extension for more information. -systems: -- morph: armv7lhf-cross-toolchain-system-x86_32-generic - deploy: - sdk: - type: sdk - location: armv7lhf-cross-toolchain-system-x86_32-generic.sh - PREFIX: /usr - TARGET: armv7lhf-baserock-linux-gnueabi - subsystems: - - morph: devel-system-armv7lhf-highbank - deploy: - sysroot: - type: sysroot - location: usr/armv7lhf-baserock-linux-gnueabi/sys-root |