Cool_Tools/bemanitools
1
0
Fork 0
mirror of https://github.com/djhackersdev/bemanitools.git synced 2025-01-31 12:13:42 +01:00
Code Releases Activity
bemanitools/Dockerfile

20 lines
402 B
Docker
Raw Normal View History

fix(dev): Improve deps docker build process, mount local folder as volume This removes the need to copy all the data into the docker container and outputs from the build process out of the container. In hindsight, this was a poor design decision as it created docker images that were very large with data, that you don't have to keep stored once the build finished, e.g. the build output. Therefore, mount the local folder, keep the checkouts also local which is good for debugging and also re-using them to build without the docker container (no second checkout required). Build output is also written directly to the build/ output folder Overall, the docker container is more lightweight and actually a "build environment" only not tainted with specific versions of the dependencies to build.
2023-03-21 23:31:23 +01:00
FROM --platform=amd64 fedora:31@sha256:cbe53d28f54c0f0b1d79a1817089235680b104c23619772473f449f20edd37dd
Add Dockerfile for building bemanitools with docker
2020-05-11 00:23:53 +02:00
LABEL description="Build environment for bemanitools"
RUN yum -y install \
git \
make \
zip \
clang \
mingw64-gcc.x86_64 \
fix(dev): Improve deps docker build process, mount local folder as volume This removes the need to copy all the data into the docker container and outputs from the build process out of the container. In hindsight, this was a poor design decision as it created docker images that were very large with data, that you don't have to keep stored once the build finished, e.g. the build output. Therefore, mount the local folder, keep the checkouts also local which is good for debugging and also re-using them to build without the docker container (no second checkout required). Build output is also written directly to the build/ output folder Overall, the docker container is more lightweight and actually a "build environment" only not tainted with specific versions of the dependencies to build.
2023-03-21 23:31:23 +01:00
mingw32-gcc.x86_64
Add Dockerfile for building bemanitools with docker
2020-05-11 00:23:53 +02:00
RUN mkdir /bemanitools
WORKDIR /bemanitools
fix(dev): Improve deps docker build process, mount local folder as volume This removes the need to copy all the data into the docker container and outputs from the build process out of the container. In hindsight, this was a poor design decision as it created docker images that were very large with data, that you don't have to keep stored once the build finished, e.g. the build output. Therefore, mount the local folder, keep the checkouts also local which is good for debugging and also re-using them to build without the docker container (no second checkout required). Build output is also written directly to the build/ output folder Overall, the docker container is more lightweight and actually a "build environment" only not tainted with specific versions of the dependencies to build.
2023-03-21 23:31:23 +01:00
ENTRYPOINT [ \
"/bin/bash", \
"-c" , \
"cd /bemanitools && \
make" ]
Copy Permalink