MSSDK61 in windows-amd64 build

[Kelly O'Hair]

FYI...

The Windows 64bit builds are still formally using the old SDK (April 2005),
so what little I have managed to get to work with the newer SDKs is
all a bit up in the air.

v6.0A should work, maybe even v7.0, but I only tested with v6.1.

These newer SDKs contain a 64bit version of Visual Studio 2008, so
lots of the work done by Tim Bell to allow for 32bit builds with
VS2008 is needed to make this 64bit Windows build to work.
Further work on Windows 64bit upgrading has been waiting on the
completion of the 32bit Windows upgrade to VS2008 and XP.

---

Max (Weijun) Wang wrote:
>> Is there some reason you stay with v6.0A, rather than upgrading to
>> $(_program_files)/Microsoft SDKs/Windows/v6.1/  ?
> 
> No reason. 6.0a is the SDK that comes with VS2008, and I didn't realize 
> an upgrade is needed.

Could you explain what you mean by 'comes with VS2008'?
On 64bit Windows, as I recall, you just install the Microsoft SDK (I installed v6.1)
and that installs a 64bit VS2008. Or I thought that was the case.

I've only seen the v6.0A show up on 32bit Windows systems when installing
VS2008.

Did you explicitly install the VS2008 product on 64bit Windows?
Either purchased or the Express one?

-kto

> 
> Max
> 
> On Dec 15, 2009, at 11:00 AM, Tim Bell wrote:
> 
>> Max (Weijun) Wang wrote:
>>> Hi Kelly
>>>
>>> This is the first time I build windows-amd64 with Visual Studio 2008.
>>>
>>> At the freetypecheck stage, it cannot find the MSSDK61 path. According
>>> to make/common/shared/Defs-windows.gmk, it's something like --
>>>
>>>    $(_program_files)/Microsoft SDKs/Windows/v6.1/
>>>
>>> but on my system there's only C:\Program Files\Microsoft SDKs\Windows
>>> \v6.0A, and there's a WINDOWSSDKDIR env variable pointing to it.
>>>
>>> Is version 6.1 a must? I've manually point MSSDK61 to $WINDOWSSSDKDIR
>>> and the build is running now.
>>
>> When using VS 2008, you can probably get away with any version 6.x SDK.
>>
>> I see that jdk/make/common/shared/Defs-windows.gmk hunts around and
>> makes a few guesses when looking for an SDK... but there is no
>> ALT_PLATFORM_SDK (or equivalent) variable so you can override it.
>>
>> Is there some reason you stay with v6.0A, rather than upgrading to
>> $(_program_files)/Microsoft SDKs/Windows/v6.1/  ?
>>
>> HTH-
>>
>> Tim
>