Organize definitions directory by morphologiesbaserock/franred/organize-morphologies-script

This is the result to run organize-morphologies.py .
The morphologies are clasified in clusters, systems, strata and chunks.
- "clusters" contains all the cluster morphologies.
- "systems" contains all the systems morphologies.
- "strata" contains all the stratum morphologies and the chunks
   morphologies which are inside of their stratum morphology folder,
   if this chunks will not be autodetected on build time.

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