Thanks for your suggestion. In VS 2017, the Property Pages have
a configuration drop down list box which allows you select among
Active(Debug), Debug, Release, and All Configurations. Mine was
set to All Configurations, leaving me to believe that setting
something would apply to both Debug
If I remember correctly VS studio has different release and debug
configurations for both compiler and linker. If release works but
debug doesnt make sure that when you add things to one to also
add to another
Thanks for very prompt reply and apologies for my extremely late
answer. Due to the current situation, I now have much more time
to work on this.
In short, I upgraded to the most recent (1.20.1) LDC compiler,
the most recent (0.52.0) Visual D, but am staying with VS 2017.
When I try to
On 08/09/2019 00:30, malpropism wrote:
> I just ported my Java application to D, got it to compile, but not to link.
>
> I'm using Windows 10 64 bit, DMD 2.088.0 , Visual D 0.50.1. This would
> be a C/C++ project in Visual Studio with only D code.
>
> With my first attempt, I'm missing 65
PS: Here are the actual linker errors:
1>phobos64.lib(gc_23c0_122.obj) : error LNK2001: unresolved
external symbol _fltused
1>phobos64.lib(ti_float_2680_3f3.obj) : error LNK2001: unresolved
external symbol _fltused
1>phobos64.lib(hash_d99_76c.obj) : error LNK2001: unresolved
external symbol
I just ported my Java application to D, got it to compile, but
not to link.
I'm using Windows 10 64 bit, DMD 2.088.0 , Visual D 0.50.1. This
would be a C/C++ project in Visual Studio with only D code.
With my first attempt, I'm missing 65 externals, 328 errors.
I added these two files
