aotus /

Filename Size Date modified Message
54 B
Added tag v0_interface for changeset bfb6dafab79a
1.9 KB
Updated to Lua 5.3.
69.5 KB
Activated the output directory specified in the dozyfile
3.2 KB
Updated README, to note the right included Lua version.
5.2 KB
Updated links in the documentation.
4.9 KB
replaced intel compiler -vec-report -opt-report by -qopt-report=5
99.1 KB
Updated waf to avoid problems after failed compilations.
11.6 KB
Fixed the bug causing LUA_USE_POSIX not being set, even so it would be possible.

Advanced Options and Tables in Universal Scripting

The AOTUS library provides a Fortran wrapper around the C-API of the Lua scripting language, allowing a convenient usage of Lua scripts as configuration files in Fortran applications. Please have a look at the Wiki for more information on its usage. And for a detailed interface reference visit its Doxygen generated documentation

This library is released under a simplified MIT licence, please have a look into the COPYRIGHT file for details.

Aotus is part of the APES suite, for which there is a mailing list where questions can be asked.

How To Build

Waf is used as build system. Run:

./waf configure build

to build the aotus library. If you want to select a specific Fortran compiler, set the environment variable FC. And for a specific C compiler, set the environment variable CC. The Fortran compiler flags are set with the help of fc_flags, which provide a set of compiler flag combinations for various compilers. They are found in the file in the root directory of the project.

By running:

./waf --help

you get a list of available options to the waf script.

What is Built

For your convenience the Lua library is included in version 5.3.1 (released 2015-06-10). Its objects are completely gathered into the final libaotus library, so you only need to link against this single static library to gain the configuration features of Aotus in your Fortran application. Due to the compiler specific module information required by any application using libaotus, the suggested approach to incorporate libaotus is to include its building in the build process of the final application. This is straight forward if waf is used for the complete project. But also in other build environments it should not be too hard to make use of the generated build directory. Yet, if you would rather install the libaotus.a and the module files into a $PREFIX directory, you can make use of:

./waf install

The default build process will also create some unit test executables and execute them to ensure functionality of the various parts in the library.

The doxygen documentation can be built by running:

./waf doxy

This will build a html directory in the build directory with the resulting documentation. Note, that this requires an installed doxygen. It is also online available at Aotus documentation.


There is an example program built, called aotus_sample, which you will find in the build directory. It can be used with the provided config.lua in the sample directory, where also the source of this small program is found.

Some projects with similar goals or related information: