From: Alain Frisch <alain.frisch@lexifi.com>
To: David Allsopp <dra-news@metastack.com>, OCaml List <caml-list@inria.fr>
Subject: Re: [Caml-list] Building MSVC ports: coreutils link conflict
Date: Wed, 15 Jul 2015 13:40:58 +0200 [thread overview]
Message-ID: <55A646CA.8050605@lexifi.com> (raw)
In-Reply-To: <003401d0be52$320d6a00$96283e00$@metastack.com>
On 07/14/2015 06:28 PM, David Allsopp wrote:
> As far as I'm aware, when started in the usual way as a login shell,
> Cygwin's bash will always prefix PATH /usr/local/bin:/usr/bin:$PATH ... so I
> was surprised to find no mention of this issue in the build instructions -
> is it simply that everyone who builds the MSVC port just curses at this
> point, alters their PATH and carries on, or is there an alternate, better
> way of setting up the build environment?
FWIW, the way we (=LexiFi) work is that our .bashrc/.bash_profile
scripts are responsible for setting up the LIB and DIR env variables for
MSVC and prepending the correct directories in front of the PATH. (They
also define aliases to switch between the 32- and 64-bit toolchains.)
We don't rely on .bat files shipped by Microsoft. It's true that it had
become messy to support various versions of Visual Studio and of Windows
SDK, but we still prefer to know exactly how the environment is set up.
Alain
next prev parent reply other threads:[~2015-07-15 11:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-14 16:28 David Allsopp
2015-07-15 11:40 ` Alain Frisch [this message]
2015-07-17 15:42 ` David Allsopp
2015-07-17 17:12 ` Alain Frisch
2015-07-22 16:23 ` Damien Doligez
2015-07-22 16:34 ` David Allsopp
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=55A646CA.8050605@lexifi.com \
--to=alain.frisch@lexifi.com \
--cc=caml-list@inria.fr \
--cc=dra-news@metastack.com \
/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).