• evilrat (15/15) Nov 23 2013 Greetings,
• Jesse Phillips (2/18) Nov 24 2013 You should file bugs for this and include a failing example.

"evilrat" <evilrat666 gmail.com> writes:

Greetings,
straight to the problem - latest release(2.064.2) has a nasty bug 
with distribution. official installer missing 
Runtime.initialize() and Runtime.terminate() symbols in 
phobos.lib for x64 version.

i tried to use rt_init() and rt_term() and at first it looks 
working, but then i have some code(including COM interface calls) 
and writeln's failing (string enforcement fails), which is 
symptoms that runtime or GC not initialized.

unfortunately i can't continue using x86(yes it is working) until 
VisualD get fixed for VS 2013... and if i remove winmain and use 
plain main it is all works again. so is there any workaround for 
this problem without rebuilding whole DMD & phobos?

(my system - windows 8.1 x64, VS 2013, windows sdk 8.1, dmd 
2.064.2 )

"Jesse Phillips" <Jesse.K.Phillips+D gmail.com> writes:

On Saturday, 23 November 2013 at 08:15:31 UTC, evilrat wrote:
 Greetings,
 straight to the problem - latest release(2.064.2) has a nasty 
 bug with distribution. official installer missing 
 Runtime.initialize() and Runtime.terminate() symbols in 
 phobos.lib for x64 version.

 i tried to use rt_init() and rt_term() and at first it looks 
 working, but then i have some code(including COM interface 
 calls) and writeln's failing (string enforcement fails), which 
 is symptoms that runtime or GC not initialized.

 unfortunately i can't continue using x86(yes it is working) 
 until VisualD get fixed for VS 2013... and if i remove winmain 
 and use plain main it is all works again. so is there any 
 workaround for this problem without rebuilding whole DMD & 
 phobos?

 (my system - windows 8.1 x64, VS 2013, windows sdk 8.1, dmd 
 2.064.2 )

You should file bugs for this and include a failing example.