digitalmars.D.ide - Visual D 0.3.43 beta1 available

Rainer Schuetze (5/5) Nov 01 2015 Hi,

Daniel N (13/18) Nov 01 2015 Thanks! Works great this far.

Rainer Schuetze (5/29) Nov 01 2015 Actually, I already created a template for DMD and LDC, but missed to

Daniel N (3/9) Nov 01 2015 Awesome! Oops, I did now, after you told me it exists, works like

Ramon (5/10) Nov 01 2015 The Add / New Folder does creates the folder, but if I move a
tester (56/61) Nov 04 2015 link errors

johann (2/71) Nov 04 2015 cant install and work???
Rainer Schuetze (4/69) Nov 04 2015 It seems it fails to add legacy_stdio_definitions.lib to the link

johann (11/108) Nov 05 2015 could you import that automatically?

johann (5/24) Nov 05 2015 now getting another error:

johann (5/25) Nov 05 2015 sorry forgot to mention
Rainer Schuetze (4/30) Nov 05 2015 I guess you have changed the subsystem to "Windows". main doesn't seem

johann (34/70) Nov 05 2015 thanks for the help pointers.

Rainer Schuetze (17/52) Nov 06 2015 The VC runtime libraries expect a WinMain entry point if you compile for...

johann (2/22) Nov 06 2015 thanks - i tried that and it doesn't work. i am bust now.

Rainer Schuetze (4/31) Nov 07 2015 "doesn't work" means same error?

johann (5/14) Nov 07 2015 sorry - sure it works, but when i use your example, it does not

Rainer Schuetze (2/7) Nov 05 2015 Yeah, I already fixed that. It'll be in the next beta.

Rainer Schuetze (3/8) Nov 05 2015 Now updated to a new beta:

Andrew LaChance (30/44) Dec 05 2015 Thank you for the update! It fixed my link issues.

Rainer Schuetze (6/51) Dec 07 2015 I can reproduce the problem here. This is caused by the breakpoint

Andrew LaChance (2/9) Dec 09 2015 Oh wow, that sounds nasty! Is there a bug in dmd for this?

Rainer Schuetze (2/15) Dec 10 2015 I have added a report here: https://issues.dlang.org/show_bug.cgi?id=154...

Andrew LaChance (9/11) Dec 05 2015 Hello! A small issue I noticed: If I create a configuration for

Rainer Schuetze (7/20) Dec 07 2015 Thanks for reporting. You can also file issues at

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

Hi,

I just uploaded a beta for the next release of Visual D.

You can find the list of changes and the installer here:

https://github.com/D-Programming-Language/visuald/releases/tag/v0.3.43-beta1 


Rainer

Nov 01 2015

Daniel N <ufo orbiting.us> writes:

On Sunday, 1 November 2015 at 10:29:23 UTC, Rainer Schuetze wrote:
 Hi,

 I just uploaded a beta for the next release of Visual D.

 You can find the list of changes and the installer here:

 https://github.com/D-Programming-Language/visuald/releases/tag/v0.3.43-beta1


 Rainer

Thanks! Works great this far.

Would it be possible to add project templates for LDC(x64)

Currently after creating a project one has to manually:
1) Switch from DMD to LDC
2) Create a new target x64 based upon x86.
3) Override the path to ldc2.exe

At least the first two steps could be solved with a project 
template...

(first after writing this. I realized that Console Application 
*DMD/GDC* actually creates 64bit projects by default, but since I 
only was interested in LDC I didn't even consider that option, 
maybe it should be renamed...?)

Nov 01 2015

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

On 01.11.2015 13:15, Daniel N wrote:
 On Sunday, 1 November 2015 at 10:29:23 UTC, Rainer Schuetze wrote:
 Hi,

 I just uploaded a beta for the next release of Visual D.

 You can find the list of changes and the installer here:

 https://github.com/D-Programming-Language/visuald/releases/tag/v0.3.43-beta1



 Rainer

 Thanks! Works great this far.

 Would it be possible to add project templates for LDC(x64)

 Currently after creating a project one has to manually:
 1) Switch from DMD to LDC
 2) Create a new target x64 based upon x86.
 3) Override the path to ldc2.exe

 At least the first two steps could be solved with a project template...

 (first after writing this. I realized that Console Application *DMD/GDC*
 actually creates 64bit projects by default, but since I only was
 interested in LDC I didn't even consider that option, maybe it should be
 renamed...?)

Actually, I already created a template for DMD and LDC, but missed to 
add it to the installer. It'll be in the next beta.

 3) Override the path to ldc2.exe

Why do you have to do this? Didn't you configure the LDC installation 
folder on the global "Projects and Solutions->Visual D" pages?

Nov 01 2015

Daniel N <ufo orbiting.us> writes:

On Sunday, 1 November 2015 at 13:46:41 UTC, Rainer Schuetze wrote:
 Actually, I already created a template for DMD and LDC, but 
 missed to add it to the installer. It'll be in the next beta.

 3) Override the path to ldc2.exe

 Why do you have to do this? Didn't you configure the LDC 
 installation folder on the global "Projects and 
 Solutions->Visual D" pages?

Awesome! Oops, I did now, after you told me it exists, works like 
a charm. :)

Nov 01 2015

Ramon <midiway midi.rs> writes:

On Sunday, 1 November 2015 at 10:29:23 UTC, Rainer Schuetze wrote:
 Hi,

 I just uploaded a beta for the next release of Visual D.

 You can find the list of changes and the installer here:

 https://github.com/D-Programming-Language/visuald/releases/tag/v0.3.43-beta1


 Rainer

The Add / New Folder does creates the folder, but if I move a 
file inside a folder item, the file isn't really moved.

I think you should drop completely the 'Filter' kind of folder 
and stick to the file system hierarchy

Nov 01 2015

tester <tester test.com> writes:

On Sunday, 1 November 2015 at 10:29:23 UTC, Rainer Schuetze wrote:
 Hi,

 I just uploaded a beta for the next release of Visual D.

 You can find the list of changes and the installer here:

 https://github.com/D-Programming-Language/visuald/releases/tag/v0.3.43-beta1


 Rainer

link errors


Command Line

set PATH=C:\proggies\D\dmd2\windows\bin;C:\Program Files 
(x86)\Microsoft Visual Studio 14.0\\Common7\IDE;C:\Program Files 
(x86)\Windows Kits\8.1\\bin;%PATH%
set DMD_LIB=C:\Program Files (x86)\Microsoft Visual Studio 
14.0\VC\\lib\amd64;C:\Program Files (x86)\Windows 
Kits\8.1\Lib\winv6.3\um\x64
set WindowsSdkDir=C:\Program Files (x86)\Windows Kits\8.1\
set VCINSTALLDIR=C:\Program Files (x86)\Microsoft Visual Studio 
14.0\VC\
dmd -m64 -g -debug -gx -allinst -X -Xf"Debug\ConsoleApp3.json" 
-deps="Debug\ConsoleApp3.dep" -c -of"Debug\ConsoleApp3.obj" main.d
if errorlevel 1 goto reportError

set LIB="C:\proggies\D\dmd2\windows\bin\..\lib64";"C:\Program 
Files (x86)\Microsoft Visual Studio 
14.0\VC\\lib\amd64";"C:\Program Files (x86)\Windows 
Kits\10\\Lib\10.0.10240.0\um\x64";"C:\Program Files (x86)\Windows 
Kits\10\\Lib\10.0.10240.0\ucrt\x64";"C:\Program Files 
(x86)\Windows Kits\10\\Lib\winv6.3\um\x64";"C:\Program Files 
(x86)\Windows Kits\10\\Lib\win8\um\x64";"C:\Program Files 
(x86)\Windows Kits\10\\Lib\x64";"\Lib\x64"
echo. > Y:\ConsoleApp3\ConsoleApp3\Debug\ConsoleApp3.build.lnkarg
echo "Debug\ConsoleApp3.obj" /OUT:"Debug\ConsoleApp3.exe" 
/MAP:"Debug\ConsoleApp3.map" user32.lib kernel32.lib 
/LIBPATH:"C:\Program Files (x86)\Microsoft Visual Studio 
14.0\VC\\lib\amd64" /LIBPATH:"C:\Program Files (x86)\Windows 
Kits\8.1\Lib\winv6.3\um\x64" /DEBUG /INCREMENTAL:NO /NOLOGO 
/NODEFAULTLIB:libcmt libcmtd.lib >> 
Y:\ConsoleApp3\ConsoleApp3\Debug\ConsoleApp3.build.lnkarg

"C:\proggies\VisualD\pipedmd.exe" -deps Debug\ConsoleApp3.lnkdep 
"C:\Program Files (x86)\Microsoft Visual Studio 
14.0\VC\\bin\link.exe" 
 Y:\ConsoleApp3\ConsoleApp3\Debug\ConsoleApp3.build.lnkarg
if errorlevel 1 goto reportError
if not exist "Debug\ConsoleApp3.exe" (echo 
"Debug\ConsoleApp3.exe" not created! && goto reportError)

goto noError

:reportError
echo Building Debug\ConsoleApp3.exe failed!

:noError
Output

phobos64.lib(stacktrace_3bb_3e5.obj) : error LNK2019: unresolved 
external symbol snprintf referenced in function 
_D4core3sys7windows10stacktrace10StackTrace13resolveNoSyncFAxmZAAa (char[][]
core.sys.windows.stacktrace.StackTrace.resolveNoSync(const(ulong)[]))
phobos64.lib(config_493_452.obj) : error LNK2001: unresolved 
external symbol snprintf
phobos64.lib(demangle_1ec_31d.obj) : error LNK2001: unresolved 
external symbol snprintf
phobos64.lib(config_493_452.obj) : error LNK2019: unresolved 
external symbol sscanf referenced in function 
_D2gc6config13__T5parseHTfZ5parseFNbNiAxaKAxaKfZb
Debug\ConsoleApp3.exe : fatal error LNK1120: 2 unresolved 
externals
Building Debug\ConsoleApp3.exe failed!

Nov 04 2015

johann <wechsler aol.com> writes:

On Wednesday, 4 November 2015 at 09:32:25 UTC, tester wrote:
 On Sunday, 1 November 2015 at 10:29:23 UTC, Rainer Schuetze 
 wrote:
 Hi,

 I just uploaded a beta for the next release of Visual D.

 You can find the list of changes and the installer here:

 https://github.com/D-Programming-Language/visuald/releases/tag/v0.3.43-beta1


 Rainer

 link errors


 Command Line

 set PATH=C:\proggies\D\dmd2\windows\bin;C:\Program Files 
 (x86)\Microsoft Visual Studio 14.0\\Common7\IDE;C:\Program 
 Files (x86)\Windows Kits\8.1\\bin;%PATH%
 set DMD_LIB=C:\Program Files (x86)\Microsoft Visual Studio 
 14.0\VC\\lib\amd64;C:\Program Files (x86)\Windows 
 Kits\8.1\Lib\winv6.3\um\x64
 set WindowsSdkDir=C:\Program Files (x86)\Windows Kits\8.1\
 set VCINSTALLDIR=C:\Program Files (x86)\Microsoft Visual Studio 
 14.0\VC\
 dmd -m64 -g -debug -gx -allinst -X -Xf"Debug\ConsoleApp3.json" 
 -deps="Debug\ConsoleApp3.dep" -c -of"Debug\ConsoleApp3.obj" 
 main.d
 if errorlevel 1 goto reportError

 set LIB="C:\proggies\D\dmd2\windows\bin\..\lib64";"C:\Program 
 Files (x86)\Microsoft Visual Studio 
 14.0\VC\\lib\amd64";"C:\Program Files (x86)\Windows 
 Kits\10\\Lib\10.0.10240.0\um\x64";"C:\Program Files 
 (x86)\Windows Kits\10\\Lib\10.0.10240.0\ucrt\x64";"C:\Program 
 Files (x86)\Windows Kits\10\\Lib\winv6.3\um\x64";"C:\Program 
 Files (x86)\Windows Kits\10\\Lib\win8\um\x64";"C:\Program Files 
 (x86)\Windows Kits\10\\Lib\x64";"\Lib\x64"
 echo. > 
 Y:\ConsoleApp3\ConsoleApp3\Debug\ConsoleApp3.build.lnkarg
 echo "Debug\ConsoleApp3.obj" /OUT:"Debug\ConsoleApp3.exe" 
 /MAP:"Debug\ConsoleApp3.map" user32.lib kernel32.lib 
 /LIBPATH:"C:\Program Files (x86)\Microsoft Visual Studio 
 14.0\VC\\lib\amd64" /LIBPATH:"C:\Program Files (x86)\Windows 
 Kits\8.1\Lib\winv6.3\um\x64" /DEBUG /INCREMENTAL:NO /NOLOGO 
 /NODEFAULTLIB:libcmt libcmtd.lib >> 
 Y:\ConsoleApp3\ConsoleApp3\Debug\ConsoleApp3.build.lnkarg

 "C:\proggies\VisualD\pipedmd.exe" -deps 
 Debug\ConsoleApp3.lnkdep "C:\Program Files (x86)\Microsoft 
 Visual Studio 14.0\VC\\bin\link.exe" 
  Y:\ConsoleApp3\ConsoleApp3\Debug\ConsoleApp3.build.lnkarg
 if errorlevel 1 goto reportError
 if not exist "Debug\ConsoleApp3.exe" (echo 
 "Debug\ConsoleApp3.exe" not created! && goto reportError)

 goto noError

 :reportError
 echo Building Debug\ConsoleApp3.exe failed!

 :noError
 Output

 phobos64.lib(stacktrace_3bb_3e5.obj) : error LNK2019: 
 unresolved external symbol snprintf referenced in function 
 _D4core3sys7windows10stacktrace10StackTrace13resolveNoSyncFAxmZAAa (char[][]
core.sys.windows.stacktrace.StackTrace.resolveNoSync(const(ulong)[]))
 phobos64.lib(config_493_452.obj) : error LNK2001: unresolved 
 external symbol snprintf
 phobos64.lib(demangle_1ec_31d.obj) : error LNK2001: unresolved 
 external symbol snprintf
 phobos64.lib(config_493_452.obj) : error LNK2019: unresolved 
 external symbol sscanf referenced in function 
 _D2gc6config13__T5parseHTfZ5parseFNbNiAxaKAxaKfZb
 Debug\ConsoleApp3.exe : fatal error LNK1120: 2 unresolved 
 externals
 Building Debug\ConsoleApp3.exe failed!

cant install and work???

Nov 04 2015

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

On 04.11.2015 10:32, tester wrote:
 On Sunday, 1 November 2015 at 10:29:23 UTC, Rainer Schuetze wrote:
 Hi,

 I just uploaded a beta for the next release of Visual D.

 You can find the list of changes and the installer here:

 https://github.com/D-Programming-Language/visuald/releases/tag/v0.3.43-beta1



 Rainer

 link errors


 Command Line

 set PATH=C:\proggies\D\dmd2\windows\bin;C:\Program Files (x86)\Microsoft
 Visual Studio 14.0\\Common7\IDE;C:\Program Files (x86)\Windows
 Kits\8.1\\bin;%PATH%
 set DMD_LIB=C:\Program Files (x86)\Microsoft Visual Studio
 14.0\VC\\lib\amd64;C:\Program Files (x86)\Windows
 Kits\8.1\Lib\winv6.3\um\x64
 set WindowsSdkDir=C:\Program Files (x86)\Windows Kits\8.1\
 set VCINSTALLDIR=C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\
 dmd -m64 -g -debug -gx -allinst -X -Xf"Debug\ConsoleApp3.json"
 -deps="Debug\ConsoleApp3.dep" -c -of"Debug\ConsoleApp3.obj" main.d
 if errorlevel 1 goto reportError

 set LIB="C:\proggies\D\dmd2\windows\bin\..\lib64";"C:\Program Files
 (x86)\Microsoft Visual Studio 14.0\VC\\lib\amd64";"C:\Program Files
 (x86)\Windows Kits\10\\Lib\10.0.10240.0\um\x64";"C:\Program Files
 (x86)\Windows Kits\10\\Lib\10.0.10240.0\ucrt\x64";"C:\Program Files
 (x86)\Windows Kits\10\\Lib\winv6.3\um\x64";"C:\Program Files
 (x86)\Windows Kits\10\\Lib\win8\um\x64";"C:\Program Files (x86)\Windows
 Kits\10\\Lib\x64";"\Lib\x64"
 echo. > Y:\ConsoleApp3\ConsoleApp3\Debug\ConsoleApp3.build.lnkarg
 echo "Debug\ConsoleApp3.obj" /OUT:"Debug\ConsoleApp3.exe"
 /MAP:"Debug\ConsoleApp3.map" user32.lib kernel32.lib
 /LIBPATH:"C:\Program Files (x86)\Microsoft Visual Studio
 14.0\VC\\lib\amd64" /LIBPATH:"C:\Program Files (x86)\Windows
 Kits\8.1\Lib\winv6.3\um\x64" /DEBUG /INCREMENTAL:NO /NOLOGO
 /NODEFAULTLIB:libcmt libcmtd.lib >>
 Y:\ConsoleApp3\ConsoleApp3\Debug\ConsoleApp3.build.lnkarg

 "C:\proggies\VisualD\pipedmd.exe" -deps Debug\ConsoleApp3.lnkdep
 "C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\\bin\link.exe"
  Y:\ConsoleApp3\ConsoleApp3\Debug\ConsoleApp3.build.lnkarg
 if errorlevel 1 goto reportError
 if not exist "Debug\ConsoleApp3.exe" (echo "Debug\ConsoleApp3.exe" not
 created! && goto reportError)

 goto noError

 :reportError
 echo Building Debug\ConsoleApp3.exe failed!

 :noError
 Output

 phobos64.lib(stacktrace_3bb_3e5.obj) : error LNK2019: unresolved
 external symbol snprintf referenced in function
 _D4core3sys7windows10stacktrace10StackTrace13resolveNoSyncFAxmZAAa
 (char[][]
 core.sys.windows.stacktrace.StackTrace.resolveNoSync(const(ulong)[]))
 phobos64.lib(config_493_452.obj) : error LNK2001: unresolved external
 symbol snprintf
 phobos64.lib(demangle_1ec_31d.obj) : error LNK2001: unresolved external
 symbol snprintf
 phobos64.lib(config_493_452.obj) : error LNK2019: unresolved external
 symbol sscanf referenced in function
 _D2gc6config13__T5parseHTfZ5parseFNbNiAxaKAxaKfZb
 Debug\ConsoleApp3.exe : fatal error LNK1120: 2 unresolved externals
 Building Debug\ConsoleApp3.exe failed!

It seems it fails to add legacy_stdio_definitions.lib to the link 
command line. You could try to add it to the "additional linker options" 
in the globl settings as a workaround.

Nov 04 2015

johann <wechsler aol.com> writes:

On Wednesday, 4 November 2015 at 18:33:49 UTC, Rainer Schuetze 
wrote:
 On 04.11.2015 10:32, tester wrote:
 On Sunday, 1 November 2015 at 10:29:23 UTC, Rainer Schuetze 
 wrote:
 Hi,

 I just uploaded a beta for the next release of Visual D.

 You can find the list of changes and the installer here:

 https://github.com/D-Programming-Language/visuald/releases/tag/v0.3.43-beta1



 Rainer

 link errors


 Command Line

 set PATH=C:\proggies\D\dmd2\windows\bin;C:\Program Files 
 (x86)\Microsoft
 Visual Studio 14.0\\Common7\IDE;C:\Program Files (x86)\Windows
 Kits\8.1\\bin;%PATH%
 set DMD_LIB=C:\Program Files (x86)\Microsoft Visual Studio
 14.0\VC\\lib\amd64;C:\Program Files (x86)\Windows
 Kits\8.1\Lib\winv6.3\um\x64
 set WindowsSdkDir=C:\Program Files (x86)\Windows Kits\8.1\
 set VCINSTALLDIR=C:\Program Files (x86)\Microsoft Visual 
 Studio 14.0\VC\
 dmd -m64 -g -debug -gx -allinst -X -Xf"Debug\ConsoleApp3.json"
 -deps="Debug\ConsoleApp3.dep" -c -of"Debug\ConsoleApp3.obj" 
 main.d
 if errorlevel 1 goto reportError

 set LIB="C:\proggies\D\dmd2\windows\bin\..\lib64";"C:\Program 
 Files
 (x86)\Microsoft Visual Studio 14.0\VC\\lib\amd64";"C:\Program 
 Files
 (x86)\Windows Kits\10\\Lib\10.0.10240.0\um\x64";"C:\Program 
 Files
 (x86)\Windows Kits\10\\Lib\10.0.10240.0\ucrt\x64";"C:\Program 
 Files
 (x86)\Windows Kits\10\\Lib\winv6.3\um\x64";"C:\Program Files
 (x86)\Windows Kits\10\\Lib\win8\um\x64";"C:\Program Files 
 (x86)\Windows
 Kits\10\\Lib\x64";"\Lib\x64"
 echo. > 
 Y:\ConsoleApp3\ConsoleApp3\Debug\ConsoleApp3.build.lnkarg
 echo "Debug\ConsoleApp3.obj" /OUT:"Debug\ConsoleApp3.exe"
 /MAP:"Debug\ConsoleApp3.map" user32.lib kernel32.lib
 /LIBPATH:"C:\Program Files (x86)\Microsoft Visual Studio
 14.0\VC\\lib\amd64" /LIBPATH:"C:\Program Files (x86)\Windows
 Kits\8.1\Lib\winv6.3\um\x64" /DEBUG /INCREMENTAL:NO /NOLOGO
 /NODEFAULTLIB:libcmt libcmtd.lib >>
 Y:\ConsoleApp3\ConsoleApp3\Debug\ConsoleApp3.build.lnkarg

 "C:\proggies\VisualD\pipedmd.exe" -deps 
 Debug\ConsoleApp3.lnkdep
 "C:\Program Files (x86)\Microsoft Visual Studio 
 14.0\VC\\bin\link.exe"
  Y:\ConsoleApp3\ConsoleApp3\Debug\ConsoleApp3.build.lnkarg
 if errorlevel 1 goto reportError
 if not exist "Debug\ConsoleApp3.exe" (echo 
 "Debug\ConsoleApp3.exe" not
 created! && goto reportError)

 goto noError

 :reportError
 echo Building Debug\ConsoleApp3.exe failed!

 :noError
 Output

 phobos64.lib(stacktrace_3bb_3e5.obj) : error LNK2019: 
 unresolved
 external symbol snprintf referenced in function
 _D4core3sys7windows10stacktrace10StackTrace13resolveNoSyncFAxmZAAa
 (char[][]
 core.sys.windows.stacktrace.StackTrace.resolveNoSync(const(ulong)[]))
 phobos64.lib(config_493_452.obj) : error LNK2001: unresolved 
 external
 symbol snprintf
 phobos64.lib(demangle_1ec_31d.obj) : error LNK2001: unresolved 
 external
 symbol snprintf
 phobos64.lib(config_493_452.obj) : error LNK2019: unresolved 
 external
 symbol sscanf referenced in function
 _D2gc6config13__T5parseHTfZ5parseFNbNiAxaKAxaKfZb
 Debug\ConsoleApp3.exe : fatal error LNK1120: 2 unresolved 
 externals
 Building Debug\ConsoleApp3.exe failed!

 It seems it fails to add legacy_stdio_definitions.lib to the 
 link command line. You could try to add it to the "additional 
 linker options" in the globl settings as a workaround.

could you import that automatically?
i just made an console program with nothing in it - except the 
main.d with the content:

import std.stdio;

int main(string[] argv)
{
     writeln("Hello D-World!");
     return 0;
}

Nov 05 2015

johann <wechsler aol.com> writes:

On Thursday, 5 November 2015 at 11:07:04 UTC, johann wrote:
 On Wednesday, 4 November 2015 at 18:33:49 UTC, Rainer Schuetze 
 wrote:
 On 04.11.2015 10:32, tester wrote:
 [...]

 It seems it fails to add legacy_stdio_definitions.lib to the 
 link command line. You could try to add it to the "additional 
 linker options" in the globl settings as a workaround.

 could you import that automatically?
 i just made an console program with nothing in it - except the 
 main.d with the content:

 import std.stdio;

 int main(string[] argv)
 {
     writeln("Hello D-World!");
     return 0;
 }

now getting another error:
LIBCMT.lib(exe_winmain.obj) : error LNK2019: unresolved external 
symbol WinMain referenced in function "int __cdecl 
__scrt_common_main_seh(void)" (?__scrt_common_main_seh  YAHXZ)

Nov 05 2015

johann <wechsler aol.com> writes:

On Thursday, 5 November 2015 at 11:12:11 UTC, johann wrote:
 On Thursday, 5 November 2015 at 11:07:04 UTC, johann wrote:
 On Wednesday, 4 November 2015 at 18:33:49 UTC, Rainer Schuetze 
 wrote:
 [...]

 could you import that automatically?
 i just made an console program with nothing in it - except the 
 main.d with the content:

 import std.stdio;

 int main(string[] argv)
 {
     writeln("Hello D-World!");
     return 0;
 }

 now getting another error:
 LIBCMT.lib(exe_winmain.obj) : error LNK2019: unresolved 
 external symbol WinMain referenced in function "int __cdecl 
 __scrt_common_main_seh(void)" (?__scrt_common_main_seh  YAHXZ)

sorry forgot to mention

installed 2069 new
installed visuald Visual D 0.3.43 beta1
use VS2015

Nov 05 2015

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

On 05.11.2015 12:11, johann wrote:
 On Thursday, 5 November 2015 at 11:07:04 UTC, johann wrote:
 On Wednesday, 4 November 2015 at 18:33:49 UTC, Rainer Schuetze wrote:
 On 04.11.2015 10:32, tester wrote:
 [...]

 It seems it fails to add legacy_stdio_definitions.lib to the link
 command line. You could try to add it to the "additional linker
 options" in the globl settings as a workaround.

 could you import that automatically?
 i just made an console program with nothing in it - except the main.d
 with the content:

 import std.stdio;

 int main(string[] argv)
 {
     writeln("Hello D-World!");
     return 0;
 }

 now getting another error:
 LIBCMT.lib(exe_winmain.obj) : error LNK2019: unresolved external symbol
 WinMain referenced in function "int __cdecl
 __scrt_common_main_seh(void)" (?__scrt_common_main_seh  YAHXZ)

I guess you have changed the subsystem to "Windows". main doesn't seem 
to work then (only for "Console"), you'll have to implement WinMain as 
in the WindowsApplication template.

Nov 05 2015

johann <wechsler aol.com> writes:

On Thursday, 5 November 2015 at 20:27:32 UTC, Rainer Schuetze 
wrote:
 On 05.11.2015 12:11, johann wrote:
 On Thursday, 5 November 2015 at 11:07:04 UTC, johann wrote:
 On Wednesday, 4 November 2015 at 18:33:49 UTC, Rainer 
 Schuetze wrote:
 On 04.11.2015 10:32, tester wrote:
 [...]

 It seems it fails to add legacy_stdio_definitions.lib to the 
 link
 command line. You could try to add it to the "additional 
 linker
 options" in the globl settings as a workaround.

 could you import that automatically?
 i just made an console program with nothing in it - except 
 the main.d
 with the content:

 import std.stdio;

 int main(string[] argv)
 {
     writeln("Hello D-World!");
     return 0;
 }

 now getting another error:
 LIBCMT.lib(exe_winmain.obj) : error LNK2019: unresolved 
 external symbol
 WinMain referenced in function "int __cdecl
 __scrt_common_main_seh(void)" (?__scrt_common_main_seh  YAHXZ)

 I guess you have changed the subsystem to "Windows". main 
 doesn't seem to work then (only for "Console"), you'll have to 
 implement WinMain as in the WindowsApplication template.

thanks for the help pointers.
i generated the dfl2 lib anew with the current compiler - works 
fine for x64. the lib was seemingly maintained by a gentleman 
named franklike.
as for main, i used the following code:

import dfl.all;
int main()
{
	Form myForm;
	Label myLabel;
	myForm = new Form;
	myForm.text = "DFL Example";
	myLabel = new Label;
	myLabel.font = new Font("Verdana", 14f);
	myLabel.text = "Hello, DFL World!";
	myLabel.location = Point(15, 15);
	myLabel.autoSize = true;
	myLabel.parent = myForm;
	Application.run(myForm);
	return 0;
}

i set the subsystem to console (or 'Not Set') and try to link 
with the dfl2 lib. that works for console and it runs as expected 
- just with console window in the background.

if i set it to windows subsystem the link fails with:
LIBCMT.lib(exe_winmain.obj) : error LNK2019: unresolved external 
symbol WinMain referenced in function "int __cdecl 
__scrt_common_main_seh(void)" (?__scrt_common_main_seh  YAHXZ)
Release\dflTEST.exe : fatal error LNK1120: 1 unresolved externals
Building Release\dflTEST.exe failed!

do you have any suggestion what happens? how can i get rid of the 
console window after linking?

Nov 05 2015

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

On 06.11.2015 08:45, johann wrote:
 On Thursday, 5 November 2015 at 20:27:32 UTC, Rainer Schuetze wrote:
 I guess you have changed the subsystem to "Windows". main doesn't seem
 to work then (only for "Console"), you'll have to implement WinMain as
 in the WindowsApplication template.

 thanks for the help pointers.
 i generated the dfl2 lib anew with the current compiler - works fine for
 x64. the lib was seemingly maintained by a gentleman named franklike.
 as for main, i used the following code:

 import dfl.all;
 int main()
 {
      Form myForm;
      Label myLabel;
      myForm = new Form;
      myForm.text = "DFL Example";
      myLabel = new Label;
      myLabel.font = new Font("Verdana", 14f);
      myLabel.text = "Hello, DFL World!";
      myLabel.location = Point(15, 15);
      myLabel.autoSize = true;
      myLabel.parent = myForm;
      Application.run(myForm);
      return 0;
 }

 i set the subsystem to console (or 'Not Set') and try to link with the
 dfl2 lib. that works for console and it runs as expected - just with
 console window in the background.

 if i set it to windows subsystem the link fails with:
 LIBCMT.lib(exe_winmain.obj) : error LNK2019: unresolved external symbol
 WinMain referenced in function "int __cdecl
 __scrt_common_main_seh(void)" (?__scrt_common_main_seh  YAHXZ)
 Release\dflTEST.exe : fatal error LNK1120: 1 unresolved externals
 Building Release\dflTEST.exe failed!

 do you have any suggestion what happens? how can i get rid of the
 console window after linking?

The VC runtime libraries expect a WinMain entry point if you compile for 
subsystem windows, so you should replace main() with WinMain:

import core.runtime;
import core.sys.windows.windows;

extern (Windows)
int WinMain(HINSTANCE hInstance, HINSTANCE hPrevInstance, LPSTR 
lpCmdLine, int nCmdShow)
{
       Runtime.initialize();

       Form myForm;
       ...
       Runtime.terminate();
       return 0;
}

AFAICT this was different in earlier versions of the VC runtime. I'm not 
sure if the D runtime can/should try to redirect this to main().

Nov 06 2015

johann <johann aol.com> writes:

On Friday, 6 November 2015 at 13:08:51 UTC, Rainer Schuetze wrote:
 On 06.11.2015 08:45, johann wrote:
[...]

 The VC runtime libraries expect a WinMain entry point if you 
 compile for subsystem windows, so you should replace main() 
 with WinMain:

 import core.runtime;
 import core.sys.windows.windows;

 extern (Windows)
 int WinMain(HINSTANCE hInstance, HINSTANCE hPrevInstance, LPSTR 
 lpCmdLine, int nCmdShow)
 {
       Runtime.initialize();

       Form myForm;
       ...
       Runtime.terminate();
       return 0;
 }

 AFAICT this was different in earlier versions of the VC 
 runtime. I'm not sure if the D runtime can/should try to 
 redirect this to main().

thanks - i tried that and it doesn't work. i am bust now.

Nov 06 2015

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

On 06.11.2015 14:46, johann wrote:
 On Friday, 6 November 2015 at 13:08:51 UTC, Rainer Schuetze wrote:
 On 06.11.2015 08:45, johann wrote:
 [...]

 The VC runtime libraries expect a WinMain entry point if you compile
 for subsystem windows, so you should replace main() with WinMain:

 import core.runtime;
 import core.sys.windows.windows;

 extern (Windows)
 int WinMain(HINSTANCE hInstance, HINSTANCE hPrevInstance, LPSTR
 lpCmdLine, int nCmdShow)
 {
       Runtime.initialize();

       Form myForm;
       ...
       Runtime.terminate();
       return 0;
 }

 AFAICT this was different in earlier versions of the VC runtime. I'm
 not sure if the D runtime can/should try to redirect this to main().

 thanks - i tried that and it doesn't work. i am bust now.

"doesn't work" means same error?

The WindowsApplication project template works for me, maybe you can use 
it as a starting point.

Nov 07 2015

johann <johann aol.com> writes:

On Saturday, 7 November 2015 at 13:01:12 UTC, Rainer Schuetze 
wrote:
 On 06.11.2015 14:46, johann wrote:
 On Friday, 6 November 2015 at 13:08:51 UTC, Rainer Schuetze 
 wrote:
 [...]

 thanks - i tried that and it doesn't work. i am bust now.

 "doesn't work" means same error?

 The WindowsApplication project template works for me, maybe you 
 can use it as a starting point.

sorry - sure it works, but when i use your example, it does not 
produce a window - just does nothing. there seems to be a 
conflict with dfl2, well thats at least my guess.

Nov 07 2015

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

On 05.11.2015 12:07, johann wrote:
 It seems it fails to add legacy_stdio_definitions.lib to the link
 command line. You could try to add it to the "additional linker
 options" in the globl settings as a workaround.

 could you import that automatically?

Yeah, I already fixed that. It'll be in the next beta.

Nov 05 2015

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

On 01.11.2015 11:29, Rainer Schuetze wrote:
 Hi,

 I just uploaded a beta for the next release of Visual D.

 You can find the list of changes and the installer here:

 https://github.com/D-Programming-Language/visuald/releases/tag/v0.3.43-beta1


 Rainer

Now updated to a new beta:

https://github.com/D-Programming-Language/visuald/releases/tag/v0.3.43-beta2

Nov 05 2015

Andrew LaChance <lachance.ak gmail.com> writes:

On Thursday, 5 November 2015 at 22:12:39 UTC, Rainer Schuetze 
wrote:
 On 01.11.2015 11:29, Rainer Schuetze wrote:
 Hi,

 I just uploaded a beta for the next release of Visual D.

 You can find the list of changes and the installer here:

 https://github.com/D-Programming-Language/visuald/releases/tag/v0.3.43-beta1


 Rainer

 Now updated to a new beta:

 https://github.com/D-Programming-Language/visuald/releases/tag/v0.3.43-beta2

Thank you for the update!  It fixed my link issues.

I have found a very strange issue with I *think* visual D.  I 
have condensed into a very small repro here: 
http://1drv.ms/1Oai14L (entire solution).  If I build and run on 
x86 build config, everything is fine.  But on x64, debugging 
(with Debug x64 config) will cause an exception somewhere on this 
line:

writeln(AnotherColor.Red.stringof); // AnotherColor is an enum

But if I were to run the exe from the command line it is fine.  
Release version is fine too.  Also, it is fine if I put a 
breakpoint on the first line in main.d and then step over each 
line.  But hitting continue will throw an exception.  I'm not 
exactly sure where the exception comes from:
  
	DPlayground.exe!_D2rt6dmain211_d_run_mainUiPPaPUAAaZiZ6runAl
MFZ9__lambda1MFZv() + 0x32 bytes	D
  
	DPlayground.exe!_D2rt6dmain211_d_run_mainUiPPaPUAAaZiZ7tryExecMFMDFZvZv() +
0x6f bytes	D
  
	DPlayground.exe!_D2rt6dmain211_d_run_mainUiPPaPUAAaZiZ6runAllMFZv() + 0x3c
bytes	D
  
	DPlayground.exe!_D2rt6dmain211_d_run_mainUiPPaPUAAaZiZ7tryExecMFMDFZvZv() +
0x6f bytes	D
  	DPlayground.exe!_d_run_main() + 0x421 bytes	D
  	DPlayground.exe!__entrypoint.main( int argc, char** argv ) + 
0x22 bytes	D
	DPlayground.exe!invoke_main() Line 75	D

  	DPlayground.exe!__scrt_common_main_seh() Line 264 + 0x5 bytes	D
  	DPlayground.exe!__scrt_common_main() Line 309	D
  	DPlayground.exe!mainCRTStartup() Line 17	D

Have you seen anything like this before?

Dec 05 2015

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

On 05.12.2015 21:50, Andrew LaChance wrote:
 On Thursday, 5 November 2015 at 22:12:39 UTC, Rainer Schuetze wrote:
 On 01.11.2015 11:29, Rainer Schuetze wrote:
 Hi,

 I just uploaded a beta for the next release of Visual D.

 You can find the list of changes and the installer here:

 https://github.com/D-Programming-Language/visuald/releases/tag/v0.3.43-beta1



 Rainer

 Now updated to a new beta:

 https://github.com/D-Programming-Language/visuald/releases/tag/v0.3.43-beta2

 Thank you for the update!  It fixed my link issues.

 I have found a very strange issue with I *think* visual D.  I have
 condensed into a very small repro here: http://1drv.ms/1Oai14L (entire
 solution).  If I build and run on x86 build config, everything is fine.
 But on x64, debugging (with Debug x64 config) will cause an exception
 somewhere on this line:

 writeln(AnotherColor.Red.stringof); // AnotherColor is an enum

 But if I were to run the exe from the command line it is fine. Release
 version is fine too.  Also, it is fine if I put a breakpoint on the
 first line in main.d and then step over each line.  But hitting continue
 will throw an exception.  I'm not exactly sure where the exception comes
 from:

      DPlayground.exe!_D2rt6dmain211_d_run_mainUiPPaPUAAaZiZ6runAl
MFZ9__lambda1MFZv() + 0x32 bytes    D

      DPlayground.exe!_D2rt6dmain211_d_run_mainUiPPaPUAAaZiZ7tryExecMFMDFZvZv()
+ 0x6f bytes    D

      DPlayground.exe!_D2rt6dmain211_d_run_mainUiPPaPUAAaZiZ6runAllMFZv()
 + 0x3c bytes    D

      DPlayground.exe!_D2rt6dmain211_d_run_mainUiPPaPUAAaZiZ7tryExecMFMDFZvZv()
+ 0x6f bytes    D
       DPlayground.exe!_d_run_main() + 0x421 bytes    D
       DPlayground.exe!__entrypoint.main( int argc, char** argv ) + 0x22
 bytes    D
     DPlayground.exe!invoke_main() Line 75    D

       DPlayground.exe!__scrt_common_main_seh() Line 264 + 0x5 bytes    D
       DPlayground.exe!__scrt_common_main() Line 309    D
       DPlayground.exe!mainCRTStartup() Line 17    D

 Have you seen anything like this before?

I can reproduce the problem here. This is caused by the breakpoint 
modifying the code at a wrong instruction address, which leads to a bad 
stack cleanup.

As this happens for all debug engines, it is very likely due to bad 
debug information emitted by dmd.

Dec 07 2015

Andrew LaChance <lachance.ak gmail.com> writes:

On Monday, 7 December 2015 at 08:27:54 UTC, Rainer Schuetze wrote:
 On 05.12.2015 21:50, Andrew LaChance wrote:
 [...]

 I can reproduce the problem here. This is caused by the 
 breakpoint modifying the code at a wrong instruction address, 
 which leads to a bad stack cleanup.

 As this happens for all debug engines, it is very likely due to 
 bad debug information emitted by dmd.

Oh wow, that sounds nasty!  Is there a bug in dmd for this?

Dec 09 2015

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

On 10.12.2015 05:56, Andrew LaChance wrote:
 On Monday, 7 December 2015 at 08:27:54 UTC, Rainer Schuetze wrote:
 On 05.12.2015 21:50, Andrew LaChance wrote:
 [...]

 I can reproduce the problem here. This is caused by the breakpoint
 modifying the code at a wrong instruction address, which leads to a
 bad stack cleanup.

 As this happens for all debug engines, it is very likely due to bad
 debug information emitted by dmd.

 Oh wow, that sounds nasty!  Is there a bug in dmd for this?

I have added a report here: https://issues.dlang.org/show_bug.cgi?id=15432

Dec 10 2015

Andrew LaChance <lachance.ak gmail.com> writes:

On Thursday, 5 November 2015 at 22:12:39 UTC, Rainer Schuetze 
wrote:
 Now updated to a new beta:

 https://github.com/D-Programming-Language/visuald/releases/tag/v0.3.43-beta2

Hello!  A small issue I noticed: If I create a configuration for 
x64, visual studio doesn't know that this means version(Win64) is 
true and version(Win32) is false, as seen here:

http://imgur.com/Gui9rYz

I verified that a pointer (using .sizeof) is 8 bytes with x64 
configuration and 4 bytes with x86 configuration, so it's just 
the editor that doesn't know.

Dec 05 2015

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

On 06.12.2015 01:16, Andrew LaChance wrote:
 On Thursday, 5 November 2015 at 22:12:39 UTC, Rainer Schuetze wrote:
 Now updated to a new beta:

 https://github.com/D-Programming-Language/visuald/releases/tag/v0.3.43-beta2

 Hello!  A small issue I noticed: If I create a configuration for x64,
 visual studio doesn't know that this means version(Win64) is true and
 version(Win32) is false, as seen here:

 http://imgur.com/Gui9rYz

 I verified that a pointer (using .sizeof) is 8 bytes with x64
 configuration and 4 bytes with x86 configuration, so it's just the
 editor that doesn't know.

Thanks for reporting. You can also file issues at 
https://issues.dlang.org/enter_bug.cgi?product=D

It seems that this happens for files that are not part of a project. It 
can be ambiguous what versions have to be defined for the source file, 
but Win64 should be taken from the selected platform. I remember having 
trouble detecting this setting for "compile and run", too.

Dec 07 2015

D Programming

C/C++ Programming

Other

digitalmars.D.ide - Visual D 0.3.43 beta1 available