Hello Hashlink
Now that you have installed both Heaps and Visual Studio Code, let’s create a new Heaps application.
- needs a different compilation target,
hl
, and other libraries to manage rendering - There’s no need for an
index.html
file - The launch.json file is different to handle hashlink
Concepts
- Heaps uses a
compile.hxml
file to tell it what to compile, how and where to compile it, and which libraries to include. - The entry point of a Haxe program is a class containing a static function called
main
.
- Create a new directory named
helloHeaps
- Create a new file called
compile.hxml
- Add the following lines to your newly created file
-cp src
Tells haxe where to search for your code files-lib heaps
Tells haxe to import the heaps library-lib hlsdl
Tells haxe to import the hlsdl rendering library- Tells haxe that Main.hx is your entry point
The -lib hlsdl
tells Heaps to compile with SDL/OpenGL support. If you are on Windows you can use -lib hldx
instead.
Open with VSCode
At this point, you can open the helloHeaps
folder with VSCode by launching VSCode and navigating the main menu File > Open Folder
Create a new Main.hx
in a src
folder in your project directory and put the following content
This example creates a Heaps Text component, adds it to the 2D scene s2d
and set its text.
Compile and run Output
To be able to compile and debug your application directly from vscode, you need to create a launch task.
Add the following code to the file:
Now, by hitting F5
, the project will compile and run.
To compile without running, hit and select haxe : active configuration
If everything works well, you should now have a hello.hl
file created in your project folder.
You can customize the default window size by adding the following to your compile.hxml
:
Compile and Run natively
The hello.hl
file contains bytecode that can be run with the HashLink virtual machine using hl hello.hl
. It does give quite good performances and have been proven by successful commercial games such as Northgard or Dead Cells.
However, it is also possible to compile the HashLink code using a native compiler. This allows to compile for consoles and mobile.
This is done by changing compile.hxml
to use -hl out/main.c
instead of -hl hello.hl
.
This will create a directory out
containing a lot of generated C code that needs to be built using a native compiler and linked to the same HashLink runtime that the HashLink virtual machine is using.
Compiling on mobile and console thus requires some knowledge with each platform compilers and build systems: for iOS, look at for Android, look at this thread * for Consoles (Nintendo Switch, Sony PS4, Microsoft XBoxOne), please contact us at nicolas @
haxe.org if you are a registered developer for one or several of these