There is no standard module for the "C" language. This language is supported without the need to import a module. The following modules are distributed with &Aap;: d Support for the "D" programming language. With this module imported, :program, :dll and :lib commands can be used as easily as with C or C++. libtool Adds support for GNU libtool, so that you can use it to build shared libraries in a portable manner. Automatically imported if you use a :ltlib command. This is a prerequisite for the KDE module. Qt™ Adds support for the Qt™ library from Trolltech™. This automatically searches for the Qt library in several likely places; see also the $QTDIR variable. Support is added for .ui (Qt Designer) files as sources, and for .moc (Qt Meta-Object system) as dependencies generated from header files. Support for the "D" programming language. With this module imported, :program, :dll and :lib commands can be used as easily as with C or C++. To customize compilation and linking, the variables below can be filled. See also for supported D tools. name type   description $D_COMPILE_ACTION Aap When not empty, specifies the action name to be executed for compiling a D file into an object, dllobject or libobject file. See . $D_BUILD_ACTION Aap When not empty, specifies the action name to be executed for building a program or library from object files compiled by a D compiler. A "buildaction" attribute on one of the object files is used before $D_BUILD_ACTION. See . $D_BUILDDLL_ACTION Aap When not empty, specifies the action name to be executed for building a dynamic link library from object files compiled by a D compiler. A "buildaction" attribute on one of the object files is used before $D_BUILDDLL_ACTION. See . $D_BUILDLIB_ACTION Aap When not empty, specifies the action name to be executed for building a static library from object files compiled by a D compiler. A "buildaction" attribute on one of the object files is used before $D_BUILDLIB_ACTION. See . $D_BUILDONESTEP_ACTION Aap When not empty, specifies the action name to be executed for building a program directly from D source. See . $D_BUILDDLLONESTEP_ACTION Aap When not empty, specifies the action name to be executed for building a dynamic link library directly from D source. See . $D_BUILDLIBONESTEP_ACTION Aap When not empty, specifies the action name to be executed for building a static library directly from D source. See . $DFLAGS user Compiler arguments passed to the D compiler. $DLINKFLAGS user Arguments passed to the linker; in most cases libraries to link with. $DIMPORT user Import directories used for the D compiler. Always use the "-Ipath" form and don't use it for other switches. A-A-P will convert it to what the compiler actually uses. This variable is also used when checking for dependencies. $DVERSION user Version arguments passed to the D compiler. Always use the "-version=..." form, the tool will convert it to what the compiler actually uses. $DDEBUG user Debug arguments passed to the D compiler. Always use the "-debug"/"-debug=..." form, the tool will convert it to what the compiler actually uses. To enable symbolic debug information, set the the $DEBUG to "yes". For other language independent debugging switches, like enabling profiling hooks, use $DFLAGS. $DIMPLIB user If this variable is set to 'yes', an import library will be created when building a dll on the Windows platform. Adds support for GNU libtool, so that you can use it to build shared libraries in a portable manner. Automatically imported if you use a :ltlib command. Adds support for the Qt™ library, distributed by Trolltech. Qt is a toolkit for graphical user interfaces, and forms the basis for the KDE Desktop environment. Qt adds a form of introspection to C++ as well as a way to loosely couple components through the signals and slots mechanism. The Qt module attempts to automatically locate the Qt libraries and headers on your system. If this fails, an error will be printed. You can set the environment variable QTDIR to tell &Aap; where Qt is installed if the automatic detection does not find it. When the Qt module is loaded, an additional source file type ui is added; these are files created by Qt's Designer application which describe a GUI. You can list a .ui file as a source file in any program, library or other &Aap; target. The .ui files are processed by uic to produce C++ code which is later compiled. As part of the Qt object system, header files (and sometimes C++ sources) are progessed to create moc (Meta Object Compiler) files; these .moc files are typically included from the C++ code. The Qt module for &Aap; automatically detects this additional dependency and processes headers and C++ sources appropriately. You must use headername.moc and not headername.moc.cpp for the .moc files -- the former is the usual style of the KDE project, the latter appears only infrequently.