Compiler Targets

The following table gives an overview of available Haxe targets:

NameTierKindStatic typingSysSince Haxe version
JavaScript1sourceNoNobeta (2006)
HashLink1byte code + sourceYesYes3.4 (2016)
Eval1interpreterNoYes4.0 (2019)
JVM1byte codeYesYes4.0 (2019)
PHP71sourceNoYes3.4 (2016)
C++2sourceYesYes2.4 (2009)
Lua2sourceNoYes3.3 (2016)
C#3sourceYesYes2.10 (2012)
Python3sourceNoYes3.2 (2015)
Java3sourceYesYes2.10 (2012)
Flash3byte codeYesNoalpha (2005)
Neko3byte codeNoYesalpha (2005)
ActionScript 3-sourceYesNo1.12 (2007), removed in 4.0 (2019)
PHP5-sourceNoYes2.0 (2008), removed in 4.0 (2019)

Notes

  • Static typing: Yes - means the target platform natively supports static typing; Haxe code itself is statically typed no matter what target it is compiled to
  • Sys: Yes - means the target supports the System API
  • String encoding - see the Encoding section of the manual for target-specifics.

Tiers

  • Tier 1: actively maintained by the core compiler team with a strong focus from the Haxe Foundation
  • Tier 2: mostly maintained by individuals, but still managed by the Haxe Foundation
  • Tier 3: kept up-to-date, but not much active development