On 1/13/16 1:51 PM, Erik Joelsson wrote:
For your build to pick up nmake from some other VS installation means
you must have that VS installation in your path. Normally, only the
devkit bin dirs will be in the path if you start with a clean
environment. We have simply not encountered that befor
For your build to pick up nmake from some other VS installation means
you must have that VS installation in your path. Normally, only the
devkit bin dirs will be in the path if you start with a clean
environment. We have simply not encountered that before, but it is
definitely a bug. However, t
[This is likely a bug, but thought I'd ask it as a question first].
Windows devkits contain an nmake.exe, but the configure and make scripts
do not define and consistently use an NMAKE variable to make sure the
devkit version is used, as many other commands do.
I had assumed that my builds we