Browse thread
what's in the future for ocamlbuild?
[
Home
]
[ Index:
by date
|
by threads
]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
Date: | 2008-03-12 (17:16) |
From: | Erick Tryzelaar <idadesub@u...> |
Subject: | Re: [Caml-list] what's in the future for ocamlbuild? |
On Wed, Mar 12, 2008 at 2:14 AM, David Allsopp <dra-news@metastack.com> wrote: > When you say that it doesn't work with cmd.exe, do you mean that bash simply > needs to be in the PATH so that ocamlbuild can execute commands? The Win32 > port of make has the same requirement for sh.exe - I can't see how that's a > show-stopper for OCaml on Windows? The problem I ran into with this is that the felix language supports being built with visual studio, and the visual studio ocaml version. This means that the end user doesn't need anything else to compile, and our build system (is supposed to) be able to run in cmd.exe with our custom python build system. In this setup we can't really justify using ocamlbuild since our crusty build system is actually more compatible. Now we could add a dependency on cygwin, but cygwin implies so much more than just bash that it might not be worth changing something that works (poorly) right now.