Browse thread
Re: [Caml-list] MingW compiler (!) and Ocaml for Windows
-
Dawid Toton
- Markus E L
[
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: | -- (:) |
| From: | Leypold Software-Dienstleistungen <kontakt@m...> |
| Subject: | Re: [Caml-list] MingW compiler (!) and Ocaml for Windows |
kyra wrote: > Markus E L wrote: >> OK. So it seems, @responsefile is only used sometimes, not >> always. That makes it difficult to see wether the situation actually >> persists. When was that you got the problem and (if you remember) with >> which version (approximately at least) of MSYS/MingW). As I said, I'd >> be interested in the long run to get a distribution of OCaml that is >> independent of Cygwin and Visual C++. > > @responsefile is only used when command-line length exceeds 256 (see > code in utils/ccomp.ml). > > @responsefile idiosyncrasy is a problem of MSYS only (not MinGW). Then this is probably not the problem from http://caml.inria.fr/pub/distrib/ocaml-3.09/notes/README.win32 I'm referring to? I'm a bit confused here, because, AFAI understand, Ocaml only uses the C-compiler as a backend and that C-Compiler comes from MingW? So where does MSYS come in? Or did I get everything wrong and it is OCaml that doesn't understand the @responsefile generated by MSYS tools? In this case, can anybody see a reason why it should not be possible to use the MingW compilers as a backend to OCaml and compile from CMD.EXE? Regards -- Markus