Thanks for the reply!
On Fri, 15 Apr 2016 08:39:02 GMT, Sönke Ludwig wrote:
I think you are hitting a bug in DUB that was recently fixed. Can you try with the latest alpha version or GIT master?
The alpha still has the same issue (and for some reason has a long delay before starting to do work):
32-bit build ("dub" with no arguments) - note libevent still referenced in vibe-d:core
vibe-d:utils 0.7.28: target for configuration "library" is up to date.
vibe-d:data 0.7.28: target for configuration "library" is up to date.
vibe-d:core 0.7.28: target for configuration "libevent" is up to date.
vibe-d:http 0.7.28: target for configuration "library" is up to date.
vibe-d:diet 0.7.28: target for configuration "library" is up to date.
vibe-d:mail 0.7.28: target for configuration "library" is up to date.
vibe-d:mongodb 0.7.28: target for configuration "library" is up to date.
vibe-d:redis 0.7.28: target for configuration "library" is up to date.
vibe-d:web 0.7.28: target for configuration "library" is up to date.
vibe-d 0.7.28: target for configuration "libasync" is up to date.
steamproxyvibed ~master: building configuration "application"...
Linking...
64-bit build (dub --arch=x86_64):
Performing "debug" build using dmd for x86_64.
vibe-d:utils 0.7.28: target for configuration "library" is up to date.
vibe-d:data 0.7.28: target for configuration "library" is up to date.
vibe-d:core 0.7.28: building configuration "libevent"...
Error: Error reading file 'blahblah\vibe-d-0.7.28\lib\win-amd64\event2.lib'
dmd failed with exit code 1.
I'll give master a try when I get the chance just in case the fix wasn't in the alpha build (0.9.25-alpha.1, built on Apr 5 2016).
You can generate a 64-bit VisualD solution using
dub generate visuald --arch=x86_64.
Oh cool, I'll give that a shot once I get the build working.
Yeah, it's really time to have a linker in the standard distribution that can link 64-bit object files. That's the only thing holding back a 64-bit default build.
Ah, interesting. Wasn't aware of there being a linker issue.