On Tuesday, 14 February 2017 at 14:11:31 UTC, Sönke Ludwig wrote:
It's a quite frequent issue to get unresolved externals on
Windows, because the lib files of the Windows platform SDK are
still stuck at Windows XP age. It would make a lot of sense to
update those to the latest Windows 10 SDK,
Am 15.02.2017 um 07:43 schrieb Mike Parker:
On Tuesday, 14 February 2017 at 20:14:32 UTC, Jonathan M Davis wrote:
I would point out that we technically don't support Windows XP. If you
use D with it, and it works for you, great, but you're on your own.
Which is why the OMF libs need to be
On Tuesday, 14 February 2017 at 20:14:32 UTC, Jonathan M Davis
wrote:
I would point out that we technically don't support Windows XP.
If you use D with it, and it works for you, great, but you're
on your own.
Which is why the OMF libs need to be updated. They're ancient!
That being
On Tuesday, February 14, 2017 17:15:59 kinke via Digitalmars-d wrote:
> On Tuesday, 14 February 2017 at 14:11:31 UTC, Sönke Ludwig wrote:
> > It's a quite frequent issue to get unresolved externals on
> > Windows, because the lib files of the Windows platform SDK are
> > still stuck at Windows XP
On Tuesday, 14 February 2017 at 14:11:31 UTC, Sönke Ludwig wrote:
It's a quite frequent issue to get unresolved externals on
Windows, because the lib files of the Windows platform SDK are
still stuck at Windows XP age. It would make a lot of sense to
update those to the latest Windows 10 SDK,
It's a quite frequent issue to get unresolved externals on Windows,
because the lib files of the Windows platform SDK are still stuck at
Windows XP age. It would make a lot of sense to update those to the
latest Windows 10 SDK, but I couldn't find a place where those are
present physically,
