On Sat, 16 Jul 2016 20:45:35 +0200, Sönke Ludwig wrote:

What are exactly the effects that you observed? Unless the
VibeDefaultMain version identifier is defined, vibe.d's main()
function shouldn't be included.

However, what will always be included is the initialization code that
sets up a per-thread event driver, and - you will probably want to
disable that by callingvibe.core.core.disableDefaultSignalHandlers()
at the start of main() - a signal handler for Ctrl+C and some others.

The signal functionality is planned to eventually be also handled by the
event loop in the future, so that this step will become mostly obsolete.

Oops. I did have a VibeDefaultMain version -- I misunderstood the build procedure and built a vibe.d application in error.

I've removed that version and everything works as expected now. Thanks

Paul