Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8092386

Consider using FXC from Visual Studio 2013 instead of DirectX SDK

    XMLWordPrintable

    Details

    • Type: Enhancement
    • Status: Resolved
    • Priority: P4
    • Resolution: Fixed
    • Affects Version/s: 9
    • Fix Version/s: 9
    • Component/s: javafx
    • Labels:
      None

      Description

      As Felipe noted in RT-38475 the only thing we still use from the DirectX SDK is the FXC tool, which is now shipped as part of Visual Studio. We could remove the dependency on the DirectX SDK if we switched to using the one from Visual Studio.

      We would need to resolve the warnings that result from running the newer FXC on our shaders.

      C:\cygwin64\home\demo\repos\8u-dev\rt\modules\graphics\build\generated-src\jsl-prism\com\sun\prism\d3d\hlsl\Solid_TextureSecondPassLCD_AlphaTest.hlsl(18,10-64): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them
      C:\cygwin64\home\demo\repos\8u-dev\rt\modules\graphics\build\generated-src\jsl-prism\com\sun\prism\d3d\hlsl\Solid_TextureSecondPassLCD_AlphaTest.hlsl(24,5-54): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them
      C:\cygwin64\home\demo\repos\8u-dev\rt\modules\graphics\build\generated-src\jsl-prism\com\sun\prism\d3d\hlsl\Solid_TextureSecondPassLCD.hlsl(24,5-54): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              vadim Vadim Pakhnushev
              Reporter:
              kcr Kevin Rushforth
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Imported: