The CHORAC.EXE command line compiler lets you generate code from the command line without opening Embedded Wizard Studio. Because ChoraC is a Windows application, running it on Linux, macOS or inside a continuous integration (CI) pipeline normally requires either a Windows machine or a manually prepared WINE environment.

This chapter describes a Docker based approach that packages ChoraC together with WINE inside a container. With it you can generate code on any machine that runs Docker - including Linux servers, WSL and CI build agents - without installing Embedded Wizard Studio or configuring WINE yourself. The container reads your Embedded Wizard project, runs ChoraC against a selected profile and writes the generated code back to your host machine.

You can download the ready-to-use Docker package here:

EmbeddedWizard-ChoraC-Docker.zip

Unpack the archive on the machine where you want to generate code. It contains the Dockerfile, the launcher scripts and a small example project - you only need to add your license key, the ChoraC setup and, optionally, your own project as described below.

The container is built once from the ChoraC setup and then executed for every code generation run. The license key is never baked into the image - it is passed in at runtime and written into the WINE registry by the container, keeping the image free of any license material:

A WINE environment inside the image emulates Windows so the native Windows ChoraC executable can run. The WINE state is kept in a persistent Docker named volume so the license activation survives between runs (see Persisting the license activation below).

The package provides a launcher for each host system: start.bat for Windows and start.sh for Linux / WSL. Both take two arguments - the .ewp file (relative to the project directory) and the name of the profile to build:

The launcher can be started from any directory. It verifies the arguments, checks that Docker is running and that .env, the ChoraC setup and the requested project are present, writes the .msi file name into the Dockerfile, builds the image, and finally runs the container with your project mounted and the license injected at runtime.

After a successful run the generated code is copied out into a subfolder named after the selected profile, under the data/GeneratedCode/ directory. For the bundled example built with profile Win32 you get:

The per-profile output folder is replaced on every run, so it always reflects the latest build. ChoraC additionally leaves its native output inside the project itself, following the default output convention - data/EmWiGuiProject/Win32/ for the example.

The WINE environment is stored in a Docker named volume so that the license activation state survives across runs. Without this persistence every fresh container would look like a new machine to the Embedded Wizard license server, which can trigger a license in use by another user error.

If you ever need to start from a clean state - for example after changing the ChoraC version or to resolve a stuck activation - remove the named volume and run again. Docker re-populates it automatically on the next run.