compiles modules, programs and web applications in the Kaya programming language.
kayac will automatically compile dependencies as necessary provided that, for a dependency Foo, the source file is called Foo.k and is in the current working directory.
-? | -h | -help
Show usage summary
-v | -version
Show version number
Show the directory in which the libraries are installed
-L DIRECTORY | -libdir DIRECTORY
Add DIRECTORY to the library search path.
Force compilation even if kayac thinks it isn't needed.
Quiet compilation; don't report which module is being built.
Don't chase up and compile dependencies. Implies -force and -q.
Fail compilation if a deprecated function is called.
Don't import the Prelude (probably only useful when compiling the standard library). Compiling anything other than modules with this option is unlikely to work well.
kayac will ignore the KAYA_LIBRARY_PATH environment variable when compiling, and will not import from the compiled-in library directories (probably only useful when compiling the standard library)
Disables some run-time checking. This speeds up the final program, at the cost of making errors harder to track down (and possibly introducing additional subtle errors where an exception would previously have occurred). Only recommended for bug free programs...
Uses a version of the Kaya VM that is optimised for applications such as web applications with a short run-time (a few seconds or less) for which it is significantly faster than the normal VM. However, for longer-running applications memory usage can grow very rapidly. This option implies and takes precedence over -nortchecks.
Disables compile-time optimisations. Probably only useful for debugging purposes.
Read-Eval-Print loop mode. In this mode you can interactively test the behaviour of functions without needing to build a separate testing program, in a top-level interpreter. See
for more information. This option implies -pic.
Use the -fPIC option of the C compiler to make position-independent code suitable for shared libraries. This option has no effect on Windows, where all code is position-independent.
Generate XML documentation. This can then be converted into HTML or Manpage format using the KayaDoc module and the
Statically link executables so that they can be run on a wider range
of systems at the cost of signficantly increased file size. This is
generally only useful if you are making a pre-compiled binary
distribution. You may get some warnings from the linker about
potential problems and limitations when linking some libraries, or
compilation may fail entirely if the static libraries are unavailable.
Turns on profiling in the output code. The program will then generate a gmon.out file when run, which can then be analysed with a program such as
gprof(1). This option also enables -static, and to get a useful call graph report from gprof, your libgc library must have been compiled with profiling enabled.
Use a string to seed the random number generator which makes a secret key. Useful for testing web apps.
These options generate debugging information.
Dump the raw parse tree.
Dump the type checked parse tree.
Dump the simplified, desugared and optimised code in a human readable (almost) form.
Dump the type equations used in type inference
Dump the function call graph
Dump the module dependency graph
Keep the generated C code
Print the command sent to gcc
A list of extra paths to search for kaya libraries. Paths are separated by ':' on Posix systems, and ';' on Windows.