Building on windows, tutorial and suggestions about curl-rust

[alexcrichton]

Yeah unfortunately building this crate for the x86_64-pc-windows-gnu target requires building it in a MSYS environment (as do almost all other C projects). If you build for x86_64-pc-windows-msvc, however, it should in theory work so long as VS is installed.

I'd be more than ok updating the docs, here, though! I know this tends to be a pain point with Windows unfortunately :(

[waynenilsen]

I installed msys via MinGW but cargo build seems to be hung. I'm going to let it run overnight just to be sure.

[waynenilsen]

Yes, it turns out that cargo build hung with MSYS environment installed. No response after over 12 hours.

[alexcrichton]

Weird! I vaguely remember running into that but I don't remember figuring out why. Can you take a look and see which processes are hung?

[waynenilsen]

The best that I could tell it was hung on make but not sure what within make was hung up.. I will try again when I get back to the machine tomorrow

[waynenilsen]

I ran again this morning and got checking size of void*... 0 configure: error: cannot find out size of void*. So I did some googling around and found out that maybe it wants vcvars so I ran that. It does seem to be running gcc now which is a good sign. Not sure how long I can expect this to take.

It has been running for about an hour now, make is pinning a core, not sure if it is stuck in a loop or actually doing something.

[alexcrichton]

Hm vcvars should only be necessary for MSVC targets which don't use gcc, so that's odd! I've found the configure script to take forever on Windows, but an hour is certainly a bit excessive... Can you get a dump of the process running to see where it's at?

[waynenilsen]

make is still pinning a core. Not sure what you mean about "get a dump of the process running" how would I go about doing that? Some tool?

[waynenilsen]

It seems (I didn't notice any error messages) that I was able to successfully run sh configure then make from the curl-sys\curl directory. I saw that you had some extra flags in your build.rs file but I did not go through the logic and figure out exactly which flags to use.

[alexcrichton]

yeah sometimes calling shell scripts from Rust is subtly different than calling them from the shell itself, and I've never really quite figured out what the problem is...

[mitsuhiko]

I think one thing that should be documented is that it only builds with VS2015 or later.

[alexcrichton]

@mitsuhiko oh dear that's not good! It's certainly intended to build with more than that, do you have a copy of the error on previous versions?

[mitsuhiko]

@alexcrichton i'm travelling without windows machine right now and probably won't be at my desktop for a month. I think it complained about undefined symbols from libc. I tried with I believe 2013 before that.

[alexcrichton]

@mitsuhiko I've now merged #119 which I think uses VS 2013, but it seems to work?

[blakehawkins]

Hi,

On a fresh install of msys2 (windows with -gnu toolchain), building this package has abysmally poor debug info - e.g. https://gist.github.com/anonymous/eb7c2e4904687b374154f19e14d6eda5

I found out that you need to be able to build libcurl from source for this package to build. By building libcurl from source (which has better debug info) I managed to make a list of necessary packages:

autoconf
git
libcurl-devel
libcurl
man
curl
vim
binutils
gcc
make
automake
libtool
pkg-config

Hopefully nothing is missing.

[alexcrichton]

I'm going to close this since I don't think this is as relevant now as it used to be.