On Sat, Jan 26, 2002 at 07:59:21AM +0900, Jacques Garrigue wrote:
> From: Sven <luther@dpt-info.u-strasbg.fr>
> 
> > > > creating cache ./config.cache
> > > > checking your compiler package... version 3.04 at /usr/lib/ocaml
> > > 
> > > Thus. That's the directory where ocaml has installed its library files (It
> > > is bound to CAMLDIR in Makefile.config of advi).  Thus, ocaml should have
> > > copied the files (mlvalues.h, alloc.h, etc.)  in the subdirectory
> > > $CAMLDIR/caml.
> > 
> > No, the include files are in /usr/include/caml on a debian system as the FHS
> > mandates.
> 
> That doesn't seem to be a good thing to do.
> Objective Caml has only one standard: a unique distribution. If you
> start to mess around with the directories, this is not very helpful
> for anybody. There is no way a library developper can find the path of
> the caml include files, other than expecting them to be in the
> standard place, under the library directory. Usually you just call
> them by <caml/mlvalues.h>, and your scheme with still work, but if

Well, yes, that is the intention.

I think there is a symlink from the old place to there. 

> anybody chooses to do -I`ocaml -where`/caml , which is supposed to be
> correct, then it breaks.
> And what are you doing with caml-light header files ?

???

> By the way, FHS or not, glib puts parts of its headers in
> /usr/local/lib/grealizelib/include, which seems to be pretty similar to what
> ocaml does (I noticed that righteous FreeBSD mainteners are moving them
> back to /usr/local/include/glib12...)

You are speaking about  /usr/lib/glib/include/glibconfig.h ?

I don't think this is a header that is supposed to be used for developpment,
is it, while the caml header belong under /usr/include, since they are used in
standard developpment, and you do a #include <caml/mlvalues.h> for them.

> And these headers will only be used by ocaml programs, this is not
> just a standard C library.

Any developper wanting to use C code will need those, thus they go into the
right place, and no need for an additional -I`ocaml -where`/caml, and it will
not break, since the files are where they are supposed to be, in /usr/include.

Just because you are used to doing it like that, doesn't make it the right way
of doing things.

But still, if you have very convincing arguments, i may consider them, i have
not seen such upto now.

Friendly,

Sven Luther
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs  FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr  Archives: http://caml.inria.fr