Hmm... the plot thickens: the firewall seems to see that vibe is hosting a listen socket (asks if it should be allowed), but still nothing is able to connect to it.
Even this relatively simple code doesn't work...
import vibe.vibe;
import std.stdio;
int main(string[] argv)
{
setLogFile("vibe_log.txt", LogLevel.Trace);
listenTcp(80, (conn) {
writeln(conn.peerAddress());
} );
runEventLoop();
return 0;
}
Chrome will say "couldn't connect", nothing printed in console or log, etc.
I realize I'm using vibe in a sort of weird way, but I'd like to control the entry points and link it just as a library rather than using the surrounding build infrastructure. It seemed to be working fine before, but not anymore :(
So to be clear what I'm doing is...
1) using provided visual D project
2) adding "vibe.d" and a few missing files in templ to it
3) removing stream/stream from it to eliminate warning
4) removing VibeWin32Driver version from compile options
5) linking resulting library in with my code (for example, the above)
Is this supposed to work or am I bypassing too much of the infastructure? Is there a preferred way for me to accomplish what I'm trying to do? Am I just missing some sort of initialization function or similar maybe?