Hello,

> People seem to have missed the actual problem I have posed: what is
> the most convenient and hassle-free mechanism for transporting
> information produced by running ./configure to O'Caml source code?
> Such features include directory prefixes, auxiliary program paths,
> various constants, features {en,dis}abled with --enable-X and alike.
> I'm *NOT* trying to use the preprocessor for any weird syntactic
> abstractions or anything of that kind.
> 
> >From the answers I've seen so far, no common, truly convenient and
> completely hassle-free mechanism exists.  Hopefully this problem will
> find a clean solution some day.  In the meantime I can live with -pp cpp
> and bite a few small kludges, like adding a (*don't remove me*) ;-)

Do not AC_SUBST(VAR) and AC_OUTPUT(config.ml) solve your problem ?
You can find such examples of the combination of configure script 
and .ml files like camlimages or advi:

	http://pauillac.inria.fr/camlimages/
	http://pauillac.inria.fr/advi/

Hopes this helps.

Jun
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners