Dockerfile linksFor more information about this image and its history, please see the relevant git repository subdirectory (haxe) in the cromo/dockerfiles GitHub repo.
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 most straightforward way to use this image is to use a haxe comtainer 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 cromo/haxe:3.2.0-neko
COPY . /source
WORKDIR /source
RUN haxe -main Main -neko Main.n
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 may be occasions where it is not appropriate to run your app inside a container. To compile, but not run your app inside the Docker instance, you can write something like:
docker run --rm -v "$(pwd)":/source -w /source cromo/haxe:3.2.0-neko haxe -main Main -neko Main.n
This will add the current directory as a volume, set the working directory to the volume, and run the command haxe -main Main -neko Main.n. This tells haxe to compile the code in Main.hx and output a Neko bytecode file to Main.n. Alternatively, if you have a build.hxml, you can instead run haxe with the hxml file inside your container:
docker run --rm -v "$(pwd)":/source -w /source cromo/haxe:3.2.0-neko haxe build.hxml
View license information for the software contained in this image. The Dockerfiles themselves are under the MIT license.
This image has been tested on Docker version 1.7.0.
Support for older versions (down to 1.0) is provided on a best-effort basis.
Documentation for this image is stored in the haxe/3.2.0/neko directory of the cromo/dockerfiles GitHub repo.
If you have any problems with or questions about this image, please contact me through a GitHub issue.
You are invited to contribute new features, fixes, or updates, large or small; I will do my best to process them as fast as I can.
Before you start to code, I recommend discussing your plans through a GitHub issue, especiall for more ambitious contributions. this gives other contributors a chance to point you in the right direction, give you feedback on your design, and help you find out if someone else is working on the same thing.
Content type
Image
Digest
sha256:63edc48d7…
Size
97.6 MB
Last updated
over 10 years ago
docker pull cromo/haxe