OCAMLMKTOP(1) General Commands Manual OCAMLMKTOP(1)NAME
ocamlmktop - Building custom toplevel systems
ocamlmktop [ -v|-version|-vnum ] [ -cclib libname ] [ -ccopt option ] [ -custom [ -o exec-file ] [ -I lib-dir ] filename ...
The ocamlmktop(1) command builds OCaml toplevels that contain user code preloaded at start-up. The ocamlmktop(1) command takes as argument
a set of x.cmo and x.cma files, and links them with the object files that implement the OCaml toplevel. If the -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.
The following command-line options are recognized by ocamlmktop(1).
-v Print the version string of the compiler and exit.
Print the version number of the compiler in short form and exit.
Pass the -llibname option to the C linker when linking in ``custom runtime'' mode (see the corresponding option for ocamlc(1).
-ccopt Pass the given option to the C compiler and linker, when linking in ``custom runtime'' mode. See the corresponding option for
Link in ``custom runtime'' mode. See the corresponding option for ocamlc(1).
Add the given directory to the list of directories searched for compiled interface files (.cmo and .cma).
Specify the name of the toplevel file produced by the linker. The default is is a.out.
SEE ALSO ocamlc(1).
Check Out this Related Man Page
OCAMLDEBUG(1) General Commands Manual OCAMLDEBUG(1)NAME
ocamldebug - the OCaml source-level replay debugger.
ocamldebug [ options ] program [ arguments ]
ocamldebug is the OCaml source-level replay debugger.
Before the debugger can be used, the program must be compiled and linked with the -g option: all .cmo and .cma files that are part of the
program should have been created with ocamlc -g, and they must be linked together with ocamlc -g.
Compiling with -g entails no penalty on the running time of programs: object files and bytecode executable files are bigger and take longer
to produce, but the executable files run at exactly the same speed as if they had been compiled without -g.
A summary of options are included below. For a complete description, see the html documentation in the ocaml-doc package.
Set the maximum number of simultaneously live checkpoints to count.
Run the debugger program from the working directory dir, instead of the current working directory. (See also the cd command.)
-emacs Tell the debugger it is executed under Emacs. (See The OCaml user's manual for information on how to run the debugger under Emacs.)
Add directory to the list of directories searched for source files and compiled files. (See also the directory command.)
Use socket for communicating with the debugged program. See the description of the command set socket in The OCaml user's manual for
the format of socket.
Print version string and exit.
-vnum Print short version number and exit.
-help or --help
Display a short usage summary and exit.
SEE ALSO ocamlc(1)
The OCaml user's manual, chapter "The debugger".
This manual page was written by Sven LUTHER <email@example.com>, for the Debian GNU/Linux system (but may be used by others).
I have written a makefile and am facing some problem in linking..
This is the first makefile i write.. i think that am just compiling all the .c files and not linking the object files.. can anybody tell me how to link all the .o files???
When i do make all i am getting the following... (1 Reply)
I'm getting the a runtime error:
aCC runtime: Use of "-mt" must be consistent during both compilation and linking
I build my executable with -mt and I link with libraries that were compiled with -mt too (we have other executables that links with them and don't have this problem).... (1 Reply)
First off all , let me apologize for my inexperience. I am just starting use of Linux and gcc .
Actually I ve some .c files in the present directory , and now I am
+vc <my_file1.c> <my.file2.c> <myfile3.c>.
All the c files are in present directory.... (2 Replies)
I use Solaris 10, compiling with a custom g++ (3.4.6) and GNU binutils (2.17). Things have gone well on two different systems, but when I tried moving to a third, it all fell over. Basically, it is now using the CC linker, but I need to use options not available to it. I believe I have found the... (0 Replies)
we have 2.2.0 of opends running on RedHat 2.6.21 and we're trying to setup a structure that will suit our needs. One of the things we'd like to do is create our own custom object classes based off some of the existing ones you get out of the box. The opends documentation covers this here (sorry, it... (1 Reply)
I'm facing an issue in which my program is using a custom library (say, libxyz.so) which is compiled using libstdc++.so.5 and the system I'm using this library to create an executable from my program, has libstdc++so.6 as well as libstdc++.so.5; both available under /usr/lib directory.
There are... (8 Replies)
ps command behavior in Redhat is such that it outputs all the output(of long lengths). In Unix the ps command output was limited to only 80 chars. In that if you pipe its output to another command hen the 80 chars restriction wouldn't be there. This 80 char limitation will only be... (14 Replies)