Re: [Caml-list] OCaml script on windows (was Re: [ANN] React 1.0.0)

[Adrien Nader <adrien@notk.org>]

On Sat, Apr 12, 2014, Adrien Nader wrote:
> On Fri, Apr 11, 2014, David Allsopp wrote:
> > Daniel Bünzli wrote:
> > > Le vendredi, 11 avril 2014 à 18:32, Daniel Bünzli a écrit :
> > > 
> > > > Ok thanks for the info. Will implement that once I get some free time in
> > > my hands.
> > > 
> > > I may also take that as an opportunity to rewrite these *trivial* shell
> > > scripts in ocaml for improving windows compatibility. Here are a few
> > > questions to the list:
> > > 
> > > 1) What should I use for #!,  /usr/bin/env ocaml  ? And what will windows
> > > do with that ?
> > 
> > Windows can't do anything with that. However, most people compiling OCaml packages on Windows expect to use bash (either from Cygwin or MSYS), where the scripts would run as on Unix. Are you sure that Windows compatibility is already a problem?
> > 
> > > 2) The only OS related things I do is write the .install file and invoke
> > > ocamlbuild once with all the targets that need to be build. Is Sys.command
> > > enough for that ? and is the invocation syntax identical ?
> > 
> > As long as you don't do anything exotic with command line parameters (quoting can be very weird for the Windows command processor, cmd, which is what Sys.command uses) then yes, Sys.command will be fine, and the same as on Unix.
> > 
> > In passing, it does have to be said that getting Windows support automatically from your build system is something that OASIS does...
> 
> Actually you can do OCaml using the Mingw port while not using Cygwin or
> Msys except for an implementation issue in ocaml/ocamlbuild because of
> Windows awful "shell" escaping. It is not very difficult to solve (and
> ocaml from svn is heading that way).
> 

Sorry, forgot to mention that this included building software through
oasis and ocamlbuild. From configure of libraries to build the final
executable. And that has been the case for 3 years at least.

-- 
Adrien Nader