Version franēaise
Home     About     Download     Resources     Contact us    

This site is updated infrequently. For up-to-date information, please visit the new OCaml website at

Browse thread
[Caml-list] Alternative proposal: COAN
[ Home ] [ Index: by date | by threads ]
[ Search: ]

[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
Date: 2003-02-28 (14:22)
From: Jean-Christophe Filliatre <Jean-Christophe.Filliatre@l...>
Subject: Re: [Caml-list] Alternative proposal: COAN

 > I know i am repeating myself, but please consider adding the following
 > points also :

Sorry, I forgot to comment on these points :

 >   o support the DESTDIR prefix to your install directory. distribution
 >     need to install into different directories than the ones the
 >     package will unpack into.

A  ./configure script  accepts a  --prefix option,  or  more precisely
--libdir, --bindir,  etc, setting some  variables at the  beginning of
the generated Makefile. Additionally,  it sets other variables such as
OCAMLLIB for  the ocaml standard  library place, etc.  Overiding these
variables when  compiling is possible  (make OCAMLLIB=... LIBDIR=...),
and thus using DESTDIR does not need changing the Makefile at all.

 >   o support separate compilation for bytecode and nativecode. I build
 >     bytecode versions of my packages on my i386 box alongside the native
 >     versions. The bytecode package is arch: all, and will be
 >     installeable on every arch, including slower arches like m68k, where
 >     building huge ocaml bytecode executables is a waste of time if it
 >     can be done quicker on my box.

The  / I provide  on my web  page also tackle
this  issue. The  makefile actually  contains two  targets  "byte" and
"opt"  for  bytecode  and  nativecode compilation.  The  "./configure"
script   determines  automatically   if   nativecode  compilation   is
supported, so that  "make" is doing the best  it can (always bytecode,
and nativecode when available). But  "make byte" and "make opt" can be
invoked  specifically, to  do one  particular  compilation. Similarly,
"make install-byte" or "make install-opt" can be invoked specifically.

Jean-Christophe Filliātre (

To unsubscribe, mail Archives:
Bug reports: FAQ:
Beginner's list: