Bensuperpc/dockcross
1
0
Fork 0
mirror of https://github.com/bensuperpc/dockcross.git synced 2024-11-10 05:07:26 +01:00
Code Issues Packages Projects Releases Wiki Activity
dfd61226a7
dockcross/linux-arm64/Dockerfile.in

47 lines
1.4 KiB
Docker
Raw Normal View History

Dockerfile: Explicitly depend on "dockcross/base:latest" As recommended in by CircleCI, explicitly specify the "latest" tag. This will be important when we will start versioning our images. Copied from CircleCI documentation [1]: "Make sure you tag the image you use in the FROM command in your Dockerfile, even if it is the default “latest” tag. Otherwise, Docker will pull down all tags for the image you specify. This will create significant performance problems because the save/load strategy described above only caches the image layers (and thus tags) that you specify in the docker save command, so other tags will be re-pulled on every build if a tag is not specified in the FROM command." [1] https://circleci.com/docs/docker/#caching-docker-layers
2016-11-27 00:25:08 +01:00
FROM dockcross/base:latest
Fixed linux-arm64 compilation I hope.
2018-05-03 12:49:46 +02:00
Sync arm64 wtih other crosstool-ng targets
2018-05-20 18:36:53 +02:00
# This is for 64-bit ARM Linux machine
Fixed linux-arm64 compilation I hope.
2018-05-03 12:49:46 +02:00
#include "common.crosstool"
arm64: Initial addition
2016-07-15 22:20:46 +02:00
Sync arm64 wtih other crosstool-ng targets
2018-05-20 18:36:53 +02:00
# The cross-compiling emulator
RUN apt-get update \
&& apt-get install -y \
qemu-user \
qemu-user-static \
&& apt-get clean --yes
arm64: Initial addition
2016-07-15 22:20:46 +02:00
Sync arm64 wtih other crosstool-ng targets
2018-05-20 18:36:53 +02:00
# The CROSS_TRIPLE is a configured alias of the "aarch64-unknown-linux-gnueabi" target.
Trying to integrate my linux-arm64 solution to dockcross
2018-04-25 11:50:45 +02:00
ENV CROSS_TRIPLE aarch64-unknown-linux-gnueabi
Sync arm64 wtih other crosstool-ng targets
2018-05-20 18:36:53 +02:00
ENV CROSS_ROOT ${XCC_PREFIX}/${CROSS_TRIPLE}
ENV AS=${CROSS_ROOT}/bin/${CROSS_TRIPLE}-as \
AR=${CROSS_ROOT}/bin/${CROSS_TRIPLE}-ar \
CC=${CROSS_ROOT}/bin/${CROSS_TRIPLE}-gcc \
CPP=${CROSS_ROOT}/bin/${CROSS_TRIPLE}-cpp \
CXX=${CROSS_ROOT}/bin/${CROSS_TRIPLE}-g++ \
LD=${CROSS_ROOT}/bin/${CROSS_TRIPLE}-ld \
FC=${CROSS_ROOT}/bin/${CROSS_TRIPLE}-gfortran
ENV QEMU_LD_PREFIX "${CROSS_ROOT}/${CROSS_TRIPLE}/sysroot"
ENV QEMU_SET_ENV "LD_LIBRARY_PATH=${CROSS_ROOT}/lib:${QEMU_LD_PREFIX}"
arm64: Initial addition
2016-07-15 22:20:46 +02:00
Sync arm64 wtih other crosstool-ng targets
2018-05-20 18:36:53 +02:00
COPY Toolchain.cmake ${CROSS_ROOT}/
ENV CMAKE_TOOLCHAIN_FILE ${CROSS_ROOT}/Toolchain.cmake
ENV PKG_CONFIG_PATH /usr/lib/aarch64-linux-gnu/pkgconfig
dockerfile: Keep track of buildtime metadata This commit build each images with the following arguments: * IMAGE: Name of the image (e.g dockcross/base, dockcross/manylinux-x64, ...) * VCS_REF: dockcross/dockcross commit from which this image is built * VCS_URL: this repository obtained reading remote.origin.url * BUILD_DATE: Date and time when the build was initiated Then, within the Dockerfile, the metadata are associated with the image using the "LABEL" instruction. See https://docs.docker.com/engine/reference/builder/#/label The corresponding labels can be found here: http://label-schema.org/rc1/#build-time-labels See #28
2016-10-31 04:57:04 +01:00
# Build-time metadata as defined at http://label-schema.org
ARG BUILD_DATE
versioning: Set DEFAULT_DOCKCROSS_IMAGE based on the image tag This ensures that the dockcross script will continue to use the specific tagged version of the image that generates it.
2019-01-13 21:50:24 +01:00
ARG IMAGE=dockcross/linux-arm64
ARG VERSION=latest
dockerfile: Keep track of buildtime metadata This commit build each images with the following arguments: * IMAGE: Name of the image (e.g dockcross/base, dockcross/manylinux-x64, ...) * VCS_REF: dockcross/dockcross commit from which this image is built * VCS_URL: this repository obtained reading remote.origin.url * BUILD_DATE: Date and time when the build was initiated Then, within the Dockerfile, the metadata are associated with the image using the "LABEL" instruction. See https://docs.docker.com/engine/reference/builder/#/label The corresponding labels can be found here: http://label-schema.org/rc1/#build-time-labels See #28
2016-10-31 04:57:04 +01:00
ARG VCS_REF
ARG VCS_URL
LABEL org.label-schema.build-date=$BUILD_DATE \
org.label-schema.name=$IMAGE \
versioning: Set DEFAULT_DOCKCROSS_IMAGE based on the image tag This ensures that the dockcross script will continue to use the specific tagged version of the image that generates it.
2019-01-13 21:50:24 +01:00
org.label-schema.version=$VERSION \
dockerfile: Keep track of buildtime metadata This commit build each images with the following arguments: * IMAGE: Name of the image (e.g dockcross/base, dockcross/manylinux-x64, ...) * VCS_REF: dockcross/dockcross commit from which this image is built * VCS_URL: this repository obtained reading remote.origin.url * BUILD_DATE: Date and time when the build was initiated Then, within the Dockerfile, the metadata are associated with the image using the "LABEL" instruction. See https://docs.docker.com/engine/reference/builder/#/label The corresponding labels can be found here: http://label-schema.org/rc1/#build-time-labels See #28
2016-10-31 04:57:04 +01:00
org.label-schema.vcs-ref=$VCS_REF \
org.label-schema.vcs-url=$VCS_URL \
org.label-schema.schema-version="1.0"
versioning: Set DEFAULT_DOCKCROSS_IMAGE based on the image tag This ensures that the dockcross script will continue to use the specific tagged version of the image that generates it.
2019-01-13 21:50:24 +01:00
ENV DEFAULT_DOCKCROSS_IMAGE ${IMAGE}:${VERSION}
Reference in New Issue Copy Permalink