Browse thread
RE: [Caml-list] minor suggestions for Win32 port
- Lionel Fourquaux
[
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: | 2001-04-07 (10:24) |
From: | Lionel Fourquaux <lionel.fourquaux@w...> |
Subject: | RE: [Caml-list] minor suggestions for Win32 port |
> -----Message d'origine----- > De : owner-caml-list@pauillac.inria.fr > [mailto:owner-caml-list@pauillac.inria.fr]De la part de Chris Hecker > Envoyé : samedi 7 avril 2001 05:15 > À : caml-list@inria.fr > Objet : [Caml-list] minor suggestions for Win32 port > > > > Here are some minor suggestions and feature requests I've come up with > while working with the Win32 MSVC ocaml port (3.00 and 3.01). > > 1. If you're using the MSVC cl.exe compiler, it sends linker command > line parameters in a relatively broken way, so this affects the > -cclib switch. Basically, to pass parms to link.exe from cl.exe, > you say /link [and then all the parms], so you can't have any > compiler flags after linker flags. You also don't know if a > library you're building is going to be linked with other libraries > with -cclib parms, so you have to do this: -cclib "/link /debug > /whatever", but then you get duped parms to the linker and it > complains, etc. It's basically hard to get it exactly right. The > right thing to do here is have the msvc driver know this, and > store the cclib parms up, sort/uniq them, and then put them after > a /link itself. > What about calling link.exe directly? ------------------- To unsubscribe, mail caml-list-request@inria.fr. Archives: http://caml.inria.fr