Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

gtkamlc(1) [debian man page]

GTKAMLC(1)						      General Commands Manual							GTKAMLC(1)

NAME

       gtkamlc - Gtkaml/GtkON compiler

SYNOPSIS

       gtkamlc [options] files...
       gtkaml [options] files...

DESCRIPTION

       This manual page documents briefly the gtkamlc command.

       gtkamlc	is  a  compiler  for the Gtkaml and the GtkON languages. These languages let you create GTK UIs to be used in Vala programs with a
       compact syntax.

       gtkaml uses the compiler and runs the output executable. For GtkON files, support for #! is enabled.

       Please see the SEE ALSO section for more information.

OPTIONS

   Gtkamlc options
       --dump-tree=FILE
	      Write code tree to FILE, allowing one to inspect the output from the gtkaml/gtkon input files

   Options inherited from Valac
       -?, --help
	      Show summary of options.

       --version
	      Show version of program.

       --vapidir=DIRECTORY
	      Look for package bindings in DIRECTORY

       --pkg=PACKAGE
	      Include binding for PACKAGE

       --vapi=FILE
	      Output vapi to FILE

       --library=NAME
	      Library name

       --gir=NAME-VERSION.gir
	      GObject-Introspection repository file name

       --girdir=DIRECTORY
	      Look for .gir files in DIRECTORY

       --genie
	      Enable Genie syntax mode for gtkon files

       -b, --basedir=DIRECTORY
	      Base source directory

       -d, --directory=DIRECTORY
	      Output directory

       -C, --ccode
	      Output C code

       -H, --header=FILE
	      Output C header file

       --use-header
	      Use C header file

       --includedir=DIRECTORY
	      Directory used to include the C header file

       -h, --internal-header=FILE
	      Output internal C header file

       --internal-vapi=FILE
	      Output vapi with internal api

       --symbols=FILE
	      Output symbols file

       -c, --compile
	      Compile but do not link

       -o, --output=FILE
	      Place output in file FILE

       -g, --debug
	      Produce debug information

       --thread
	      Enable multithreading support

       --enable-mem-profiler
	      Enable GLib memory profiler

       -D, --define=SYMBOL
	      Define SYMBOL

       --main=SYMBOL
	      Use SYMBOL as entry point

       --nostdpkg
	      Do not include standard packages

       --disable-assert
	      Disable assertions

       --enable-checking
	      Enable additional run-time checks

       --enable-deprecated
	      Enable deprecated features

       --enable-experimental
	      Enable experimental features

       --disable-warnings
	      Disable warnings

       --fatal-warnings
	      Treat warnings as fatal

       --enable-experimental-non-null
	      Enable experimental enhancements for non-null types

       --disable-dbus-transformation
	      Disable transformation of D-Bus member names

       --cc=COMMAND
	      Use COMMAND as C compiler command

       -X, --Xcc=OPTION
	      Pass OPTION to the C compiler

       --save-temps
	      Keep temporary files

       --profile=PROFILE
	      Use the given profile instead of the default

       -q, --quiet
	      Do not print messages to the console

       -v, --verbose
	      Print additional messages to the console

       --target-glib=MAJOR.MINOR
	      Target version of glib for code generation

       --enable-version-header, --disable-version-header
	      Write/do not write vala build version in generated files

SEE ALSO

       For more  information  on  the  Gtkaml  and  the  GtkON	languages,  please  see  the  documentation  available	at  the  project  website:
       http://code.google.com/p/gtkaml/.

AUTHOR

       gtkaml was written by Vlad Grecescu <b100dian@gmail.com>.

       This manual page was written by David Paleino <dapal@debian.org>, for the Debian project (and may be used by others).

								    Dec 1, 2011 							GTKAMLC(1)

Check Out this Related Man Page

BUILDAPP(1)							   User Commands						       BUILDAPP(1)

NAME

       buildapp - application to create common lisp images

SYNOPSIS

       buildapp --output OUTPUT-FILE [--flag1 value1 ...]

DESCRIPTION

   Required flags:
       --output OUTPUT-FILE
	      Use OUTPUT-FILE as the name of the executable to create

   Entry-point flags:
       --entry NAME
	      Use  the function identified by NAME as the executable's toplevel function. Called with SB-EXT:*POSIX-ARGV* as its only argument. If
	      NAME has a colon, it is treated as a package separator, otherwise CL-USER is the implied package.

       --dispatched-entry DNAME
	      Specify one possible entry function, depending on the name of the file that is used to start the application. The syntax of DNAME is
	      APPLICATION-NAME/ENTRY-NAME.  If	the name used to start the executable matches APPLICATION-NAME, use ENTRY-NAME as the entry point.
	      This can be used to choose one of many possible entry points by e.g. symlinking names to the  application  executable.  If  APPLICA-
	      TION-NAME  is  empty,  the specified ENTRY-NAME is used as a default if no other application names match. There may be any number of
	      dispatched entry points, but only one default.

   Action flags:
       --load FILE
	      Load FILE. CL:*PACKAGE* is bound to the CL-USER package before loading

       --load-system NAME
	      Load an ASDF system identified by NAME

       --require NAME
	      Use CL:REQUIRE to load NAME

       --eval CODE
	      Use CL:EVAL to evaulate CODE. The code is read with CL:READ-FROM-STRING in the CL-USER package

       There may be any number of load/load-system/require/eval flags. Each is executed in command-line order before creating an executable.

   Load path flags:
       --load-path DIRECTORY
	      When handling a --load, search DIRECTORY for files to load

       --asdf-path DIRECTORY
	      When handling a --load-system, search DIRECTORY for ASDF system files to load

       --asdf-tree DIRECTORY
	      When handling a --load-system, search DIRECTORY and all its subdirectories for ASDF system files to load

       There may be any number of load-path/asdf-path/asdf-tree flags. asdf-path arguments take precedence over asdf-tree arguments.

   Other flags:
       --help Show this usage message

       --logfile FILE
	      Log compilation and load output to FILE

       --sbcl PATH-TO-SBCL
	      Use PATH-TO-SBCL instead of the sbcl program found in your PATH environment variable

       For the latest documentation, see http://www.xach.com/lisp/buildapp/

buildapp 1.1							     July 2010							       BUILDAPP(1)
Man Page