On Mon, 17 Feb 2014 18:02:02 GMT, Matthew Fong wrote:
I did a few more tests. Here are my findings:
dub does correctly set the -version=VibeWin32Driver flag for dmd and -m64, so that should be fine.
when it comes to the linking stage though, it still instructs the compiler to link in the non-existen libevent file.
So I wondered why that would be the case and indeed I found it also passes -version=VibeLibeventDriver to dmd. So somehow it must think I specified that too. (which I didn't - at least not in my local package.json).
Is there any other files that dub checks for for these version specifiers? Some files that I might have changed (I can't remember doing so, but I dont want to rule out the possibility)?
Here is my complete dub output on pastebin (since its too long otherwise):
http://pastebin.com/uiUU3BPdI hope that helps diagnosing the problem
Oh sorry, I completely missed something. Selecting the driver must be done by choosing a different configuration instead of manually specifying a version constant:
{
...
"subConfigurations": {
"vibe-d": "win32"
},
"versions": ["VibeDefaultMain"]
}
This will use the correct linker settings. Have a look at vibe.d's package.json to see how this is organized.