jdk/make/netbeans/awt2d/README

*** 37,58 ****
        To get a list of variables you most likely will need to override
        to make the the build work in NetBeans, you can do something like this 
        (on Windows):
          #>env | grep ALT
          ALT_JDK_IMPORT_PATH=c:/devtools/java/jdk1.7.0
-         ALT_DXSDK_PATH=c:/devtools/DirectX/DXSDK_Dec06
          ALT_BOOTDIR=c:/DevTools/java/jdk1.6.0
  
        If your build is a FASTDEBUG build, don't forget
        to set FASTDEBUG=true in the property file as well so that what you 
        have built from the terminal matches what will be built from NetBeans.
  
        Set "make.options" in your build.properties
        accordingly:
          make.options=\
              ALT_JDK_IMPORT_PATH=c:/devtools/java/jdk1.7.0 \
-             ALT_DXSDK_PATH=c:/devtools/DirectX/DXSDK_Dec06 \
              ALT_BOOTDIR=c:/DevTools/java/jdk1.6.0 \
              FASTDEBUG=true
          make=c:/devtools/cygwin/bin/make
  
     4. Windows only: make sure you either call vcvars32.bat
--- 37,56 ----
*** 173,183 ****
    ../../build/windows-i586/tmp/sun/sun.awt/awt/obj_gO;
    ../../build/windows-i586/tmp/sun/sun.awt/jpeg/CClassHeaders;
    ../../build/windows-i586/tmp/sun/sun.awt/splashscreen/CClassHeaders;
    ../../build/windows-i586/tmp/sun/sun.font/fontmanager/CClassHeaders;
    ../../build/windows-i586/tmp/sun/sun.font/t2k/CClassHeaders;
-   C:/DevTools/DirectX/DXSDK_Dec06/Include;
    C:/devtools/VS2003/SDK/v1.1/include;
    C:/devtools/VS2003/VC7/ATLMFC/INCLUDE;
    C:/devtools/VS2003/VC7/INCLUDE;
    C:/devtools/VS2003/VC7/PlatformSDK/include;
    C:/devtools/VS2003/VC7/PlatformSDK/include/prerelease;
--- 171,180 ----
*** 186,196 ****
    into the text field instead of entering them one by one)
  
    Note that most paths are relative to the native project directory - 
    this helps if you decide to relocate the workspace later. The ones that 
    aren't relative are paths to external include directories, like those 
!   of the Platform SDK, DirectX SDK.
    On Unix platforms these may be directories like /usr/include.
  
    The parser must know some defines to correctly parse the source files,
    these can also be obtained from the log file. For example, on Windows
    x86 with debugging enabled, the defines would be something like this:
--- 183,193 ----
    into the text field instead of entering them one by one)
  
    Note that most paths are relative to the native project directory - 
    this helps if you decide to relocate the workspace later. The ones that 
    aren't relative are paths to external include directories, like those 
!   of the Platform SDK.
    On Unix platforms these may be directories like /usr/include.
  
    The parser must know some defines to correctly parse the source files,
    these can also be obtained from the log file. For example, on Windows
    x86 with debugging enabled, the defines would be something like this: