This wiki is out of date, use the continuation of this wiki instead

Tutorial:Setting up Fenix on Windows

From FenixWiki

Jump to: navigation, search


[edit] Download

  • To download a few old version of Fenix, go to the Fenix site.
  • To download previews of new beta versions, go to the Spanish forum.
  • To download all Fenix versions, official DLL's and more up to date stuff, go to the SourceForge site of Fenix.

The current downloads you'll need is the latest Fenix version.

[edit] Package

The Fenix consists of two main items: fxc.exe and fxi.exe. FXC.exe (FeniX Compiler) compiles code you program to bytecode, which FXI.exe (FeniX Interpreter) reads when you want to run your program. See their pages for more detailed info about them, for now we will focus on basic operations.

[edit] FXC.exe

FXC.exe [<options>] <filename>


-d - Debugging mode.
-i <dir> - Adds the directory to the PATH.
-a - Automaticaly adds all files to the DCB.
-f <file> - Adds a single file to the DCB.
-l <lang> - Specify locale settings.
-s <stub> - Generate a stubbed executable from the given stub.
-g - Stores debugging information at the DCB.
-c - File uses the MS-DOS character set.


The code to be compiled to bytecode.

FXC.exe compiles <file>.<file_extension> to the bytecode file <file>.dcb. Any information regarding the compilation and possible errors will be reported in stdout.txt.

[edit] FXC.bat

This calls FXC.exe and outputs stdout.txt to the screen.

[edit] FXI.exe

FXI.exe [<options>] <filename>


-d - Activate DEBUG mode.
-f - 16bpp Filter ON (only 16bpp color mode).


The bytecode generated by FXC.exe, usually a .dcb file.

FXI.exe outputs text to both stdout.txt and stderr.txt. The first will contain console messages, like the ones produced with the say() command, while the latter will only contain text when a fatal error occurs. In such a case the file will contain an error message.

[edit] DLLs

Some DLLs in the package don't have to be included everytime, there are a few which can be left out when compiling or running the code, if their functionality is not used. (Specifics needed)

[edit] NEWS

The file NEWS contains the changelog of the Fenix version it was included with.

[edit] Setting up

Extract the latest archive to a folder (At the moment 0.92a and overwrite it with 0.93 preview 9).

There are many ways to use Fenix. The most simplistic way is to use the command window to call the executables/batch files and type in the code with any text editor, which is a rather cumbrous method.

[edit] Commandline

Using the commandline is not recommended, but still possible. Copy the needed files (fxc.exe, fxi.exe and their DLLs) to a new directory, "mygamedir" for example. Make a new file, "mygame.prg" for example and open it with a text editor, say Notepad. Here you can code what you want; save the code when you're done. Now go to this directory with the commandline and compile "mygame.prg":

fxc mygame.prg

Now "stdout.txt" will contain information about the compiling, including possible errors. When there are no errors, "mygame.dcb" will be created, which is a bytecode version of your code. To run this code, type:

fxi mygame.dcb

That's it.

[edit] ConTEXT

One can also make use of ConTEXT and set it up like described here. There's a highlighter file which is rather up-to-date and customizable.

[edit] FlameBird

It is also possible to download Flamebird, which is an IDE made for Fenix, although it seems a bit unstable. Additional steps have to be taken in order to get Flamebird to work on Windows Vista, involving copying the file "MSVBVM50.DLL" from the "WINDOWS\SYSTEM32\" directory of a windows XP machine into the same directory as the flamebird EXE file ("FB2.exe" or "FBMX.exe") (More information and explanation needed)

[edit] External links

Personal tools