www.digitalmars.com         C & C++   DMDScript  

digitalmars.D.learn - dub generate visuald

reply Tofu Ninja <joeyemmons yahoo.com> writes:
I am  not sure what changed but I can no longer build using 
visuald after generating from dub. When I try to build from 
visual studio I get the following error

LINK : warning LNK4001: no object files specified; libraries used
LINK : warning LNK4068: /MACHINE not specified; defaulting to X86
LINK : fatal error LNK1561: entry point must be defined

I did update visuald recently so I suppose that's what caused it. 
Updated dub to 1.0 trying to fix this. Anyone else get this, any 
solution. I can build directly from dub with no problem, but 
building from VS gives that error.
Sep 05 2016
next sibling parent reply Guillaume Piolat <first.last gmail.com> writes:
On Monday, 5 September 2016 at 17:25:45 UTC, Tofu Ninja wrote:
 I can build directly from dub with no problem, but building 
 from VS gives that error.
Building with dub uses the dmd settings in sc.ini Building with VisualD can override those settings.
Sep 05 2016
parent Tofu Ninja <joeyemmons yahoo.com> writes:
On Monday, 5 September 2016 at 18:22:02 UTC, Guillaume Piolat 
wrote:
 On Monday, 5 September 2016 at 17:25:45 UTC, Tofu Ninja wrote:
 I can build directly from dub with no problem, but building 
 from VS gives that error.
Building with dub uses the dmd settings in sc.ini Building with VisualD can override those settings.
There is an option to disable that in the visuald settings, but that does not seem to change anything.
Sep 05 2016
prev sibling parent reply Tofu Ninja <joeyemmons yahoo.com> writes:
On Monday, 5 September 2016 at 17:25:45 UTC, Tofu Ninja wrote:
 I am  not sure what changed but I can no longer build using 
 visuald after generating from dub. When I try to build from 
 visual studio I get the following error

 LINK : warning LNK4001: no object files specified; libraries 
 used
 LINK : warning LNK4068: /MACHINE not specified; defaulting to 
 X86
 LINK : fatal error LNK1561: entry point must be defined

 I did update visuald recently so I suppose that's what caused 
 it. Updated dub to 1.0 trying to fix this. Anyone else get 
 this, any solution. I can build directly from dub with no 
 problem, but building from VS gives that error.
I moved my project to a folder that has no spaces in the path, which has changed the error. Now I get: core.exception.RangeError pipedmd(286): Range violation
Sep 05 2016
parent Tofu Ninja <joeyemmons yahoo.com> writes:
On Monday, 5 September 2016 at 19:03:00 UTC, Tofu Ninja wrote:
 On Monday, 5 September 2016 at 17:25:45 UTC, Tofu Ninja wrote:
 I am  not sure what changed but I can no longer build using 
 visuald after generating from dub. When I try to build from 
 visual studio I get the following error

 LINK : warning LNK4001: no object files specified; libraries 
 used
 LINK : warning LNK4068: /MACHINE not specified; defaulting to 
 X86
 LINK : fatal error LNK1561: entry point must be defined

 I did update visuald recently so I suppose that's what caused 
 it. Updated dub to 1.0 trying to fix this. Anyone else get 
 this, any solution. I can build directly from dub with no 
 problem, but building from VS gives that error.
I moved my project to a folder that has no spaces in the path, which has changed the error. Now I get: core.exception.RangeError pipedmd(286): Range violation
https://issues.dlang.org/show_bug.cgi?id=15606 Ugggg.... it seems that bug has been in visuald for months now... and people wonder why D isn't popular... shit ain't useable.
Sep 05 2016