On 8/5/2014 10:20 PM, Dicebot wrote:
On Tuesday, 5 August 2014 at 21:48:40 UTC, Johannes Blume wrote:
Normally, you just execute vcvars32.bat/vcvars64.bat before doing
anything from the command line and you are set. Even make scripts I
created five years ago for VS2008 still work without a hitch on VS2013
without any manual PATH trickery. The detailed directory layout of VS
is not something makefiles are supposed to know about.
If it is only reliable way to get environment prepared, is there any
reason we shouldn't require running `make -f win*.mak` from it instead
of trying to configure all paths manually?
I call into a batch file that runs that batch file from my shell script,
which then calls msbuild to actually build DMD.
