[PATCH] [DOCS] How to Setup a Windows Builder
rfoos at codeaurora.org
Wed Nov 13 17:25:37 PST 2013
On 11/13/2013 06:01 PM, Sean Silva wrote:
> On Wed, Nov 13, 2013 at 6:22 PM, Robinson, Paul
> <Paul_Robinson at playstation.sony.com
> <mailto:Paul_Robinson at playstation.sony.com>> wrote:
> Very much a side comment:
> > Also, AFAIK almost all LLVM MSVC users are running 12.
> Speaking as one who isn't, I'm not so sure about that.
> Our builders are using 2010 and while we're aware of the
> movement to require 2012, we're not there yet.
> That comment was mostly in the spirit of "if you had to choose a
> single MSVC version to describe, 2012 is likely to be the better
> choice". It is a fact that there are still developers using 2010 and
> until the upcoming policy change to require 2012 I expect that to
> remain true.
That actually brings up a good point. We have build machines with
multiple versions of MSVC.
You can check what is installed by the vs-comntools, and use that
variable as a path to invoke the vsvars32.bat of the version you want.
(VS100COMNTOOLS, VS90COMNTOOLS, VS80COMNTOOLS, etc).
That might be worth a sentence in the instructions as multiple MSVC's is
a useful configuration for a build machine. (We also have multiple
MinGW's, and specific GCC versions are part of some builds).
A build machine then could have multiple versions of MSVC installed to
allow testing a move from 2010 to 2012, and to 2013.
> llvm-commits mailing list
> llvm-commits at cs.uiuc.edu
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the llvm-commits