>

>

>Does findlib support linking of applications as well as

packages?

>

NAME="GENERATOR"

CONTENT="Modular DocBook HTML Stylesheet Version 1.79">

REL="HOME"

TITLE="The findlib User's Guide"

HREF="index.html">

REL="UP"

TITLE="FAQs"

HREF="c429.html">

REL="PREVIOUS"

TITLE="Why does findlib not automatically include the -custom option if

linked with C code?"

HREF="x443.html">

REL="NEXT"

TITLE="	  Does Findlib support camlp4?

        "

HREF="x461.html">

>

CLASS="SECT1"

BGCOLOR="#FFFFFF"

TEXT="#000000"

LINK="#0000FF"

VLINK="#840084"

ALINK="#0000FF"

>

CLASS="NAVHEADER"

>

SUMMARY="Header navigation table"

WIDTH="100%"

BORDER="0"

CELLPADDING="0"

CELLSPACING="0"

>

>

COLSPAN="3"

ALIGN="center"

>The findlib User's Guide

>

>

>

WIDTH="10%"

ALIGN="left"

VALIGN="bottom"

>

HREF="x443.html"

ACCESSKEY="P"

>Prev

>

>

WIDTH="80%"

ALIGN="center"

VALIGN="bottom"

>Chapter 7. FAQs

>

WIDTH="10%"

ALIGN="right"

VALIGN="bottom"

>

HREF="x461.html"

ACCESSKEY="N"

>Next

>

>

>

>

ALIGN="LEFT"

WIDTH="100%">

>

CLASS="SECT1"

>

CLASS="SECT1"

>

NAME="AEN449"

>Does findlib support linking of applications as well as

packages?

>

>

>

CLASS="emphasis"

>

CLASS="EMPHASIS"

>Short answer:

>

> Yes, but it is not very obvious

>

>Applications also depend on other components, they have predicates, sometimes

they need linker options; there seems to be only little difference between

applications (stand-alone programs) and packages. If you want to use the

findlib mechanisms for applications, too, the following trick helps.

>

>The environment variable 

CLASS="LITERAL"

>OCAMLPATH

> may contain a

colon-separated path of possible sitelib locations. It is allowed to include

"." into the path (Shell commands follow):

CLASS="PROGRAMLISTING"

>OCAMLPATH=.

export OCAMLPATH

>

This makes ".", i.e.  your current directory, another sitelib location. You may

now put the components of your applications into subdirectories together with

META files; the hierarchy might look as follows:

CLASS="PROGRAMLISTING"

>./Makefile                          global Makefile

./localpkg1/META                    first local package directory: Contains META

./localpkg1/...                     ... and more

./localpkg2/META                    second local package dir: Contains META

./localpkg2/...                     ... and more

...

>

From findlib's point of view, these directories are now package directories,

and you can refer to them on the command line:

CLASS="PROGRAMLISTING"

>ocamlfind ocamlc -o ... -linkpkg -package localpkg1,localpkg2,...

>

If you do not want subdirectories, you can also refer to the META file in the

same directory by the name ".", e.g.:

CLASS="PROGRAMLISTING"

>ocamlfind ocamlc -o ... -linkpkg -package .

>

In this case, the linking information will be taken from

CLASS="LITERAL"

>./META

>.

>

>

CLASS="NAVFOOTER"

>

ALIGN="LEFT"

WIDTH="100%">

SUMMARY="Footer navigation table"

WIDTH="100%"

BORDER="0"

CELLPADDING="0"

CELLSPACING="0"

>

>

WIDTH="33%"

ALIGN="left"

VALIGN="top"

>

HREF="x443.html"

ACCESSKEY="P"

>Prev

>

>

WIDTH="34%"

ALIGN="center"

VALIGN="top"

>

HREF="index.html"

ACCESSKEY="H"

>Home

>

>

WIDTH="33%"

ALIGN="right"

VALIGN="top"

>

HREF="x461.html"

ACCESSKEY="N"

>Next

>

>

>

>

WIDTH="33%"

ALIGN="left"

VALIGN="top"

>Why does findlib not automatically include the -custom option if

linked with C code?

>

WIDTH="34%"

ALIGN="center"

VALIGN="top"

>

HREF="c429.html"

ACCESSKEY="U"

>Up

>

>

WIDTH="33%"

ALIGN="right"

VALIGN="top"

>Does Findlib support camlp4?

>

>

>

>

>

>