On 01/24/2013 01:08 AM, dale wrote:
I am following these helpful suggestions, but still having trouble
linking properly. I have Visual Studio 10 and its 64-bit extension
installed, and I believe the amd64\link.exe is getting called, but I
must have something configured incorrectly, because it does not appear
to find all of the libraries correctly.
C:\prj\D>dmd -m64 hello64B.d
C:\d\dmd2\windows\bin\..\lib\shell32.lib : warning LNK4003: invalid
library format; library ignored
C:\d\dmd2\windows\bin\..\lib\kernel32.lib : warning LNK4003: invalid
library format; library ignored
phobos64.lib(dmain2_4a8_47b.obj) : error LNK2019: unresolved external
symbol GetCommandLineW referenced in function _d_run_main
phobos64.lib(dmain2_4a8_47b.obj) : error LNK2019: unresolved external
symbol CommandLineToArgvW referenced in function _d_run_main
...
And zillions more "unresolved externals" follow.
Why is it trying to include shell32.lib and kernel32.lib for a 64-bit
app? Is that a problem?
Any hints as to what I'm missing?
Thanks,
dale
I think this has come up before, and it has something to do with some
environment variables set in sc.ini and the MS linker picking up the
libs supplied be dmd for win32 because of it.
--
Mike Wey
