On Thursday, 7 April 2016 at 13:40:17 UTC, Rene Zwanenburg wrote:
On Thursday, 7 April 2016 at 13:25:29 UTC, Jerry wrote:
I generated a visuald project and tried that. Now suddenly it
is working as expected. So I guess it's a bug in dub.
That's possible of course, but I'd expect something so
On Thursday, 7 April 2016 at 13:40:17 UTC, Rene Zwanenburg wrote:
That's possible of course, but I'd expect something so
fundamental breaking to be noticed sooner.
Just to make sure, could you run dub with --force to rule out
that it's picking up some stale object files from somewhere?
And
On Thursday, 7 April 2016 at 13:25:29 UTC, Jerry wrote:
I generated a visuald project and tried that. Now suddenly it
is working as expected. So I guess it's a bug in dub.
That's possible of course, but I'd expect something so
fundamental breaking to be noticed sooner.
Just to make sure,
On Thursday, 7 April 2016 at 13:17:32 UTC, Jerry wrote:
On Thursday, 7 April 2016 at 13:13:14 UTC, Suliman wrote:
dup upgdare
dub upgdare
Tried that. I have to say this is odd.
I generated a visuald project and tried that. Now suddenly it is
working as expected. So I guess it's a bug in
dup upgdare
dub upgdare
On Thursday, 7 April 2016 at 13:13:14 UTC, Suliman wrote:
dup upgdare
dub upgdare
Tried that. I have to say this is odd.
On Thursday, 7 April 2016 at 12:01:59 UTC, Jerry wrote:
Hello, I am trying to use vibe with DMD 2.67, dub and windows.
But in some way the default main function is sneaking in my
build system even when I'm using VibeCustomMain version.
Main file:
import vibe.vibe;
void main() {
Hello, I am trying to use vibe with DMD 2.67, dub and windows.
But in some way the default main function is sneaking in my build
system even when I'm using VibeCustomMain version.
Main file:
import vibe.vibe;
void main() {
writeln("Hello world");
}
And dub file:
{
"targetType":
