Compile/link Win64

Nick Sabalausky SeeWebsiteToContactMe at semitwist.com
Fri Jan 10 13:47:23 PST 2014


On 1/10/2014 3:56 PM, Rainer Schuetze wrote:
>
>
> On 10.01.2014 21:34, Nick Sabalausky wrote:
>> On 1/10/2014 3:26 PM, Nick Sabalausky wrote:
>>> On 1/10/2014 3:19 PM, Brad Anderson wrote:
>>>>
>>>> I don't have VC2008 so I unfortunately could not test while I was
>>>> working on the installer/sc.ini update. Rainer says 2008 does work
>>>> though. With modern VC there is a vcvars32.bat and vcvars64.bat to
>>>> choose whether to use the 32-bit or 64-bit toolchain. What is the value
>>>> of %WindowsSdkDir% within your vcvars.bat command prompt?
>>>
>>> Hmm, that's strange, %WindowsSdkDir% isn't set. I thought vcvarsall.bat
>>> was supposed to set up all of that.
>>>
>>
>> It's also not set if I go into VS's [idiotic] "Visual Studio Command
>> Prompt" either. :/
>>
>
> IIRC this variable is read from the registry by vcvars*.bat, but
> uninstalling any SDK deletes the registry entry. So if you had multiple
> SDK versions installed, but removed one, the variable will no longer be
> set.

Hmm, I hadn't ever uninstalled it.

Regardless, *now* I've just uninstalled and reinstalled the Windows SDK, 
and re-ran vcvarsall.bat. The %WindowsSdkDir% is now set, but I'm still 
getting the same problem.

The %WindowsSdkDir% is set to "C:\Program Files (x86)\Microsoft 
SDKs\Windows\v8.0A", but there doesn't appear to be much in there (Just 
a "Bootstrapper\Packages" directory with not much inside it either). I 
don't think it installed correctly. There doesn't appear to be any other 
Windows SDK installation AFAICT either. Stupid f#&*^&# microsoft tools...

In any case, the issue I was hunting down turned out to be Posix-related 
instead of 64-bit-related anyway, so I'm not going to deal with this 
anymore for the time being.



More information about the Digitalmars-d-learn mailing list