Skip to main content
October Donation Campaign Donate Now

Setting SWT windows native build setup

Software needed for setting up windows native build

  1. Microsoft 'Visual Studio 2008'

  2. Microsoft 'Windows Server 2003 SP1 SDK', link to download page

  3. JDK8 64bit and 32bit (IBM JDK preferred), link to download page

  4. Webkit SDKs:

    1. WebKit-r72896

    2. WebKitSupportLibrary

    Disclaimer:

    Note these Webkit SDKs are an older version being consumed by SWT native build process and Webkit build binaries are no more available for download in public Webkit download page.

    But WebKit-r72896 sources are still avilable for download in public main link and also on backup link.

  5. Cygwin [Optional for local setup]

Note: MSDN developer license is a pre-requisite for Microsoft softwares. [Also work in-progress to move to "Visual Studio C++ Express 2008" which doesn't require MSDN license via bugzilla bug 521927]

Steps to set up Windows native build:

  1. [Optional for local setup] Install and configure Cygwin SSH Server on Windows.

    Note: Make sure 'openssh' package is also installed.

    For more details on how to configuring SSH refer: link

  2. [Optional for local setup] Configure the machine for password-less SSH authentication with the Hudson machine.

    For more details you can refer: public guide

    Sharing some key steps below(which I recall):

    • Generate the 'dsa' public/private key from your "swtbuild" account from windows machine.

    • Now login to the Hudson machine with "swtbuild" account.

    • Copy the public keys and register then on the Hudson machine.. this should enable password-less authentication.

  3. "swt-builddir" can be copied from one of the existing windows build machine, recommended path is C:\BUILD\swt-builddir

    This directory contains various libraries like Windows SDKs, Visual Studio libraries, JDK and libraries for compiling Webkit etc..

    or

    Create your on 'swt-builddir' with below like directory structure:

    • Create directory 'C:\BUILD\swt-builddir'

    • Install Windows Server 2003 SPI SDK in 'C:\BUILD\swt-builddir\MSSDKs\Windows Server 2003 SP1 SDK'

    • Install MS VS2008 in 'C:\BUILD\swt-builddir\MSVCs\Microsoft Visual Studio 8'

    • Unzip the two Webkit SDKs into 'C:\BUILD\swt-builddir\webkit' as below directories:

      1. 'C:\BUILD\swt-builddir\webkit\WebKit-r72896'

      2. 'C:\BUILD\swt-builddir\webkit\WebKitSupportLibrary'

      Note: SWT's Webkit support exists for SWT 32bit on Windows, so Webkit SDKs are consumed only by the SWT 32bit build process.

    • Install/Unzip IBM(preferred) JDK8 64bit in 'C:\BUILD\swt-builddir\ibm-java-sdk-80-win-x86_64\sdk'

    • Install/Unzip IBM(preferred) JDK8 32bit in 'C:\BUILD\swt-builddir\ibm-java-sdk-80-win-i386\sdk'

  4. For local testing, Run as Ant build below file with 'build_libraries' as target(assuming SWT setup is in place):

    ${workspace_loc:/org.eclipse.swt.win32.win32.x86_64/build.xml}

    For building windows native build for 32bit, you need to convert the source to 32bit first, by running 'replace.64.to.32' target

    Once sources are converted to 32bit you can run the 'build_libraries' target for ${workspace_loc:/org.eclipse.swt.win32.win32.x86/build.xml}

  5. [Optional for local setup] Now you can point the Windows hudson job to this machine and trigger a native build.

    Note: For testing purpose from hudson, temporarily turn the nativeChanges flag to 'true' to force a native build compilation.

Back to the top