On 2016-01-07 15:35:24 +0000, Robert M. Münch said:
When I build for Windows, it seems that the "libevent" driver is used.
I can see that there is a "Win32EventDriver" which setups a GUI message
loop as well. How can I use this driver instead of the "libevent" one?
Ok, after fiddling around for quite some while, here is the workaround:
1. I made a copy of vibe to manually build the "win32" version using:
dub -verison=win32
2. To compile it without errors, I had to comment quite some
conflicting declarations and had to remove one ".ptr"
3. Spotting "By default, the first configuration that matches the
target type and build platform is selected automatically..." in the DUB
json docs i moved the "win32" configuration to the top.
4. Then building my actual project the my wanted configuration "win32"
was used.
So, I think DUB has a bug as the above rule can't be overwritten with:
"subConfigurations": {
"vide-d": "win32"
}
--
Robert M. Münch
http://www.saphirion.com
smarter | better | faster
