caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Lionel Fourquaux" <lionel.fourquaux@wanadoo.fr>
To: <caml-list@inria.fr>
Subject: RE: [Caml-list] minor suggestions for Win32 port
Date: Sat, 7 Apr 2001 12:14:53 +0200	[thread overview]
Message-ID: <000301c0bf4b$9a836a50$cb63f8c1@wfr01946> (raw)



> -----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


             reply	other threads:[~2001-04-07 10:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-07 10:14 Lionel Fourquaux [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-04-07  3:14 Chris Hecker
2001-04-10  8:48 ` Xavier Leroy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='000301c0bf4b$9a836a50$cb63f8c1@wfr01946' \
    --to=lionel.fourquaux@wanadoo.fr \
    --cc=caml-list@inria.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).