Build Instructions


For UNIX-like environments, Antinat uses the autoconf system to provide "./configure && make && make install" style compilation.

However, you will need to have installed expat (including expat-devel) in order to compile. If the configure script is unable to locate your installation of expat, you may need to specify it on the command line:

./configure CPPFLAGS="-I/path/to/expat/include" LDFLAGS="-L/path/to/expat/lib"

The only compiler being supported on UNIX is gcc, version 2.95.3 or newer. If you use a different compiler and encounter compilation problems, by all means send in patches or bug reports, but there is no guarantee that compilation will always work with your compiler.

If you wish to include verbose output in your build, use the --with-feedback switch to configure; if you want compilation warnings turned on (gcc only!) use --with-warnings.

IPv6 is not compiled by default. If you want to include it (and know what you're doing) use --with-ipv6. Note that IPv6 support is incomplete (no filtration) and not well tested. You have been warned.


On Windows, you can use the MinGW compiler, or a Microsoft compiler. If you use a MinGW compiler, compilation instructions are the same as mentioned in the UNIX/Linux section, above.

Using a Microsoft compiler is slightly different. There is no requirement for an installed copy of expat in this case; Antinat uses the AutoWin build system, which allows for compilation using a large range of versions of the Microsoft compiler.

    • If you use Visual Studio .NET (or Visual C++ .NET) open a command prompt for your compiler from the Visual Studio/Visual C++ group of the Start Menu.
    • If you use Visual C++ Toolkit, open a command prompt from the Visual C++ Toolkit group of the Start Menu and be sure to set the environment variables for the Platform SDK by running SetEnv.bat in your Platform SDK directory. You may also need to make sure the path containing NMAKE is in your PATH (put it at the end.)
    • If you use an older version of Visual C++, open a command prompt from the Accessories group of the Start Menu (or the master Start Menu, depending on your version of Windows) and run vcvars32.bat from your compiler's BIN subdirectory.
  1. Change to the directory where you have unpacked the Antinat source.
  2. Run:
    NMAKE /f Makefile.w32

    Depending on your version, you may also need to specify some additional flags to NMAKE to help it with your development environment. For starters, you may need to specify the version of the compiler you intend to use. Note that this is a compiler version, not Visual C++ version.

    For this version of Visual C++Use this compiler version
    Visual C++ 2MSC_VER=9
    Visual C++ 4MSC_VER=10
    Visual C++ 5MSC_VER=11
    Visual C++ 6MSC_VER=12
    Visual C++ .NET (any subversion)MSC_VER=13
    Whidbey/Visual C++ 2005MSC_VER=14

    These values are appended to the command line, eg.

    NMAKE /f Makefile.w32 MSC_VER=10
  3. You can customise your build using any supported AutoWin flag, as well as some Antinat-specific ones. The following flags may also be useful: (Visual C++ Toolkit).
    This flag...does thisDefaultLegitimate values
    MSC_EDChanges between the edition of the compiler you're using.MSC_ED=pro (for MSC_VER up to 12), MSC_ED=free (for versions 13 or over.)MSC_ED=std (standard edition), MSC_ED=pro (professional edition), MSC_ED=free
    DEBUGEnables or disables debugging information in the buildDEBUG=0DEBUG=0, DEBUG=1
    CLIB_SHAREDChanges between using a static C library or the DLL (for your compiler)CLIB_SHARED=1 (for MSC_VER up to 12), CLIB_SHARED=0 (for versions 13 or over.)CLIB_SHARED=0, CLIB_SHARED=1
    PC_HEADERSEnables or disables precompiled headers.PC_HEADERS=0PC_HEADERS=0, PC_HEADERS=1
    WITH_FEEDBACKEnables or disables verbose debugging output.WITH_FEEDBACK=0WITH_FEEDBACK=0, WITH_FEEDBACK=1
  4. Finally, if you wish to build a self-installing version, you will need NSIS version 2 or later in your PATH; then type:
    NMAKE /f Makefile.w32 distribution