Re: [Caml-list] One build system to rule them all?

[Adrien Nader <adrien@notk.org>]

On that topic, I've recently cleaned up my build scripts for use in
win-builds.org (which should see a release in a few weeks hopefully).

For the oasis case, I only set OCAMLFIND_CONF to a file which contains:
  destdir="/opt/windows_32/lib/ocaml/site-lib"
  path="/opt/windows_32/lib/ocaml/site-lib"
  # Where the cross-compiler is installed
  stdlib="/opt/cross_toolchain_32/lib/ocaml"
  # I have this variable but I only do native compile so I don't
  # actually use it
  ldconf="/opt/windows_32/lib/ocaml/ld.conf"
  # Below, the .exe versions are the cross-compiler binaries; their
  # proper name should be something like "i686-w64-mingw32-ocamlopt.opt"
  # instead of "ocamlopt.opt.exe"
  ocamlc="ocamlc.opt.exe"
  ocamlopt="ocamlopt.opt.exe"
  # Btw, that one is needed too for C stubs libraries and hasn't been in
  # oasis since the beginning; only something like >= 0.4
  ocamlmklib="ocamlmklib.exe"
  # And these are from the native toolchain, not the cross one (with my
  # most recent patches, these are cross-compiled and will be windows
  # executables)
  ocamldep="ocamldep.opt"
  ocamldoc="ocamldoc.opt"

Then, my oasis configure invocation looks like:
  ocaml setup.ml -configure --prefix "/${PREFIX}" --mandir "/${PREFIX}/man" --override ext_dll .dll

Very simple in practice.

I also need to mention that this relies on oasis not using all the
values it finds during configure. For instance it finds the host C
compiler but it'll let ocamlbuild and in turn ocamlc call the C
compiler.

-- 
Adrien Nader