[Pkg-ocaml-maint-commits] r5306 - in /trunk/packages/ocamlduce/trunk/debian: man/ man/expungeduce.1 man/ocamlduce.1 man/ocamlducec.1 man/ocamlducedep.1 man/ocamlducedoc.1 man/ocamlducefind.1 man/ocamlducemktop.1 man/ocamlduceopt.1 ocamlduce.manpages
munga-guest at users.alioth.debian.org
munga-guest at users.alioth.debian.org
Wed Mar 5 15:20:32 UTC 2008
Author: munga-guest
Date: Wed Mar 5 15:20:32 2008
New Revision: 5306
URL: http://svn.debian.org/wsvn/pkg-ocaml-maint/?sc=1&rev=5306
Log:
- add manpage stubs
Added:
trunk/packages/ocamlduce/trunk/debian/man/
trunk/packages/ocamlduce/trunk/debian/man/expungeduce.1
trunk/packages/ocamlduce/trunk/debian/man/ocamlduce.1
trunk/packages/ocamlduce/trunk/debian/man/ocamlducec.1
trunk/packages/ocamlduce/trunk/debian/man/ocamlducedep.1
trunk/packages/ocamlduce/trunk/debian/man/ocamlducedoc.1
trunk/packages/ocamlduce/trunk/debian/man/ocamlducefind.1
trunk/packages/ocamlduce/trunk/debian/man/ocamlducemktop.1
trunk/packages/ocamlduce/trunk/debian/man/ocamlduceopt.1
trunk/packages/ocamlduce/trunk/debian/ocamlduce.manpages
Added: trunk/packages/ocamlduce/trunk/debian/man/expungeduce.1
URL: http://svn.debian.org/wsvn/pkg-ocaml-maint/trunk/packages/ocamlduce/trunk/debian/man/expungeduce.1?rev=5306&op=file
==============================================================================
--- trunk/packages/ocamlduce/trunk/debian/man/expungeduce.1 (added)
+++ trunk/packages/ocamlduce/trunk/debian/man/expungeduce.1 Wed Mar 5 15:20:32 2008
@@ -1,0 +1,9 @@
+.TH OCAMLDUCE 1
+
+.SH NAME
+expugneduce \- The OCamlDuce ??
+
+
+.SH SYNOPSIS
+.B expugneduce
+
Added: trunk/packages/ocamlduce/trunk/debian/man/ocamlduce.1
URL: http://svn.debian.org/wsvn/pkg-ocaml-maint/trunk/packages/ocamlduce/trunk/debian/man/ocamlduce.1?rev=5306&op=file
==============================================================================
--- trunk/packages/ocamlduce/trunk/debian/man/ocamlduce.1 (added)
+++ trunk/packages/ocamlduce/trunk/debian/man/ocamlduce.1 Wed Mar 5 15:20:32 2008
@@ -1,0 +1,101 @@
+.TH OCAMLDUCE 1
+
+.SH NAME
+ocamlduce \- The OCamlDuce interactive toplevel
+
+
+.SH SYNOPSIS
+.B ocamlduce
+[
+.B \-unsafe
+]
+[
+.BI \-I \ lib-dir
+]
+[
+.I object-files
+]
+[
+.I script-file
+]
+.SH DESCRIPTION
+
+The
+.BR ocamlduce (1)
+command is the toplevel system for OCamlDuce,
+that permits interactive use of the OCamlDuce system through a
+read-eval-print loop. In this mode, the system repeatedly reads Caml
+phrases from the input, then typechecks, compiles and evaluates
+them, then prints the inferred type and result value, if any. The
+system prints a # (sharp) prompt before reading each phrase.
+
+A toplevel phrase can span several lines. It is terminated by ;; (a
+double-semicolon). The syntax of toplevel phrases is as follows.
+
+The toplevel system is started by the command
+.BR ocamlduce (1).
+Phrases are read on standard input, results are printed on standard
+output, errors on standard error. End-of-file on standard input
+terminates
+.BR ocamlduce (1).
+
+If one or more
+.I object-files
+(ending in
+.B .cmo
+or
+.B .cma
+ ) are given, they are loaded silently before starting the toplevel.
+
+If a
+.I script-file
+is given, phrases are read silently from the file, errors printed on
+standard error.
+.BR ocamlduce (1)
+exits after the execution of the last phrase.
+
+.SH OPTIONS
+
+The following command-line options are recognized by
+.BR ocamlduce (1).
+
+.TP
+.BI \-I \ directory
+Add the given directory to the list of directories searched for
+source and compiled files. By default, the current directory is
+searched first, then the standard library directory. Directories added
+with
+.B \-I
+are searched after the current directory, in the order in which they
+were given on the command line, but before the standard library
+directory.
+
+.TP
+.B \-unsafe
+Turn bound checking off on array and string accesses (the v.(i)
+and s.[i] constructs). Programs compiled with
+.B \-unsafe
+are therefore slightly faster, but unsafe: anything can happen if the program
+accesses an array or string outside of its bounds.
+
+.SH ENVIRONMENT VARIABLES
+
+.TP
+.B LC_CTYPE
+If set to iso_8859_1, accented characters (from the
+ISO Latin-1 character set) in string and character literals are
+printed as is; otherwise, they are printed as decimal escape sequences.
+
+.TP
+.B TERM
+When printing error messages, the toplevel system
+attempts to underline visually the location of the error. It
+consults the TERM variable to determines the type of output terminal
+and look up its capabilities in the terminal database.
+
+.SH SEE ALSO
+.BR ocamlducec (1).
+.br
+.I The Objective Caml user's manual,
+chapter "The toplevel system".
+
Added: trunk/packages/ocamlduce/trunk/debian/man/ocamlducec.1
URL: http://svn.debian.org/wsvn/pkg-ocaml-maint/trunk/packages/ocamlduce/trunk/debian/man/ocamlducec.1?rev=5306&op=file
==============================================================================
--- trunk/packages/ocamlduce/trunk/debian/man/ocamlducec.1 (added)
+++ trunk/packages/ocamlduce/trunk/debian/man/ocamlducec.1 Wed Mar 5 15:20:32 2008
@@ -1,0 +1,248 @@
+.TH OCAMLDUCEC 1
+
+.SH NAME
+ocamlducec \- The OCamlDuce bytecode compiler
+
+
+.SH SYNOPSIS
+.B ocamlducec
+[
+.B \-aciv
+]
+[
+.BI \-cclib \ libname
+]
+[
+.BI \-ccopt \ option
+]
+[
+.B \-custom
+]
+[
+.B \-unsafe
+]
+[
+.BI \-o \ exec-file
+]
+[
+.BI \-I \ lib-dir
+]
+.I filename ...
+
+.B ocamlducec.opt
+.I (same options)
+
+.SH DESCRIPTION
+
+The OCamlDuce bytecode compiler
+.BR ocamlducec (1)
+compiles Caml source files to bytecode object files and link
+these object files to produce standalone bytecode executable files.
+These executable files are then run by the bytecode interpreter
+.BR ocamlducerun (1).
+
+The
+.BR ocamlducec (1)
+command has a command-line interface similar to the one of
+most C compilers. It accepts several types of arguments and processes them
+sequentially:
+
+Arguments ending in .mli are taken to be source files for
+compilation unit interfaces. Interfaces specify the names exported by
+compilation units: they declare value names with their types, define
+public data types, declare abstract data types, and so on. From the
+file
+.IR x \&.mli,
+the
+.BR ocamlducec (1)
+compiler produces a compiled interface
+in the file
+.IR x \&.cmi.
+
+Arguments ending in .ml are taken to be source files for compilation
+unit implementations. Implementations provide definitions for the
+names exported by the unit, and also contain expressions to be
+evaluated for their side-effects. From the file
+.IR x \&.ml,
+the
+.BR ocamlducec (1)
+compiler produces compiled object bytecode in the file
+.IR x \&.cmo.
+
+If the interface file
+.IR x \&.mli
+exists, the implementation
+.IR x \&.ml
+is checked against the corresponding compiled interface
+.IR x \&.cmi,
+which is assumed to exist. If no interface
+.IR x \&.mli
+is provided, the compilation of
+.IR x \&.ml
+produces a compiled interface file
+.IR x \&.cmi
+in addition to the compiled object code file
+.IR x \&.cmo.
+The file
+.IR x \&.cmi
+produced
+corresponds to an interface that exports everything that is defined in
+the implementation
+.IR x \&.ml.
+
+Arguments ending in .cmo are taken to be compiled object bytecode. These
+files are linked together, along with the object files obtained
+by compiling .ml arguments (if any), and the Caml Light standard
+library, to produce a standalone executable program. The order in
+which .cmo and.ml arguments are presented on the command line is
+relevant: compilation units are initialized in that order at
+run-time, and it is a link-time error to use a component of a unit
+before having initialized it. Hence, a given
+.IR x \&.cmo
+file must come before all .cmo files that refer to the unit
+.IR x .
+
+Arguments ending in .cma are taken to be libraries of object bytecode.
+A library of object bytecode packs in a single file a set of object
+bytecode files (.cmo files). Libraries are built with
+.B ocamlducec \-a
+(see the description of the
+.B \-a
+option below). The object files
+contained in the library are linked as regular .cmo files (see above), in the order specified when the .cma file was built. The only difference is that if an object file
+contained in a library is not referenced anywhere in the program, then
+it is not linked in.
+
+Arguments ending in .c are passed to the C compiler, which generates a .o object file. This object file is linked with the program if the
+.B \-custom
+flag is set (see the description of
+.B \-custom
+below).
+
+Arguments ending in .o or .a are assumed to be C object files and
+libraries. They are passed to the C linker when linking in
+.B \-custom
+mode (see the description of
+.B \-custom
+below).
+
+.B ocamlducec.opt
+is the same compiler as
+.BR ocamlducec ,
+but compiled with the native-code compiler
+.BR ocamlduceopt (1).
+Thus, it behaves exactly like
+.BR ocamlducec ,
+but compiles faster.
+.B ocamlducec.opt
+is not available in all installations of OCamlDuce.
+
+.SH OPTIONS
+
+The following command-line options are recognized by
+.BR ocamlducec (1).
+
+.TP
+.B \-a
+Build a library (.cma file) with the object files (.cmo files) given on the command line, instead of linking them into an executable
+file. The name of the library can be set with the
+.B \-o
+option. The default name is
+.BR library.cma .
+
+.TP
+.B \-c
+Compile only. Suppress the linking phase of the
+compilation. Source code files are turned into compiled files, but no
+executable file is produced. This option is useful to
+compile modules separately.
+
+.TP
+.BI \-cclib\ -l libname
+Pass the
+.BI \-l libname
+option to the C linker when linking in
+``custom runtime'' mode (see the
+.B \-custom
+option). This causes the
+given C library to be linked with the program.
+
+.TP
+.B \-ccopt
+Pass the given option to the C compiler and linker, when linking in
+``custom runtime'' mode (see the
+.B \-custom
+option). For instance,
+.B -ccopt -L
+.I dir
+causes the C linker to search for C libraries in
+directory
+.IR dir .
+
+.TP
+.B \-custom
+Link in ``custom runtime'' mode. In the default linking mode, the
+linker produces bytecode that is intended to be executed with the
+shared runtime system,
+.BR ocamlducerun (1).
+In the custom runtime mode, the
+linker produces an output file that contains both the runtime system
+and the bytecode for the program. The resulting file is larger, but it
+can be executed directly, even if the
+.BR ocamlducerun (1)
+command is not
+installed. Moreover, the ``custom runtime'' mode enables linking Caml
+code with user-defined C functions.
+
+.TP
+.B \-i
+Cause the compiler to print all defined names (with their inferred
+types or their definitions) when compiling an implementation (.ml
+file). This can be useful to check the types inferred by the
+compiler. Also, since the output follows the syntax of interfaces, it
+can help in writing an explicit interface (.mli file) for a file: just
+redirect the standard output of the compiler to a .mli file, and edit
+that file to remove all declarations of unexported names.
+
+.TP
+.BI \-I \ directory
+Add the given directory to the list of directories searched for
+compiled interface files (.cmi) and compiled object code files
+(.cmo). By default, the current directory is searched first, then the
+standard library directory. Directories added with
+.B -I
+are searched
+after the current directory, in the order in which they were given on
+the command line, but before the standard library directory.
+
+.TP
+.BI \-o \ exec-file
+Specify the name of the output file produced by the linker. The
+default output name is
+.BR a.out ,
+in keeping with the Unix tradition. If the
+.B \-a
+option is given, specify the name of the library produced.
+
+.TP
+.B \-v
+Print the version number of the compiler.
+
+.TP
+.B \-unsafe
+Turn bound checking off on array and string accesses (the
+.B v.(i)
+and
+.B s.[i]
+constructs). Programs compiled with
+.B \-unsafe
+are therefore
+slightly faster, but unsafe: anything can happen if the program
+accesses an array or string outside of its bounds.
+
+.SH SEE ALSO
+.BR ocamlduce (1),
+.BR ocamlrun (1).
+.br
+.I The Objective Caml user's manual,
+chapter "Batch compilation".
Added: trunk/packages/ocamlduce/trunk/debian/man/ocamlducedep.1
URL: http://svn.debian.org/wsvn/pkg-ocaml-maint/trunk/packages/ocamlduce/trunk/debian/man/ocamlducedep.1?rev=5306&op=file
==============================================================================
--- trunk/packages/ocamlduce/trunk/debian/man/ocamlducedep.1 (added)
+++ trunk/packages/ocamlduce/trunk/debian/man/ocamlducedep.1 Wed Mar 5 15:20:32 2008
@@ -1,0 +1,79 @@
+.TH OCAMLDUCEDEP 1
+
+.SH NAME
+ocamlducedep \- Dependency generator for OCamlDuce
+
+.SH SYNOPSIS
+.B ocamlducedep
+[
+.BI \-I \ lib-dir
+]
+.I filename ...
+
+.SH DESCRIPTION
+
+The
+.BR ocamlducedep (1)
+command scans a set of Objective Caml source files
+(.ml and .mli files) for references to external compilation units,
+and outputs dependency lines in a format suitable for the
+.BR make (1)
+utility. This ensures that make will compile the source files in the
+correct order, and recompile those files that need to when a source
+file is modified.
+
+The typical usage is:
+.P
+ocamlducedep
+.I options
+*.mli *.ml > .depend
+.P
+where .depend is the file that should contain the
+dependencies.
+
+Dependencies are generated both for compiling with the bytecode
+compiler
+.BR ocamlducec (1)
+and with the native-code compiler
+.BR ocamlduceopt (1).
+
+.SH OPTIONS
+
+The following command-line option is recognized by
+.BR ocamlducedep (1).
+
+.TP
+.BI \-I \ directory
+Add the given directory to the list of directories searched for
+source files. If a source file foo.ml mentions an external
+compilation unit Bar, a dependency on that unit's interface
+bar.cmi is generated only if the source for bar is found in the
+current directory or in one of the directories specified with
+.BR -I .
+Otherwise, Bar is assumed to be a module form the standard library,
+and no dependencies are generated. For programs that span multiple
+directories, it is recommended to pass
+.BR ocamlducedep (1)
+the same -I options that are passed to the compiler.
+
+.TP
+.BI \-native
+Generate dependencies for a pure native-code program (no bytecode
+version). When an implementation file (.ml file) has no explicit
+interface file (.mli file),
+.BR ocamlducedep (1)
+generates dependencies on the
+bytecode compiled file (.cmo file) to reflect interface changes.
+This can cause unnecessary bytecode recompilations for programs that
+are compiled to native-code only. The flag
+.BR -native
+causes dependencies on native compiled files (.cmx) to be generated instead
+of on .cmo files. (This flag makes no difference if all source files
+have explicit .mli interface files.)
+
+.SH SEE ALSO
+.BR ocamlducec (1),
+.BR ocamlopt (1).
+.br
+.I The Objective Caml user's manual,
+chapter "Dependency generator".
Added: trunk/packages/ocamlduce/trunk/debian/man/ocamlducedoc.1
URL: http://svn.debian.org/wsvn/pkg-ocaml-maint/trunk/packages/ocamlduce/trunk/debian/man/ocamlducedoc.1?rev=5306&op=file
==============================================================================
--- trunk/packages/ocamlduce/trunk/debian/man/ocamlducedoc.1 (added)
+++ trunk/packages/ocamlduce/trunk/debian/man/ocamlducedoc.1 Wed Mar 5 15:20:32 2008
@@ -1,0 +1,9 @@
+.TH OCAMLDUCE 1
+
+.SH NAME
+ocamlducedoc \- The OCamlDuce ??
+
+
+.SH SYNOPSIS
+.B ocamlducedoc
+
Added: trunk/packages/ocamlduce/trunk/debian/man/ocamlducefind.1
URL: http://svn.debian.org/wsvn/pkg-ocaml-maint/trunk/packages/ocamlduce/trunk/debian/man/ocamlducefind.1?rev=5306&op=file
==============================================================================
--- trunk/packages/ocamlduce/trunk/debian/man/ocamlducefind.1 (added)
+++ trunk/packages/ocamlduce/trunk/debian/man/ocamlducefind.1 Wed Mar 5 15:20:32 2008
@@ -1,0 +1,9 @@
+.TH OCAMLDUCE 1
+
+.SH NAME
+ocamlduceifind \- The OCamlDuce ??
+
+
+.SH SYNOPSIS
+.B ocamlducefind
+
Added: trunk/packages/ocamlduce/trunk/debian/man/ocamlducemktop.1
URL: http://svn.debian.org/wsvn/pkg-ocaml-maint/trunk/packages/ocamlduce/trunk/debian/man/ocamlducemktop.1?rev=5306&op=file
==============================================================================
--- trunk/packages/ocamlduce/trunk/debian/man/ocamlducemktop.1 (added)
+++ trunk/packages/ocamlduce/trunk/debian/man/ocamlducemktop.1 Wed Mar 5 15:20:32 2008
@@ -1,0 +1,84 @@
+.TH OCAMLDUCEMKTOP 1
+
+.SH NAME
+ocamlducemktop \- Building custom toplevel systems
+
+.SH SYNOPSIS
+.B ocamlducemktop
+[
+.B \-v
+]
+[
+.BI \-cclib \ libname
+]
+[
+.BI \-ccopt \ option
+]
+[
+.B \-custom
+[
+.BI \-o \ exec-file
+]
+[
+.BI \-I \ lib-dir
+]
+.I filename ...
+
+.SH DESCRIPTION
+
+The
+.BR ocamlducemktop (1)
+command builds OCamlDuce toplevels that
+contain user code preloaded at start-up.
+The
+.BR ocamlducemktop (1)
+command takes as argument a set of
+.IR x \&.cmo
+and
+.IR x \&.cma
+files, and links them with the object files that implement the OCamlDuce toplevel. If the
+.B -custom
+flag is given, C object files and libraries (.o and .a files) can also
+be given on the command line and are linked in the resulting toplevel.
+
+.SH OPTIONS
+
+The following command-line options are recognized by
+.BR ocamlducemktop (1).
+
+.TP
+.B \-v
+Print the version number of the compiler.
+
+.TP
+.BI \-cclib\ -l libname
+Pass the
+.BI \-l libname
+option to the C linker when linking in
+``custom runtime'' mode (see the corresponding option for
+.BR ocamlducec (1).
+
+.TP
+.B \-ccopt
+Pass the given option to the C compiler and linker, when linking in
+``custom runtime'' mode. See the corresponding option for
+.BR ocamlducec (1).
+
+.TP
+.B \-custom
+Link in ``custom runtime'' mode. See the corresponding option for
+.BR ocamlducec (1).
+
+.TP
+.BI \-I directory
+Add the given directory to the list of directories searched for
+compiled interface files (.cmo and .cma).
+
+.TP
+.BI \-o \ exec-file
+Specify the name of the toplevel file produced by the linker.
+The default is is
+.BR a.out .
+
+.SH SEE ALSO
+.BR ocamlducec (1).
Added: trunk/packages/ocamlduce/trunk/debian/man/ocamlduceopt.1
URL: http://svn.debian.org/wsvn/pkg-ocaml-maint/trunk/packages/ocamlduce/trunk/debian/man/ocamlduceopt.1?rev=5306&op=file
==============================================================================
--- trunk/packages/ocamlduce/trunk/debian/man/ocamlduceopt.1 (added)
+++ trunk/packages/ocamlduce/trunk/debian/man/ocamlduceopt.1 Wed Mar 5 15:20:32 2008
@@ -1,0 +1,231 @@
+.TH OCAMLDUCEOPT 1
+
+.SH NAME
+ocamlduceopt \- The OCamlDuce native-code compiler
+
+
+.SH SYNOPSIS
+.B ocamlduceopt
+[
+.B \-acivS
+]
+[
+.BI \-cclib \ libname
+]
+[
+.BI \-ccopt \ option
+]
+[
+.B \-compact
+]
+[
+.B \-unsafe
+]
+[
+.BI \-o \ exec-file
+]
+[
+.BI \-I \ lib-dir
+]
+.I filename ...
+
+.B ocamlduceopt.opt
+.I (same options)
+
+.SH DESCRIPTION
+The OCamlDuce high-performance
+native-code compiler
+.BR ocamlduceopt (1)
+compiles Caml source files to native code object files and link these
+object files to produce standalone executables.
+
+The
+.BR ocamlduceopt (1)
+command has a command-line interface very close to that
+of
+.BR ocamlducec (1).
+It accepts the same types of arguments and processes them
+sequentially:
+
+Arguments ending in .mli are taken to be source files for
+compilation unit interfaces. Interfaces specify the names exported by
+compilation units: they declare value names with their types, define
+public data types, declare abstract data types, and so on. From the
+file
+.IR x \&.mli,
+the
+.BR ocamlduceopt (1)
+compiler produces a compiled interface
+in the file
+.IR x \&.cmi.
+The interface produced is identical to that
+produced by the bytecode compiler
+.BR ocamlducec (1).
+
+Arguments ending in .ml are taken to be source files for compilation
+unit implementations. Implementations provide definitions for the
+names exported by the unit, and also contain expressions to be
+evaluated for their side-effects. From the file
+.IR x \&.ml,
+the
+.BR ocamlduceopt (1)
+compiler produces two files:
+.IR x \&.o,
+containing native object code, and
+.IR x \&.cmx,
+containing extra information for linking and
+optimization of the clients of the unit. The compiled implementation
+should always be referred to under the name
+.IR x \&.cmx
+(when given a .o file,
+.BR ocamlduceopt (1)
+assumes that it contains code compiled from C, not from Caml).
+
+The implementation is checked against the interface file
+.IR x \&.mli
+(if it exists) as described in the manual for
+.BR ocamlducec (1).
+
+Arguments ending in .cmx are taken to be compiled object code. These
+files are linked together, along with the object files obtained
+by compiling .ml arguments (if any), and the Caml Light standard
+library, to produce a native-code executable program. The order in
+which .cmx and .ml arguments are presented on the command line is
+relevant: compilation units are initialized in that order at
+run-time, and it is a link-time error to use a component of a unit
+before having initialized it. Hence, a given
+.IR x \&.cmx
+file must come
+before all .cmx files that refer to the unit
+.IR x .
+
+Arguments ending in .cmxa are taken to be libraries of object code.
+Such a library packs in two files
+.IR lib \&.cmxa
+and
+.IR lib \&.a
+a set of object files (.cmx/.o files). Libraries are build with
+.B ocamlduceopt \-a
+(see the description of the
+.B \-a
+option below). The object
+files contained in the library are linked as regular .cmx files (see
+above), in the order specified when the library was built. The only
+difference is that if an object file contained in a library is not
+referenced anywhere in the program, then it is not linked in.
+
+Arguments ending in .c are passed to the C compiler, which generates
+a .o object file. This object file is linked with the program.
+
+Arguments ending in .o or .a are assumed to be C object files and
+libraries. They are linked with the program.
+
+The output of the linking phase is a regular Unix executable file. It
+does not need
+.BR ocamlducerun (1)
+to run.
+
+.B ocamlduceopt.opt
+is the same compiler as
+.BR ocamlduceopt ,
+but compiled with itself instead of with the bytecode compiler
+.BR ocamlducec (1).
+Thus, it behaves exactly like
+.BR ocamlduceopt ,
+but compiles faster.
+.B ocamlduceopt.opt
+is not available in all installations of OCamlDuce.
+
+.SH OPTIONS
+
+The following command-line options are recognized by
+.BR ocamlduceopt (1).
+
+.TP
+.B \-a
+Build a library (.cmxa/.a file) with the object files (.cmx/.o
+files) given on the command line, instead of linking them into an
+executable file. The name of the library can be set with the
+.B \-o
+option. The default name is library.cmxa.
+
+.TP
+.B \-c
+Compile only. Suppress the linking phase of the
+compilation. Source code files are turned into compiled files, but no
+executable file is produced. This option is useful to
+compile modules separately.
+
+.TP
+.BI \-cclib\ -l libname
+Pass the
+.BI -l libname
+option to the linker. This causes the given C library to be linked
+with the program.
+
+.TP
+.BI \-ccopt \ option
+Pass the given option to the C compiler and linker. For instance,
+.B -ccopt -L
+.I dir
+causes the C linker to search for C libraries in
+directory
+.IR dir .
+
+.TP
+.B \-compact
+Optimize the produced code for space rather than for time. This
+results in smaller but slightly slower programs. The default is to
+optimize for speed.
+
+.TP
+.B \-i
+Cause the compiler to print all defined names (with their inferred
+types or their definitions) when compiling an implementation (.ml
+file). This can be useful to check the types inferred by the
+compiler. Also, since the output follows the syntax of interfaces, it
+can help in writing an explicit interface (.mli file) for a file:
+just redirect the standard output of the compiler to a .mli file,
+and edit that file to remove all declarations of unexported names.
+
+.TP
+.BI \-I \ directory
+Add the given directory to the list of directories searched for
+compiled interface files (.cmi) and compiled object code files
+(.cmo). By default, the current directory is searched first, then the
+standard library directory. Directories added with -I are searched
+after the current directory, in the order in which they were given on
+the command line, but before the standard library directory.
+
+.TP
+.BI \-o \ exec-file
+Specify the name of the output file produced by the linker. The
+default output name is a.out, in keeping with the Unix tradition. If
+the
+.B \-a
+option is given, specify the name of the library produced.
+
+.TP
+.B \-S
+Keep the assembly code produced during the compilation. The assembly
+code for the source file
+.IR x \&.ml
+is saved in the file
+.IR x \&.s.
+
+.TP
+.B \-v
+Print the version number of the compiler.
+
+.TP
+.B \-unsafe
+Turn bound checking off on array and string accesses (the v.(i) and
+s.[i] constructs). Programs compiled with -unsafe are therefore
+faster, but unsafe: anything can happen if the program accesses an
+array or string outside of its bounds.
+
+.SH SEE ALSO
+.BR ocamlducec (1).
+.br
+.I The Objective Caml user's manual,
+chapter "Native-code compilation".
Added: trunk/packages/ocamlduce/trunk/debian/ocamlduce.manpages
URL: http://svn.debian.org/wsvn/pkg-ocaml-maint/trunk/packages/ocamlduce/trunk/debian/ocamlduce.manpages?rev=5306&op=file
==============================================================================
--- trunk/packages/ocamlduce/trunk/debian/ocamlduce.manpages (added)
+++ trunk/packages/ocamlduce/trunk/debian/ocamlduce.manpages Wed Mar 5 15:20:32 2008
@@ -1,0 +1,9 @@
+debian/man/expungeduce.1
+debian/man/ocamlduce.1
+debian/man/ocamlducec.1
+debian/man/ocamlducedep.1
+debian/man/ocamlducedoc.1
+debian/man/ocamlducefind.1
+debian/man/ocamlducemktop.1
+debian/man/ocamlduceopt.1
+
More information about the Pkg-ocaml-maint-commits
mailing list