| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| |
|
|
|
| |
We gained this file when we imported Tristan's gnu-toolchain project, we just
need to update it for building the Baserock reference systems.
|
| |\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
sam/buildstream-autoconvert
This branch contains a manual conversion of the Baserock bootstrap
process to BuildStream. The original branch can be found here:
https://gitlab.com/BuildStream/buildstream-tests/tree/gnu-toolchain
It's not possible to automatically convert the existing Baserock
bootstrap due to differences in how BuildStream works.
|
| | |\
| | |
| | |
| | |
| | | |
Update toolchain and allow cross-building
See merge request !9
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
We cannot do long GCC builds using the default GitLab CI runners, we'll
need to provide our own.
|
| | | |
| | |
| | |
| | |
| | | |
This is primarly to avoid hitting the 1 hour timeout that seems to be
hardcoded into the CI system. It's also a bit clearer this way.
|
| | | |
| | |
| | |
| | |
| | |
| | | |
With an empty cache, every worker must spend 10 minutes pulling all of
the sources that are required. There's no point having 5 workers pulling
the same things in parallel, so the first stage now contains only 1 job.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
| | | | |
|
| | | | |
|
| | |/ |
|
| | |
| |
| |
| |
| |
| |
| | |
o Use the org.freedesktop.BasePlaform and org.freedesktop.BaseSdk
for building instead of the whole GNOME runtime.
o Some minor renames
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
This required making sure that fhs-dirs is depended on by anything
which would stage on top of it, as the directory symlinks must come
first.
In this commit the dependencies are listed explicitly, probably
there is a way to do this without being as wordy.
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
This is because otherwise we end up using the sysrooted
/tools/sbin/ldconfig, causing the gcc build to fail as it
does not find libz.so which is otherwise properly located
if /sbin/ldconfig is used.
|
| | |
| |
| |
| |
| | |
Because the GNOME sdk is no longer there, and ldconfig from stage2
is in /tools/sbin.
|
| | |\
| | |
| | |
| | |
| | | |
Don't use ssh urls in the aliases when not needed
See merge request !1
|
| | |/ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This huge commit is a manual conversion, notes on what was
needed:
o project.conf defines the arch specific stuff which was
previously hardcoded into YBD, so the stage1 target and target
etc are all defined by the build-essential project.conf
o Direct and easy changes for git source representation
o Added stage1.bst & stage2.bst "stacks", everything built in
stage2 build-depends on stage1.bst, and the final build-essential
products build-depend on stage2.bst (note build-depend means
to depend _only_ for building, not propagated forward).
o Instead of using host tools we build on the GNOME flatpak
sdk/platform bundles
o Some build-essential morph files use $(dirname $(pwd)) for a sysroot,
which is weird, it means the morph files rely on building at one directory
below the slash sysroot - in buildstream we build in /buildstream/build
which is two - had to replace these with $(dirname $(dirname $(pwd))) instead
o Remove the devices sections from the fhs-dirs elements, not allowed
to create static device nodes in buildstream.
|
| | |
| |
| |
| | |
This is on by default for any autotools or supporting build system.
|
| | |
| |
| |
| |
| | |
Pull in a different org.gnome.Sdk branch depending on the
build architecture.
|
| | |
| |
| |
| |
| | |
Pull in a different org.gnome.Platform branch depending on the
build architecture.
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
introspection.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
And it also builds glade for the hell of it.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
If USE_BUILD_LIBS is enabled, the build fails under BuildStream. This
seems to be because files get installed to $DESTDIR/buildstream/build
which are then included in the artifacts. (This breaks subsequent builds
as the /buildstream/build/ dir is expected to be empty until source is
checked out.)
https://gitlab.com/BuildStream/buildstream/issues/74 is the relevant
BuildStream issue.
|
| |
|
|
|
|
|
| |
These presumably aren't needed since they are probably not even
accessible during the normal operation of a system (as there can be a
tmpfs mounted over the top). YBD doesn't raise any error about this
but BuildStream does.
|
| |
|
|
|
| |
It's obsolete and full of security holes. And it fails to compile under
BuildStream for some reason but let's see if we can just get rid of it.
|
| | |
|
