From 30dac6d0f4a5ece922a3ba4ea597de97370c1bb6 Mon Sep 17 00:00:00 2001 From: James Le Cuirot Date: Fri, 12 Jul 2024 15:49:30 +0100 Subject: [PATCH 1/2] Make SDK bootstrap process page appear in the menu Signed-off-by: James Le Cuirot --- .../latest/reference/developer-guides/sdk-bootstrapping.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/content/docs/latest/reference/developer-guides/sdk-bootstrapping.md b/content/docs/latest/reference/developer-guides/sdk-bootstrapping.md index 1932a68b..43aafa2d 100644 --- a/content/docs/latest/reference/developer-guides/sdk-bootstrapping.md +++ b/content/docs/latest/reference/developer-guides/sdk-bootstrapping.md @@ -1,4 +1,9 @@ -## SDK bootstrap process +--- +title: SDK bootstrap process +weight: 10 +--- + +## Introduction This document aims to provide a high-level overview of the SDK build ("bootstrap") process. From 3298fa7b08c6d6e27eff5896f0c28933c0bc3fff Mon Sep 17 00:00:00 2001 From: James Le Cuirot Date: Fri, 12 Jul 2024 15:49:45 +0100 Subject: [PATCH 2/2] Revise SDK bootstrap process according to new seed update procedure --- .../latest/reference/developer-guides/sdk-bootstrapping.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/content/docs/latest/reference/developer-guides/sdk-bootstrapping.md b/content/docs/latest/reference/developer-guides/sdk-bootstrapping.md index 43aafa2d..cb01b0f0 100644 --- a/content/docs/latest/reference/developer-guides/sdk-bootstrapping.md +++ b/content/docs/latest/reference/developer-guides/sdk-bootstrapping.md @@ -27,9 +27,7 @@ The output of the 4th stage, i.e. the archived contents of `/tmp/stage4root`, re Stage 1 is somewhat of a preparation phase and does not actually involve any components to be found in the final SDK. This stage takes the seed tarball - which must be a previously released Flatcar SDK - and builds a minimal toolchain from the seed (with `USE=-*`). -**NOTE** -* this toolchain, i.e. the output of Stage 1, will be built from the "old" package versions from the seed SDK. Contents of `../third_party/coreos-overlay` and `../third_party/portage-stable` are ignored in this step. Instead, the ebuild repos included in the seed SDK are used (**FIXME: Not entirely true yet**) -* Stage 1 does _not_ feature strong library link isolation. All packages installed to `/tmp/stage1root` will be linked against libraries in `/` instead of libraries in `/tmp/stage1root`. Therefore, Stage 1 only uses the "old" seed SDK's package versions when building the seed for Stage 2. +**NOTE**: Stage 1 does _not_ feature strong library link isolation. All packages installed to `/tmp/stage1root` will be linked against libraries in `/` instead of libraries in `/tmp/stage1root`. We avoid issues with missing libraries later in the build by initially updating the seed, specifically relevant packages that have changed [sub-slot](https://wiki.gentoo.org/wiki/Sub-slots_and_Slot-Operators). #### Stage 2 - Build the toolchain that builds the SDK