On 10/5/2016 3:27 PM, Richard Hipp wrote:
On 10/5/16, Ross Berteig <[email protected]> wrote:
Note that building for 64-bit needs something trickier than just
following that recipe from a 64-bit VisualStudio prompt.
Really?  Because just typing "nmake /f makefile.msc" from a 64-bit
VisualStudio prompt works fine for me on Windows10 with VS2012.

I have VS2010 installed here. It is possible I was fooled by not having a clean enough workspace.

Certainly, having zlib already built by a previous 32-bit compile wasn't helping. I tried to work around that by also setting FOSSIL_ENABLE_MINIZ=1 which did allow a clean compile and link. The resulting fossil.exe ran, at least fossil version -v worked. I did not run the test suite.

But handing it to DEPENDS.EXE to see what DLLs it was really linked against showed a mix of 32-bit and 64-bit DLLs. That might be a red herring, and does seem odd to me given that the program does run at all.

I certainly can try running the test suite over that fossil, and see what happens. I'll try that later tonight and report back.

--
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

Reply via email to