Somewhat wonkier Windows problem

David Chase at
Thu May 23 17:12:19 UTC 2013

On 2013-05-22, at 8:44 PM, Tim Bell <tim.bell at> wrote:
> Here is a pointer to the source changes I needed to make, so far:
> You will need to run 'bash common/autoconf/' after applying the patch from the webrev.
> It has also been reported that the free VS2012 'Express' edition does not include the 64-bit compiler, so you will be able to build 32-bit only.   I have not verified that.

A report back on your patch, with minor testing:

This worked:

jdk8tl + closed + your patch
Windows 7
VS 2012 Express, x64 Command Prompt
DirectX SDK 2010
REBASE=/usr/bin/rebase bash configure --with-boot-jdk=...1.7.0_21

The java -showversion happily declared that it was 64-bit, and I ran some of the applet demos, and they all seemed to work.

Things that fail, so far (each line describes a different failure):
DirectX SDK 2006 (because it makes a mess of the path)
VS 2012 Express, 32-bit Command Prompt (because it fails to find x86 direct X, though it is there)

Are there more experiments that you think I should try?
I am most interested in working around the 32-bit problem in configure,
then in testing if it still works properly with VS2010, 32 and 64,
then in testing if it works with the closed bits missing.

As near as I can tell, the combinations to consider for "the future" are at minimum

{ VS2010, VS2012, VS2012sp1} x {express, professional} x {32, 64} x {open, closed}

Everything there has to should build and pass a bunch of tests once.

I'd love to stick with a single modern version of DXSDK.


More information about the build-dev mailing list