Using Thrift with Haxe

Haxe setup

Thrift requires Haxe 4.2.1. Installers for Windows and OSX platforms are available at

Depending on the desired targets, you may have to install the appropriate HaxeLibs after installing Haxe itself. For example, if you plan to target C++, enter the following command after installing Haxe:

haxelib install hxcpp

For other targets, please consult the Haxe documentation whether or not any additional target libraries need to be installed and how to achieve this.

Haxe on Linux

For Linux platforms it is recommended to use the distro-specific package manager, where possible. More detailed information can be found at the Haxe Linux download section:

If you run into the error message

Uncaught exception - load.c(237) : Failed to load library : /usr/lib/neko/regexp.ndll  
( cannot open shared object file: No such file or directory)

this can be solved depending on your OSes bitness by either

sudo ln -sf /usr/lib/ /usr/lib/
sudo ldconfig


sudo ln -sf /usr/lib64/ /usr/lib64/
sudo ldconfig

Thrift Haxe bindings

Thrift Haxe bindings can be set up via the haxelib tool as usual. Alternatively, the “github” method can be used.

As usual, the installed library can be updated using haxelib upgrade or haxelib update thrift.

In order to work with Thrift, you will need to install the Thrift compiler or build from source, depending on your operating system. Appropriate downloads and more information can be found at

To get started, visit the /tutorial/haxe and /test/haxe dirs for examples. If you are using the HaxeDevelop IDE, you’ll find appropriate project files in these folders.

Breaking changes

This version requires Haxe 4 and cannot be used with earlier versions.

It is recommended to clear out all gen-haxe contents once before switching to the new version. Otherwise you may run into troubles with leftovers from previous versions.

The compiler option callbacks is now obsolete. The compiler will always generate a dual interface (i.e. with optional callback style) for use on the client side, plus a new _service interface to be used for server implementations. Consequentially, your client and server implementations will need some manual intervention.

PHP HTTP Server notes