2 files changed, 95 insertions, 36 deletions
@@ -8,52 +8,46 @@ These are some example definitions for use with Baserock tooling. You can fork
this repo and develop your own systems directly within it, or use it as a
reference point when developing your own set of definitions.
-These definitions follow the Baserock definitions format, which is defined in
-spec.git repository (http://git.baserock.org/cgit/baserock/baserock/spec.git).
-The spec is readable online at <http://docs.baserock.org/spec>.
-The systems listed in the systems/ directory are example systems
+The systems listed in the elements/systems/ directory are example systems
that build and run at some point. The only ones we can be sure
that still build in current master of definitions are the ones that
we keep building in our ci system; they are listed in
-Keeping up to date
+It is possible to use BuildStream to build Baserock definitions. The
+BuildStream build tool uses a different definitions format, so a conversion
+needs to be done first.
+Run the `convert` script from the root of the repository and you will be
+rewarded with an autogenerated set of .bst files in the elements/ subdirectory
+which should be buildable using BuildStream.
-The Baserock definitions format is evolving. A set of automated migrations is
-provided in the migrations/ directory of spec.git, for use when the format has
-changed and you want to bring your definitions up to date.
+To run `convert`, you will need defs2bst and ybd. The following commands, run
+from the root of the repository, should be enough to do a conversion:
-Before running the migrations, you can use the 'migrations/indent' tool to
-format the definitions in the specific style that the migrations expect.
-The migrations use the 'ruamel.yaml' Python library for editing the .morph
-files. This library preserves comments, ordering and some of the formatting
-when it rewrites a .morph file. However, it does impose a certain line width
-and indent style.
+ git clone https://gitlab.com/BuildStream/defs2bst/ ../defs2bst
+ git clone https://gitlab.com/baserock/ybd/ ../ybd
-It makes a lot of sense to run the migrations with a *clean Git working tree*,
-so you can clearly see what changes they made, and can then choose to either
-commit them, tweak them, or revert them with `git reset --hard` and write an
+You can then build e.g. a devel-system using BuildStream:
-The suggested workflow is to run this from within your definitions.git clone:
+ bst build systems/devel-system-content.bst
- git clone git://git.baserock.org/baserock/baserock/spec ../spec.git
+Some things are not supported by the BuildStream conversion tool, and will need
+to be manually dealt with.
- git status # ensure a clean Git tree
- git diff # check for any spurious changes
- git commit -a -m "Fix formatting"
- git diff # check the results
- git commit -a -m "Migrate to version xx of Baserock definitions format"
+ * the build-essential stratum isn't automatically converted, the
+ elements/gnu-toolchain.bst element is its equivalent and needs to be
+ manually kept in sync with any changes
-If you are working in a fork of the Baserock definitions.git repo, you can
-also keep to date with using changes in 'master' using `git merge`. In general,
-we recommend first running the migrations, committing any changes they make,
-*then* merging in changes using `git merge`. This should minimise the number of
-merge conflicts, although merge conflicts are still possible.
+ * .configure and .write extensions need to be rewritten as BuildStream
-See migrations/GUIDELINES for information on how to write new migrations.
+ * non-x86_64 systems aren't automatically converted; BuildStream supports
+ "arch conditionals" which should make it easier for a single tree of .bst
+ files to support many platforms, but it's not easy to automatically achieve
+ this in places like linux.bst where Baserock currently has many different
diff --git a/convert b/convert
new file mode 100755
@@ -0,0 +1,65 @@
+# Baserock definitions -> BuildStream conversion script.
+# This script aims to be the "canonical" conversion of the Baserock definitions
+# repository for use with the BuildStream build tool.
+# This must point to a clone of https://gitlab.com/BuildStream/defs2bst/
+# This must point to a clone of https://gitlab.com/baserock/ybd/
+# Only the following systems will be converted.
+mkdir -p elements/
+mkdir -p elements/systems/
+for system_morph in $systems; do
+ # Run the defs2bst script for $system_morph. This will produce a .bst
+ # file for every chunk involved in the build, and will produce a file named
+ # something like XX-system-x86_64-content.bst from the system .morph file.
+ $CONVERTER --ybd $YBD \
+ --definitions ./ \
+ --output ./elements \
+ --rebase strata/build-essential.morph gnu-toolchain.bst \
+ $system_morph x86_64
+ # Figure out the .bst file defs2bst will have produced for $system_morph.
+ system_bst_initial=$(echo $system_morph | sed -e 's@systems/@@' -e 's@\.morph$@-content.bst@')
+ # Now we remove x86_64 from the name; BuildStream allows architecture
+ # conditionals so we don't need to duplicate everything per platform.
+ # We take the opportunity to remove -generic as well if present.
+ system_bst_final=$(basename $system_bst_initial | sed -e 's@-x86_64@@' -e 's@-generic@@')
+ # All systems go in an elements/systems/ subdirectory, rather than being
+ # spread around different dirs like they are currently.
+ mv elements/$system_bst_initial elements/systems/$system_bst_final
+ echo "convert: Created elements/systems/$system_bst_final from elements/$system_bst_initial"
+# Manual fix for libffi build instructions. The output of $(gcc -dumpmachine)
+# is not the same as the output of $(sh ./config.guess) when building with
+# the BuildStream gnu-toolchain definitions.
+# We cannot fix this in definitions.git master, see: https://gitlab.com/baserock/definitions/merge_requests/49
+sed -i elements/core/libffi.bst -e 's@\$(gcc -dumpmachine)@$(sh ./config.guess)@'