On 24 October 2016 at 13:08, Warren Young <w...@etr-usa.com> wrote: > On Oct 24, 2016, at 2:03 PM, jungle Boogie <jungleboog...@gmail.com> wrote: >> >> On 24 October 2016 at 11:44, jungle Boogie <jungleboog...@gmail.com> wrote: >>> Building zlib from "..\compat\zlib"... >>> >>> cl -c -D_CRT_SECURE_NO_DEPRECATE -D_CRT_NONSTDC_NO_DEPRECATE >>> -nologo -MD -W3 -O2 -Oy- -Zi -Fd"zlib" .\adler32.c >>> 'cl' is not recognized as an internal or external command, >> >> Is what's above something I can work around to build successfully? > > ‘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 had put this big ugly thing in my path thinking it had all the toolchain necessary but it looks like it still failed. C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin Launching Visual Studio Command Prompt (2010) directly did get the build working. Thanks for the pointers, Warren! -- ------- inum: 883510009027723 sip: jungleboo...@sip2sip.info _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
