| Age | Commit message (Collapse) | Author |
|---|
|
Missed this in the gcc 11 version update, but if anyone is using this
then they'll need gcc 11 to build Lagom.
|
|
The goal of these more recent additions to the Dockerfile is to provide
a working copy of SerenityOS with the toolchain prebuilt. To me, these
additions feel misplaced:
- The toolchain is built assuming the i686 architecture, which may not
be what you want.
- You get a shallow clone of the project limiting you in your abilities
to navigate through the project's history or bisect.
- There's this awkward directory structure of `/serenity/serenity-git`
and `/serenity/out`.
The Dockerfile is immensely useful for building SerenityOS in a
containerized environment, separate from the host's environment. If we
want to automate builds, we can always use CI or extend this image to
do so. For now, let's remove the `git clone` and associated actions.
Fixes #9310.
|
|
It is no longer used to build the git port, it seems.
|
|
|
|
Also add `libsdl2-dev` as a required dependency and reorder the
list of packages passed to `apt-get`.
|
|
|
|
Docker is a nice way of doing build automation, or just
containerizing builds for increased safety and isolating unstable
packages. The old Dockerfile in the toolchain did not satisfy these
needs. The new Dockerfile is known to run successfully on Docker
version 20.10.7. It clones the SerenityOS repo and builds the
toolchain. In this way, it is intended to be a starting point for other
Docker images that can e.g. run builds. For example, one can simply run
this docker image as-is, exec a shell in it and run a build there.
|
|
We need `msgfmt` inside of the `gettext` package in order to build the
git port.
|
|
Following up on 2d38d56e, we were missing this in our Dockerfile.
|
|
|
|
Both utilies are used in the .port_include.sh file.
|
|
|
|
|
|
|
