summaryrefslogtreecommitdiffstats
path: root/base/compiler_specific.h
diff options
context:
space:
mode:
authormaniscalco <maniscalco@chromium.org>2015-10-05 12:30:22 -0700
committerCommit bot <commit-bot@chromium.org>2015-10-05 19:32:05 +0000
commit91be48ce93f2cef2a78157a0af2fbbfb3d6ea687 (patch)
tree9a3af07ad06653dc7a8fae434f408a37cd4aa099 /base/compiler_specific.h
parent49d1d6354eeec0eed524cde21ab49991aa6d534d (diff)
downloadchromium_src-91be48ce93f2cef2a78157a0af2fbbfb3d6ea687.zip
chromium_src-91be48ce93f2cef2a78157a0af2fbbfb3d6ea687.tar.gz
chromium_src-91be48ce93f2cef2a78157a0af2fbbfb3d6ea687.tar.bz2
Add script to bundle blimp engine into a Docker image
The blimp engine will run as a Docker container, and this CL adds the tools to be able to do that. There are three main parts: - The Dockerfile: Defines what should be part of the Docker image. - bundle-engine.py: Bundles the blimp engine and all its runtime dependencies into a tarball. This tarball also contains the Dockerfile itself. - Building a Docker image. This can easily be done by using the tarball that bundle-engine.py generates. This part is only documented and is not itself packaged into a script. To create the tarball, you execute: $ ./blimp/tools/bundle-engine.py \ --build-dir ./out-linux/Debug \ --dockerfile ./blimp/engine/Dockerfile \ --target blimp/engine:blimp_engine \ --output ./out-linux/Debug/blimp_engine_deps.tar You can then build the Docker image with: $ docker build -t blimp_engine - < ./out-linux/Debug/blimp_engine_deps.tar You can then run your Docker container with: $ docker run blimp_engine --with-my-flags BUG=538353 Review URL: https://codereview.chromium.org/1380123004 Cr-Commit-Position: refs/heads/master@{#352386}
Diffstat (limited to 'base/compiler_specific.h')
0 files changed, 0 insertions, 0 deletions