• John Chapman (11/11) Sep 20 2018 When I try to build within Visual D, I get the following error:
• Rainer Schuetze (7/19) Sep 22 2018 I guess you are using the VC-projects in VS2017. In that case the Visual...
• John Chapman (7/15) Oct 10 2018 Thanks - that worked.
• Rainer Schuetze (4/21) Oct 10 2018 Please try the latest beta, there has been a bug fix exactly for that

John Chapman <johnch_atms hotmail.com> writes:

When I try to build within Visual D, I get the following error:

LINK : fatal error LNK1104: cannot open file 'phobos64.lib'

I've added the path to the lib64 folder in the "DMD directories > 
Library paths" option and verified that the path to the linker is 
correct.

When I change to a Win32 configuration, it complains it can't 
open 'phobos32mscoff.lib' (even if I add the lib32coff folder to 
the path).

If I build on the command line everything works fine. Does anyone 
have any suggestion before I resort to using makefiles instead? 
Thanks.

Rainer Schuetze <r.sagitario gmx.de> writes:

On 20/09/2018 14:17, John Chapman wrote:
 When I try to build within Visual D, I get the following error:
 
 LINK : fatal error LNK1104: cannot open file 'phobos64.lib'
 
 I've added the path to the lib64 folder in the "DMD directories > 
 Library paths" option and verified that the path to the linker is correct.
 
 When I change to a Win32 configuration, it complains it can't open 
 'phobos32mscoff.lib' (even if I add the lib32coff folder to the path).
 
 If I build on the command line everything works fine. Does anyone have 
 any suggestion before I resort to using makefiles instead? Thanks.

I guess you are using the VC-projects in VS2017. In that case the Visual 
D settings are not transferred to msbuild in version 0.47. You might 
want to try a preliminary build from appveyor: 
https://ci.appveyor.com/project/rainers/visuald/build/1.0.230/job/c2g9qeg8c1dau3v6

Please ignore the "no compiler detected" message in the compiler 
settings, this function needs a small patch to phobos.

John Chapman <johnch_atms hotmail.com> writes:

On Saturday, 22 September 2018 at 13:49:36 UTC, Rainer Schuetze 
wrote:
 On 20/09/2018 14:17, John Chapman wrote:
 When I try to build within Visual D, I get the following error:
 
 LINK : fatal error LNK1104: cannot open file 'phobos64.lib'

 I guess you are using the VC-projects in VS2017. In that case 
 the Visual D settings are not transferred to msbuild in version 
 0.47. You might want to try a preliminary build from appveyor: 
 https://ci.appveyor.com/project/rainers/visuald/build/1.0.230/job/c2g9qeg8c1dau3v6

Thanks - that worked.

Another problem I'm having is that if I add version identifiers 
to the project's property page, Intellisense stops working for 
everything in core.sys.* - so that's all druntime's native API 
bindings.

Rainer Schuetze <r.sagitario gmx.de> writes:

On 10/10/2018 14:37, John Chapman wrote:
 On Saturday, 22 September 2018 at 13:49:36 UTC, Rainer Schuetze wrote:
 On 20/09/2018 14:17, John Chapman wrote:
 When I try to build within Visual D, I get the following error:

 LINK : fatal error LNK1104: cannot open file 'phobos64.lib'

 I guess you are using the VC-projects in VS2017. In that case the
 Visual D settings are not transferred to msbuild in version 0.47. You
 might want to try a preliminary build from appveyor:
 https://ci.appveyor.com/project/rainers/visuald/build/1.0.230/job/c2g9qeg8c1dau3v6

 
 Thanks - that worked.
 
 Another problem I'm having is that if I add version identifiers to the
 project's property page, Intellisense stops working for everything in
 core.sys.* - so that's all druntime's native API bindings.

Please try the latest beta, there has been a bug fix exactly for that
scenario:

https://github.com/dlang/visuald/releases/tag/v0.48.0-beta2