downloaded master and trying to build:


Error: module completion is in file 'vsi\completion.d' which cannot be read

..\sdk\port\base.d(16): Error: module windef is in file 'sdk\win32\windef.d' which cannot be read

..\tools\tlb2idl.d(4): Deprecation: module std.c.windows.com is deprecated - Import core.sys.windows.com instead

visuald.rc(82) : error RC2135 : file not found: Resources/PkgCmd.cto

\visuald-master\sdk\..\bin\Debug\vsi.lib
 Warning 2: File Not Found \visuald-master\sdk\..\bin\Debug\vsi.lib
\visuald-master\stdext\..\bin\Debug\stdext.lib
 Warning 2: File Not Found \visuald-master\stdext\..\bin\Debug\stdext.lib
..\bin\Debug\Win32\cpp2d.obj(cpp2d)
 Error 42: Symbol Undefined _D6stdext4file14expandFileListFAAyaAyaZAAya (immutable(char)[][] stdext.file.expandFileList(immutable(char)[][], immutable(char)[]))
..\bin\Debug\Win32\cpp2d.obj(cpp2d)
 Error 42: Symbol Undefined _D6stdext4path12normalizeDirFAyaZAya (immutable(char)[] stdext.path.normalizeDir(immutable(char)[]))
..\bin\Debug\Win32\cpp2d.obj(cpp2d)
 Error 42: Symbol Undefined _D6stdext6string12tokenizeArgsFAyabbZAAya (immutable(char)[][] stdext.string.tokenizeArgs(immutable(char)[], bool, bool))
..\bin\Debug\Win32\cpp2d.obj(cpp2d)
 Error 42: Symbol Undefined _D6stdext4path12__ModuleInfoZ
..\bin\Debug\Win32\cpp2d.obj(cpp2d)
 Error 42: Symbol Undefined _D6stdext4file12__ModuleInfoZ
\visuald-master\c2d\..\bin\Debug\Win32\c2d.lib(cpp2d)
 Error 42: Symbol Undefined _D6stdext4path20makeFilenameAbsoluteFAyaAyaZAya (immutable(char)[] stdext.path.makeFilenameAbsolute(immutable(char)[], immutable(char)[]))
\visuald-master\c2d\..\bin\Debug\Win32\c2d.lib(cpp2d)
 Error 42: Symbol Undefined _D6stdext4file12parseIniTextFAyaZHAyaHAyaAya (immutable(char)[][immutable(char)[]][immutable(char)[]] stdext.file.parseIniText(immutable(char)[]))
Building ..\bin\Debug\Win32\cpp2d.exe failed!


Using VS 2015 with VS sdk installed.

On 13.06.2016 19:11, Joerg Joergonson wrote:
> downloaded master and trying to build:
>
>
> Error: module completion is in file 'vsi\completion.d' which cannot be read
>
> ..\sdk\port\base.d(16): Error: module windef is in file
> 'sdk\win32\windef.d' which cannot be read
>
> ..\tools\tlb2idl.d(4): Deprecation: module std.c.windows.com is
> deprecated - Import core.sys.windows.com instead
>
> visuald.rc(82) : error RC2135 : file not found: Resources/PkgCmd.cto
>
> \visuald-master\sdk\..\bin\Debug\vsi.lib
>  Warning 2: File Not Found \visuald-master\sdk\..\bin\Debug\vsi.lib
> \visuald-master\stdext\..\bin\Debug\stdext.lib
>  Warning 2: File Not Found \visuald-master\stdext\..\bin\Debug\stdext.lib
> ..\bin\Debug\Win32\cpp2d.obj(cpp2d)
>  Error 42: Symbol Undefined _D6stdext4file14expandFileListFAAyaAyaZAAya
> (immutable(char)[][] stdext.file.expandFileList(immutable(char)[][],
> immutable(char)[]))
> ..\bin\Debug\Win32\cpp2d.obj(cpp2d)
>  Error 42: Symbol Undefined _D6stdext4path12normalizeDirFAyaZAya
> (immutable(char)[] stdext.path.normalizeDir(immutable(char)[]))
> ..\bin\Debug\Win32\cpp2d.obj(cpp2d)
>  Error 42: Symbol Undefined _D6stdext6string12tokenizeArgsFAyabbZAAya
> (immutable(char)[][] stdext.string.tokenizeArgs(immutable(char)[], bool,
> bool))
> ..\bin\Debug\Win32\cpp2d.obj(cpp2d)
>  Error 42: Symbol Undefined _D6stdext4path12__ModuleInfoZ
> ..\bin\Debug\Win32\cpp2d.obj(cpp2d)
>  Error 42: Symbol Undefined _D6stdext4file12__ModuleInfoZ
> \visuald-master\c2d\..\bin\Debug\Win32\c2d.lib(cpp2d)
>  Error 42: Symbol Undefined
> _D6stdext4path20makeFilenameAbsoluteFAyaAyaZAya (immutable(char)[]
> stdext.path.makeFilenameAbsolute(immutable(char)[], immutable(char)[]))
> \visuald-master\c2d\..\bin\Debug\Win32\c2d.lib(cpp2d)
>  Error 42: Symbol Undefined _D6stdext4file12parseIniTextFAyaZHAyaHAyaAya
> (immutable(char)[][immutable(char)[]][immutable(char)[]]
> stdext.file.parseIniText(immutable(char)[]))
> Building ..\bin\Debug\Win32\cpp2d.exe failed!
>
>
> Using VS 2015 with VS sdk installed.
>

Unfortunately the instructions at http://rainers.github.io/visuald/visuald/BuildFromSource.html are slightly out of date, the github README is a little better:

- install the Visual Studio SDK
- start Visual Studio and load solution visuald_vs9.sln (VS 2008) or visuald_vs10.sln (VS 2010+)
- build project "build"
- build project "VisualD"

On Monday, 13 June 2016 at 17:46:05 UTC, Rainer Schuetze wrote:
>
>
> On 13.06.2016 19:11, Joerg Joergonson wrote:
>>[...]
>
> Unfortunately the instructions at http://rainers.github.io/visuald/visuald/BuildFromSource.html are slightly out of date, the github README is a little better:
>
> - install the Visual Studio SDK
> - start Visual Studio and load solution visuald_vs9.sln (VS 2008) or visuald_vs10.sln (VS 2010+)
> - build project "build"
> - build project "VisualD"

That is where those errors come from:

Building just the build project gives the error

Building ..\bin\Debug\build.sdk...
could not detect the Visual Studio SDK
Building ..\bin\Debug\sdk.success failed!

I installed the sdk but I imagine 2015 is different than the one you used.

On 13.06.2016 20:14, Joerg Joergonson wrote:
> On Monday, 13 June 2016 at 17:46:05 UTC, Rainer Schuetze wrote:
>>
>>
>> On 13.06.2016 19:11, Joerg Joergonson wrote:
>>> [...]
>>
>> Unfortunately the instructions at
>> http://rainers.github.io/visuald/visuald/BuildFromSource.html are
>> slightly out of date, the github README is a little better:
>>
>> - install the Visual Studio SDK
>> - start Visual Studio and load solution visuald_vs9.sln (VS 2008) or
>> visuald_vs10.sln (VS 2010+)
>> - build project "build"
>> - build project "VisualD"
>
> That is where those errors come from:
>
> Building just the build project gives the error
>
> Building ..\bin\Debug\build.sdk...
> could not detect the Visual Studio SDK
> Building ..\bin\Debug\sdk.success failed!
>
> I installed the sdk but I imagine 2015 is different than the one you used.

Sorry, you are right. It seems I've only built against the VS 2013 SDK or earlier.

I pushed some changes to also build with the VS 2015 SDK.

On Wednesday, 15 June 2016 at 21:11:30 UTC, Rainer Schuetze wrote:
>
>
> On 13.06.2016 20:14, Joerg Joergonson wrote:
>> On Monday, 13 June 2016 at 17:46:05 UTC, Rainer Schuetze wrote:
>>> [...]
>>
>> That is where those errors come from:
>>
>> Building just the build project gives the error
>>
>> Building ..\bin\Debug\build.sdk...
>> could not detect the Visual Studio SDK
>> Building ..\bin\Debug\sdk.success failed!
>>
>> I installed the sdk but I imagine 2015 is different than the one you used.
>
> Sorry, you are right. It seems I've only built against the VS 2013 SDK or earlier.
>
> I pushed some changes to also build with the VS 2015 SDK.

Cool, thanks!

On Wednesday, 15 June 2016 at 21:22:25 UTC, Joerg Joergonson wrote:
> On Wednesday, 15 June 2016 at 21:11:30 UTC, Rainer Schuetze wrote:
>>
>>
>> On 13.06.2016 20:14, Joerg Joergonson wrote:
>>> On Monday, 13 June 2016 at 17:46:05 UTC, Rainer Schuetze wrote:
>>>> [...]
>>>
>>> That is where those errors come from:
>>>
>>> Building just the build project gives the error
>>>
>>> Building ..\bin\Debug\build.sdk...
>>> could not detect the Visual Studio SDK
>>> Building ..\bin\Debug\sdk.success failed!
>>>
>>> I installed the sdk but I imagine 2015 is different than the one you used.
>>
>> Sorry, you are right. It seems I've only built against the VS 2013 SDK or earlier.
>>
>> I pushed some changes to also build with the VS 2015 SDK.
>
> Cool, thanks!

Ok, the problem is that the sdk paths are not correct. MS now does some crazy versioning and all that:

...\Windows\Kits\10\Include\10.0.10586.0\um

I used a junction and had to copy files from shared to um to get it to compile. I then get the error:

std.file.FileException@std\file.d(578): ..\sdk\win32\10.0.10240.0\activdbg.d: The system cannot find the path specified.

Not sure why it's looking there... I went head and copied the file to it though.. it's in sdk\port though in the visuald dir.

That didn't work as I guess the path is the VD dir and not the Win kits... so I made it and copied.

Then this error:

..\sdk\win32\10.0.10586.0\activdbg.d: The system cannot find the path specified.


Which I did the same:

Then I get something about project has been modified outside VS and get this error


Translation successful!
Visual Studio now prompts to reload the vsi project, but cannot do so because the build is still running.
Please reload the solution manually.
WindowsSdkDir=C:\Program Files\Windows\Kits\10\
could not detect the Windows SDK library folder
Building ..\bin\Debug\sdk_libs.success failed!

Anyways, I feel this will continue until the correct paths are worked out.

Any ideas? I'm using Windows Kit 10.

On 15.06.2016 23:37, Joerg Joergonson wrote:
> On Wednesday, 15 June 2016 at 21:22:25 UTC, Joerg Joergonson wrote:
>> On Wednesday, 15 June 2016 at 21:11:30 UTC, Rainer Schuetze wrote:
>>>
>>>
>>> On 13.06.2016 20:14, Joerg Joergonson wrote:
>>>> On Monday, 13 June 2016 at 17:46:05 UTC, Rainer Schuetze wrote:
>>>>> [...]
>>>>
>>>> That is where those errors come from:
>>>>
>>>> Building just the build project gives the error
>>>>
>>>> Building ..\bin\Debug\build.sdk...
>>>> could not detect the Visual Studio SDK
>>>> Building ..\bin\Debug\sdk.success failed!
>>>>
>>>> I installed the sdk but I imagine 2015 is different than the one you
>>>> used.
>>>
>>> Sorry, you are right. It seems I've only built against the VS 2013
>>> SDK or earlier.
>>>
>>> I pushed some changes to also build with the VS 2015 SDK.
>>
>> Cool, thanks!
>
> Ok, the problem is that the sdk paths are not correct. MS now does some
> crazy versioning and all that:
>
> ...\Windows\Kits\10\Include\10.0.10586.0\um
>
> I used a junction and had to copy files from shared to um to get it to
> compile. I then get the error:
>
> std.file.FileException@std\file.d(578):
> ..\sdk\win32\10.0.10240.0\activdbg.d: The system cannot find the path
> specified.
>
> Not sure why it's looking there... I went head and copied the file to it
> though.. it's in sdk\port though in the visuald dir.
>
> That didn't work as I guess the path is the VD dir and not the Win
> kits... so I made it and copied.
>
> Then this error:
>
> ..\sdk\win32\10.0.10586.0\activdbg.d: The system cannot find the path
> specified.
>
>
> Which I did the same:
>
> Then I get something about project has been modified outside VS and get
> this error
>
>
> Translation successful!
> Visual Studio now prompts to reload the vsi project, but cannot do so
> because the build is still running.
> Please reload the solution manually.
> WindowsSdkDir=C:\Program Files\Windows\Kits\10\
> could not detect the Windows SDK library folder
> Building ..\bin\Debug\sdk_libs.success failed!
>
> Anyways, I feel this will continue until the correct paths are worked out.
>
> Any ideas? I'm using Windows Kit 10.
>

I've not yet adjusted the conversion to the Windows 10 SDK. I'll try to fix this, but maybe you can get hold of an Win 8.1 SDK in the mean time.

The version numbers inside the sdk\win32 folders are no good, this won't work.

On 16.06.2016 08:25, Rainer Schuetze wrote:
> I've not yet adjusted the conversion to the Windows 10 SDK. I'll try to
> fix this, but maybe you can get hold of an Win 8.1 SDK in the mean time.

I've pushed a few changes that allow converting the Windows 10 SDK. Please try again.

On Friday, 17 June 2016 at 08:02:24 UTC, Rainer Schuetze wrote:
>
>
> On 16.06.2016 08:25, Rainer Schuetze wrote:
>> I've not yet adjusted the conversion to the Windows 10 SDK. I'll try to
>> fix this, but maybe you can get hold of an Win 8.1 SDK in the mean time.
>
> I've pushed a few changes that allow converting the Windows 10 SDK. Please try again.


I still get "couldn't not detect sdk" and have to manually fix up. IIRC, it requires accessing the registry to find the proper info(I think I saw someone with a similar SDK problem in some software that said that).

On 18.06.2016 17:53, Joerg Joergonson wrote:
> On Friday, 17 June 2016 at 08:02:24 UTC, Rainer Schuetze wrote:
>>
>>
>> On 16.06.2016 08:25, Rainer Schuetze wrote:
>>> I've not yet adjusted the conversion to the Windows 10 SDK. I'll try to
>>> fix this, but maybe you can get hold of an Win 8.1 SDK in the mean time.
>>
>> I've pushed a few changes that allow converting the Windows 10 SDK.
>> Please try again.
>
>
> I still get "couldn't not detect sdk" and have to manually fix up. IIRC,
> it requires accessing the registry to find the proper info(I think I saw
> someone with a similar SDK problem in some software that said that).
>

Visual D is supposed to do that and set the WindowsSDKDir environment variable accordingly. Unfortunately, I left my test code in the batch file.

I've pushed a version without the test override.