Win64 libevent2 .lib and .dll missing

[ColdenCullen]

event2.lib and libevent.dll are both in lib/win-1386, but not lib/win-amd64 folder. This leads to an error when building a Windows application with --arch=x86_64.

[dariusc93]

I believe that dmd for windows is only 32bit. I could be wrong

[ColdenCullen]

I don't believe that to be the case, it still takes the -m64 switch.

[etcimon]

Yes, you can still compile for x64, the only difference is that DMD 64bit would allow the compiler to use more than 4gb of memory at compile-time, which may be required for very large libraries or high use of CTFE.

I think the libevent dll would have to be compiled for win x64, but the .lib file can stay the same.

You would need Visual Studio and CMake.

https://github.com/libevent/libevent/

cmake . -G"Visual Studio 11 Win64"

I haven't tried this though. I might be easier to use my fork with the native events after all, which would build on win64 with dub build --arch=x86_64, it should end up being better and faster, although it's not tested on a big scale yet. It's only tested with win32/linux64/osx64, you'd have to let me know if it works with win64, it might be a bit more lasting to fix it if anything because I think native D events is the way to go.

[Kelet]

With the x86_64-w64-mingw32 build of GDC, I get

gdc: error: C:\Users\Kelet\AppData\Roaming\dub\packages\vibe-d-0.7.23\lib\win-amd64\event2.lib: No such file or directory

Seems to be the same issue. Compiled with dub build --compiler=gdc.

[s-ludwig]

Since the future path will be to directly talk to the OS APIs without a C library in-between (as libasync does), it doesn't make sense to invest time building a Win64 version of libevent anymore (requires setting up a custom makefile/VS project). I've instead disabled the libevent configuration on Win64 now.

[etcimon]

Will you be developing your own library or are we still looking at making libasync default in the future?