Somewhat wonkier Windows problem

Erik Joelsson erik.joelsson at oracle.com
Fri May 24 07:23:32 UTC 2013



On 2013-05-23 20:10, David Chase wrote:
> One change to add (a by-hand "diff") to common/autoconf/toolchain_windows.m4 :
>
>    AC_MSG_CHECKING([for DirectX SDK lib dir])
>    if test "x$with_dxsdk_lib" != x; then
>      DXSDK_LIB_PATH="$with_dxsdk_lib"
>    elif test "x$OPENJDK_TARGET_CPU" = "xx86_64"; then
>      DXSDK_LIB_PATH="$dxsdk_path/Lib/x64"
> +  elif test -d "$dxsdk_path/Lib/x86"; then
> +    DXSDK_LIB_PATH="$dxsdk_path/Lib/x86"
>    else
>      DXSDK_LIB_PATH="$dxsdk_path/Lib"
>    fi
>
> This allows 32-bit configure with DirectX SDK 2010.
> This assumes that DXSDK 2004 lacks any subdirectory Lib/x86; I haven't seen it yet.
>
Yes, newer directx sdks have that subdir while the only one we support 
doesn't. That's why I didn't add that check. The 2d team is quite 
adamant about that being the only working directx sdk and any talk about 
changing it should be with them, not the build team.

If we want to change directx sdk, we should first consider removing the 
dependency completely since technically, everything that's needed is 
installed with visual studio and/or the normal windows sdk.

/Erik
> It built, I ran an applet demo, so some minor success there, too.
>
> I'm keeping notes on what works.
>
> More later.
>
> David
>
>
>



More information about the build-dev mailing list