Add >VS2008 envvar

[mirh]

Idk about VS2017 then (which in other news also add native cmake support)

[bashbaug]

I think this is fine, but would it be even better to build using cmake instead of invoking nmake directly?

Then, the batch file could simply become:

set BUILD_DIR=build
set BIN_DIR=bin

mkdir %BUILD_DIR%
cd %BUILD_DIR%
cmake ../
cmake --build .
cd ..

[mirh]

Mh, well, that works too.
I wouldn't be sure about pros and cons of the thing though.
For example, a funny difference I noticed (aside from cmd spawning VS compiler logs, instead of a "gcc-like" progress screen) is that the exe manifest uses ' instead of " now.
This should be insignificant, but makes me wonder what's else.

[bashbaug]

Are the differences purely cosmetic? I can't think of any good reason why one method would be any more right than the other, just different.

To be clear, I'm OK with the proposed changes as-is, though it would be nice to avoid needing an update for each new VS version.

@kepatil any thoughts?

[kepatil]

Are the differences purely cosmetic? I can't think of any good reason why one method would be any more right than the other, just different.

To be clear, I'm OK with the proposed changes as-is, though it would be nice to avoid needing an update for each new VS version.

@kepatil any thoughts?

I think building using cmake as you suggested is better. I'll make that change.

[CLAassistant]

Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[bashbaug]

We've removed the batch files and switched entirely to a CMake build system in #61, so I am closing this pull request.