Bensuperpc/dockcross
1
0
Fork 0
mirror of https://github.com/bensuperpc/dockcross.git synced 2024-09-20 02:30:39 +02:00
Code Issues Packages Projects Releases Wiki Activity
1fb2785377
dockcross/linux-x64/Dockerfile.in

38 lines
1.1 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
linux-x64: Update to thewtex/cross-compiler-base as base.
2016-03-28 18:45:57 +02:00
MAINTAINER Matt McCormick "matt.mccormick@kitware.com"
Use base image, add Makefile, compress RUN statements to save on disk space Signed-off-by: Steeve Morin <steeve.morin@gmail.com>
2014-10-17 13:42:56 +02:00
libssl-dev
2020-06-01 05:55:51 +02:00
RUN apt-get update && \
apt-get -y install \
libelf-dev \
libssl-dev \
&& apt-get clean --yes
linux-x64: install libelf-dev
2020-06-01 05:42:51 +02:00
Use base image, add Makefile, compress RUN statements to save on disk space Signed-off-by: Steeve Morin <steeve.morin@gmail.com>
2014-10-17 13:42:56 +02:00
ENV CROSS_TRIPLE x86_64-linux-gnu
linux-x64: Add CMAKE_TOOLCHAIN_FILE
2016-07-21 21:35:22 +02:00
ENV CROSS_ROOT /usr/bin
linux-x64: Update to thewtex/cross-compiler-base as base.
2016-03-28 18:45:57 +02:00
ENV AS=/usr/bin/${CROSS_TRIPLE}-as \
AR=/usr/bin/${CROSS_TRIPLE}-ar \
CC=/usr/bin/${CROSS_TRIPLE}-gcc \
CPP=/usr/bin/${CROSS_TRIPLE}-cpp \
CXX=/usr/bin/${CROSS_TRIPLE}-g++ \
Added fortran compiler * Added FC to all Dockerfiles * Changed cmake toolchains to use environment variables for compilers
2018-05-25 18:34:20 +02:00
LD=/usr/bin/${CROSS_TRIPLE}-ld \
FC=/usr/bin/${CROSS_TRIPLE}-gfortran
dockcross: make the default image specific to each compiler
2016-07-04 06:10:36 +02:00
linux-x64: Add CMAKE_TOOLCHAIN_FILE
2016-07-21 21:35:22 +02:00
COPY ${CROSS_TRIPLE}-noop.sh /usr/bin/${CROSS_TRIPLE}-noop
COPY Toolchain.cmake /usr/lib/${CROSS_TRIPLE}/
ENV CMAKE_TOOLCHAIN_FILE /usr/lib/${CROSS_TRIPLE}/Toolchain.cmake
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
Dockerfile: Remove unused default value associated IMAGE build argument
2020-05-07 01:17:16 +02:00
ARG 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
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