> > I thought by default I didn't need to define SSL as libcurl by default will >> use Windows SSPI? >> > > No way
Lines 58 - 61 of Makefile.b32 : # By default SSPI support is enabled for BCC !ifndef DISABLE_SSPI DEFINES = $(DEFINES) -DUSE_WINDOWS_SSPI !endif Looks like maybe there should be a =+ in there somewhere I haven't followed this long thread, but you could try these too: > -DUSE_SCHANNEL -DUSE_WINDOWS_SSPI Perfect! That definitely cured my problem. Greatly appreciated. Also I would like to state that this mailing this is probably one of the most useful things I've ran into in a while regarding support / discussion for this extremely useful library. Regards, JT On Mon, Jun 2, 2014 at 12:52 PM, Gisle Vanem <gva...@yahoo.no> wrote: > "Jon Torrey" <ntox...@gmail.com> wrote: > > I thought by default I didn't need to define SSL as libcurl by default >> will >> use Windows SSPI? >> > > No way! > > > Anywho, I made the following change >> >> On line 56 of Makefile.b32 I have : >> >> DEFINES = -DNDEBUG -DWIN32 -DBUILDING_LIBCURL -DCURL_STATICLIB -USE_SSL >> >> Everything builds fine. >> >> Still throwing the same error. >> > > I haven't followed this long thread, but you could try these too: > -DUSE_SCHANNEL -DUSE_WINDOWS_SSPI > > I assume you don't want OpenSSL, but the Win-native SSPI stuff in > secur32.lib. > > --gv > > ------------------------------------------------------------------- > List admin: http://cool.haxx.se/list/listinfo/curl-library > Etiquette: http://curl.haxx.se/mail/etiquette.html >
------------------------------------------------------------------- List admin: http://cool.haxx.se/list/listinfo/curl-library Etiquette: http://curl.haxx.se/mail/etiquette.html
