On 10/24/2016 2:12 PM, jungle Boogie wrote:
On 24 October 2016 at 13:08, Warren Young <[email protected]> wrote:
‘cl’ and related tools are not in the PATH after installing Visual
Studio. If you look in the Start Menu folder for Visual Studio, you
will find something like “VS2015 x86 Native Tools Command Prompt.”
Running nmake under that should succeed, at least with this C99 fix
in place.
....
SUCCESS!
....
I think MS gave up on putting the VS tool chain in the PATH by default
when they started delivering both 32-bit and 64-bit toolchains. If you
look in vcvarsall.bat, you'll see that the full environment it needs is
more complicated than just the PATH, and looking in the nest of batch
files now, it is more complicated than I recalled.
As an embedded developer with many different compiler toolchains
crossing my desk, I am very happy to see that from them. Back in the
day, they used to insist on setting PATH, and then adding INCLUDE and
LIB which often messed with other compilers, even other compilers
targeting Windows let alone cross compilers.
--
Ross Berteig [email protected]
Cheshire Engineering Corp. http://www.CheshireEng.com/
+1 626 303 1602
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
