Changes between Version 17 and Version 18 of WinCE


Ignore:
Timestamp:
Jan 29, 2013 1:04:11 PM (9 years ago)
Author:
Patrick Gansterer
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • WinCE

    v17 v18  
    2727We use [http://cmake.org/ CMake] as our build system. You '''don't''' need a full Cygwin environment like Apple's Windows port, but the following tooles are required:
    2828
    29  * [http://gnuwin32.sourceforge.net/downlinks/bison.php Bison]
    3029 * [http://gnuwin32.sourceforge.net/downlinks/gperf.php GPerf]
    31  * [http://gnuwin32.sourceforge.net/downlinks/flex.php Flex]
     30 * [http://sourceforge.net/projects/winflexbison/files/latest/download Win flex-bison]
    3231 * [http://www.activestate.com/activeperl/downloads ActiveState Perl]
    3332 * [http://www.python.org/download/ Python 2.x]
     
    3534Please '''install these tools in a path without spaces''' (i.e. '''not in "C:\Program Files"''')
    3635
    37 Make sure the GnuWin32 packages are in your PATH as well as Perl and Python.
    38 If you have Cygwin's bin directory in your path, make sure that it comes after ActiveState Perl and GnuWin32. You might have to remove it completely from your PATH if you have problems while building.
     36Make sure that all listed tools are accessible via your PATH.
     37If you have Cygwin's bin directory in your path, make sure that it comes after the paths to the listed tools. You might have to remove it completely from your PATH if you have problems while building.
    3938
    4039=== Windows CE SDK ===
     
    4645=== CMake ===
    4746
    48 Because the offical CMake has no support for Windows CE at the moment, we need to use a special CMake version.
    49 
    50 Please install the CMake version 2.8.3 from http://cmake.org/cmake/resources/software.html.
    51 
    52 ==== Build CMake with WinCE support (recommended) ====
    53 
    54 To build your own CMake you need to get the code from the gitorious repository.
    55 
    56 {{{
    57 git clone git://gitorious.org/~paroga/cmake/parogas-cmake.git
    58 git checkout wince
    59 }}}
    60 
    61 Then you can build it with the following commands.
    62 
    63 {{{
    64 mkdir CMakeBuild
    65 cd CMakeBuild
    66 cmake \path\to\source
    67 cmake --build .
    68 }}}
    69 
    70 After this you have you own {{{cmake.exe}}} in the {{{bin}}} directory. Make sure to use this one when creating the project files for Windows CE. You also need to use the {{{Modules}}} directory form the gitorious repository. The easiest way is to copy {{{cmake.exe}}} and the whole {{{Modules}}} directory into you CMake installation directory (C:\Program Files\CMake 2.8).
    71 
    72 ==== Use provided binary (not secure) ====
    73 
    74 '''This is not a secure source for a binary, so we recommend to build it yourself!
    75 
    76 If you are not able to clone the repository and/or compile CMake on your host it is possible to use the provided binary on this page. You only need to extract [attachment:cmake-2.8.3-ce-win32-x86-diff.zip] in you CMake installation directory. It will replace the {{{bin/cmake.exe}}} and change a few Modules files.
     47Starting with CMake 2.8.11 Windows CE is supported out of the box. Until the release of that version a [http://www.cmake.org/files/dev/ Nightly Binary] of CMake can be used.
    7748
    7849=== Build WebKit ===
    7950
    80 When you have a working CMake with WinCE support you can generate a Visual Studio Solution out of the CMake files.
     51When you have installed all tools correctly you can generate a Visual Studio Solution out of the CMake files.
    8152
    8253{{{
    8354mkdir WebKitBuild
    8455cd WebKitBuild
    85 cmake -G "Visual Studio 8 2005" -DCMAKE_WINCE_SDK="STANDARDSDK_500 (ARMV4I)" -DPORT=WinCE -D3RDPARTY_DIR=/path/to/webkit-thirdparty \path\to\source
     56cmake -G "Visual Studio 8 2005 STANDARDSDK_500 (ARMV4I)" -DPORT=WinCE -D3RDPARTY_DIR=/path/to/webkit-thirdparty \path\to\source
    8657}}}
    8758
    8859'''ATTENTION:''' The {{{3RDPARTY_DIR}}} argument needs slash as separator, while the path to the source needs backslash.
    8960
    90 This will generate a WebKit.sln in the WebKitBuild directory from the sourcecode in {{{\path\to\source}}}. You can change the generator to {{{Visual Studio 9 2008}}} if you want to generate Visual Studio 2008 projects. It is also possible to select an other Windwos CE SDK when you replace the {{{STANDARDSDK_500 (ARMV4I)}}} with the name of SDK you want to use.
     61This will generate a WebKit.sln in the WebKitBuild directory from the sourcecode in {{{\path\to\source}}}. You can replace {{{Visual Studio 8 2005}}} with {{{Visual Studio 9 2008}}} if you want to generate Visual Studio 2008 projects. It is also possible to select an other Windwos CE SDK when you replace the {{{STANDARDSDK_500 (ARMV4I)}}} with the name of SDK you want to use.
    9162
    9263Now you should be able to open the solution and build it. You also can simply type {{{cmake --build . --config Release}}} in your build directory.
     
    9970C:\>mkdir WebKitBuild
    10071C:\>cd WebKitBuild
    101 C:\WebKitBuild>cmake -G "Visual Studio 8 2005" -DCMAKE_WINCE_SDK="STANDARDSDK_500 (ARMV4I)" -DPORT=WinCE -D3RDPARTY_DIR=C:/webkit-thirdparty C:\WebKit
     72C:\WebKitBuild>cmake -G "Visual Studio 8 2005 STANDARDSDK_500 (ARMV4I)" -DPORT=WinCE -D3RDPARTY_DIR=C:/webkit-thirdparty C:\WebKit
    10273C:\WebKitBuild>cmake --build . --config Release
    10374}}}
     75
     76Additonal information about cross compiling for Windows CE can be found at [http://www.cmake.org/Wiki/CMake_Cross_Compiling#Cross_compilation_for_Windows_CE http://www.cmake.org/Wiki/CMake_Cross_Compiling].
    10477
    10578==== Possible Builderrors ====