I'm building on Win7 64-bit. Tomorrow, at work, I can try again on a Win7
32-bit, and see if that makes a difference.
Version [ee46563cbd] built without any errors, and apparently has SSL
support (much larger file size, and an attempt to connect to an HTTPS server
did not produce errors about missing SSL support).
So, the question is, if that older version relies on pre-built SSL
libraries, where does it find them? And, why can't I do the same (use these
pre-built SSL libraries) when building the latest trunk version?
-----Original Message-----
From: Joe Mistachkin
Sent: Sunday, September 28, 2014 10:44 PM
To: 'Fossil SCM user's discussion'
Subject: Re: [fossil-users] Compilation with SSL option fails on Win7
to...@acm.org wrote:
When I tried with an earlier version [ee46563cbd], it worked OK. Since
the
latest trunk fails consistently (regardless of Perl version used),
something
must have broken sometime in between these two check-ins.
That version ([ee46563cbd]) makes no attempt to automatically build OpenSSL;
therefore, it relies on the OpenSSL libraries already being built.
I'm unable to replicate this issue here locally and I just built an SSL
enabled
Fossil binary here with MSVC (yesterday).
Are you building for x86 or x64? I suspect the current "Makefile.msc" will
only
work for x86 builds. I'll look into fixing that.
--
Joe Mistachkin
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
