3.1.3
,3.1
(3.1/Dockerfile)3.1.3-onbuild
,3.1-onbuild
(3.1/onbuild/Dockerfile)3.2.1
,3.2
(3.2/Dockerfile)3.2.1-onbuild
,3.2-onbuild
(3.2/onbuild/Dockerfile)3.3.0-rc.1
,3.3.0
,3.3
(3.3/Dockerfile)3.3.0-rc.1-onbuild
,3.3.0-onbuild
,3.3-onbuild
(3.3/onbuild/Dockerfile)3.4.2
,3.4
,latest
(3.4/Dockerfile)3.4.2-onbuild
,3.4-onbuild
(3.4/onbuild/Dockerfile)
-
Where to get help:
the Docker Community Forums, the Docker Community Slack, or Stack Overflow -
Where to file issues:
https://github.com/HaxeFoundation/docker-library-haxe/issues -
Maintained by:
the Haxe Foundation -
Published image artifact details:
repo-info repo'srepos/haxe/
directory (history)
(image metadata, transfer size, etc) -
Image updates:
official-images PRs with labellibrary/haxe
official-images repo'slibrary/haxe
file (history) -
Source of this description:
docs repo'shaxe/
directory (history) -
Supported Docker versions:
the latest release (down to 1.6 on a best-effort basis)
Haxe is an open source toolkit based on a modern, high level, strictly typed programming language, a cross-compiler, a complete cross-platform standard library and ways to access each platform's native capabilities.
The Haxe compiler can output a number of source and binary files. As of Haxe 3.4.0-rc.1, the Haxe compiler can target JavaScript, Java, C#, C++, Python, PHP, Flash SWF, ActionScript 3, Lua, and Neko.
This image ships a minimal Haxe toolkit:
- the
haxe
compiler with its standard library - the
haxelib
library manager - the
neko
virtual machine
The most straightforward way to use this image is to use a Haxe container as both the build and runtime environment. In your Dockerfile
, writing something along the lines of the following will compile and run your project:
FROM haxe:3.4
RUN mkdir -p /usr/src/app
WORKDIR /usr/src/app
# install dependencies
COPY *.hxml /usr/src/app/
RUN yes | haxelib install all
# compile the project
COPY . /usr/src/app
RUN haxe build.hxml
# run the output when the container starts
CMD ["neko", "Main.n"]
Then, build and run the Docker image:
$ docker build -t my-haxe-app .
$ docker run -it --rm --name my-running-app my-haxe-app
There are onbuild
variants that include multiple ONBUILD
triggers to perform all of the steps in the above Dockerfile, except there is no CMD
instruction for running the compilation output.
Rewriting the above Dockerfile with haxe:3.4-onbuild
, we will get:
FROM haxe:3.4-onbuild
# run the output when the container starts
CMD ["neko", "Main.n"]
The onbuild
variants assume the main compilation hxml file is named build.hxml
. To use another hxml file, set the BUILD_HXML
build argument during build:
$ docker build -t my-haxe-app --build-arg BUILD_HXML=compile.hxml .
View license information for the software contained in this image.