1212
livecode/toolchain/lc-run.1.md at develop · LiveCodeSteven/livecode · GitHub
Skip to content

Latest commit

 

History

History
56 lines (37 loc) · 1.83 KB

File metadata and controls

56 lines (37 loc) · 1.83 KB

lc-run(1) -- run LiveCode Builder bytecode programs

SYNOPSIS

lc-run [OPTION ...] [--handler NAME] [--] LCMFILE [ARG ...]

lc-run [OPTION ...] --list-handlers [--] LCMFILE

DESCRIPTION

lc-run runs a LiveCode Builder program from the bytecode file LCMFILE. When running an LCB program with lc-run, some standard libraries are unavailable (e.g. the canvas and engine libraries).

lc-run can use any public, top-level handler with no arguments as an entry point. If the --handler option is not used to specify an entry point NAME, then lc-run looks for a handler named main().

The --list-handlers option can be used to obtain a list of valid entry points for a particular LCMFILE.

Any arguments ARG... specified after LCMFILE are available to the program as the value of the command arguments.

OPTIONS

  • -l, --load LCMLIB: In addition to loading the LCMFILE, load a module from the bytecode file LCMLIB. Any number of --load options may be provided. LCMFILE is loaded first, followed by each LCMLIB in reverse order.

  • -H, --handler NAME: Call the handler with the specified NAME as the entry point of the program. NAME must have public visibility and accept no arguments. The default value of NAME is main.

  • --list-handlers: Don't run the program. Instead, print a list of valid entry point handlers in LCMFILE to standard output.

  • -h, --help: Print some basic usage information.

  • --: Stop processing options. This is useful in case LCMFILE begins with - or --.

COPYRIGHT

Copyright 2015 LiveCode Ltd.

This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

SEE ALSO

lc-compile(1).