From the error message you get, it looks like the linker is trying to
link your 64-bit DLL with the previously built 32-bit obj files. Did
you try an 'nmake clean' before making the 64-bit build, or manually
cleaning the object files out?

I agree with Steve that the Visual Studio project files are the
simplest to work with, and they do contain configurations for building
64-bit DLLs. It's what I use, and I have not had any problems
building that way, though I build the static library. If you don't
find the configuration you need, you can create your own ones, by
tweaking an existing one (I wouldn't try to create one from scratch).
You can build with the VS project files from the command-line.

HTH,
  - Henri

On Tue, Apr 5, 2016 at 3:24 PM, Patrick Seiter <patrick.seiter_at_gmail.com> wrote:
> Hello everyone,
>
> After many Google searches and many attempts at building, I am officially
> flummoxed trying to build 64-bit libcurl for Windows. I finished the code
> for my project months ago, but I need to distribute both 32 and 64-bit
> copies for release. Here's the StackOverflow question I made on the issue:
>
> http://stackoverflow.com/questions/35398914/how-do-i-build-libcurl-for-64-bit-windows-in-using-visual-studio-2010
>
> I don't want to spam copypasta for my first post to the reading list, but I
> can copy output as needed here. Eventually I'll want to build OpenSSL and
> zlib into this, but one step at a time.
>
> Sincerely,
> Patrick Seiter /zaɪ tɛr/
>
> -------------------------------------------------------------------
> List admin: https://cool.haxx.se/list/listinfo/curl-library
> Etiquette: https://curl.haxx.se/mail/etiquette.html

-------------------------------------------------------------------
List admin: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.haxx.se/mail/etiquette.html
Received on 2016-04-06