Changes between Initial Version and Version 1 of WinCE

Jul 24, 2010 6:22:46 PM (12 years ago)



  • WinCE

    v1 v1  
     3= Windows CE Port of WebKit =
     5WebKit is an open source web browser engine. WebKit WinCE is a project aiming at porting this fabulous engine to Windows CE.
     7The WinCE port of WebKit currently compiles on Windows.
     10== Status ==
     12WebKit WinCE port is based on the work by Torche Mobile and is currently under development.
     14== Getting the Source ==
     15As the port is not completely upstreamed yet, one can get only the partial source code from official [ WebKit repository]. Instead, we are hosting our development in
     18git clone git://
     21Third party libraries are under "3rdparty" directory.
     24== Build ==
     26We use [ CMake] as our build system. You don't need a full Cygwin environment, but the following tooles are required:
     28 * bison
     29 * flex
     30 * gperf
     31 * perl
     32 * python
     34=== Windows CE SDK ===
     36Visual Studio 2005 (No Express Edition!) with a Windows CE SDK is required to build the binary. Visual Studio 2008 should work too.
     38You can find the Windows CE 5 Standard SDK at Any other SDK should work too.
     40=== Build CMake with WinCE support ===
     42Because the offical CMake has not support for Windows CE at the moment, we need to use the CMake version from AlexeyS.
     45git clone git://
     48Follow the instructions in the Readme.txt to build a CMake with WinCE support.
     50=== Build WebKit ===
     52When you have a working CMake with WinCE support you can generate a Visual Studio Solution out of the CMake files.
     55mkdir WebKitBuild
     56cd WebKitBuild
     57cmake -G "Visual Studio 8 2005 for Windows CE" -DPORT:STRING=WinCE -DCMAKE_WINDOWS_CE_PLATFORM:STRING="STANDARDSDK_500 (ARMV4I)" C:\WebKitSource
     60This will generate a WebKit.sln in the WebKitBuild directory from the sourcecode in C:\WebKitSource. You can change the generator to {{{Visual Studio 9 2008 for Windows CE}}} 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.
     62Now you should be able to open the solution and build it.
     64==== Possible Builderrors ====
     65Because of the fact that the buildsystem isn't 100% finished you may see one or more of the following errors:
     68example.h(123) : fatal error C1083: Cannot open include file: 'ExampleNames.h': No such file or directory
     70This should happen only with the first build, because of some missing dependencies. When you build the solution a second time (wait until the first is finished!) they will be gone.
     73Creating library...
     74LIB : warning LNK4068: /MACHINE not specified; defaulting to X86
     75example.obj : fatal error LNK1112: module machine type 'ARM' conflicts with target machine type 'X86'
     77To fix this issue open the project properties and navigate to "Configuration Properties" / "Librarian" / "Command Line" and add {{{/MACHINE:ARM}}} into the "Additional options".
     80example.lib(example.obj) : error LNK2005: "void * __cdecl operator new(unsigned int)" (??2@YAPAXI@Z) already defined in coredll.lib(COREDLL.dll)
     81example.lib(example.obj) : error LNK2005: "void __cdecl operator delete(void *)" (??3@YAXPAX@Z) already defined in coredll.lib(COREDLL.dll)
     83If you get tons of this messages you hit Moving all windows libraries after the WebKit libraries in "Configuration Properties" / "Linker" / "Additional Dependencies" will solve this problem.
     85== Questions and feedback ==
     87If you have questions please send an email to Patrick Gansterer <>