[webkit-dev] build system for wince port

Patrick Roland Gansterer paroga at paroga.com
Wed Jan 6 02:28:50 PST 2010

David Kilzer:
> On Thu, December 24, 2009 at 1:51:43 AM, Patrick Roland Gansterer wrote:
> > On Thu, Dec 24, 2009 at 02:53:18, Adam Barth:
> > > I'm worried that the port will rot without an active maintainer, no
> > > matter which build system you choose.
> >
> > If i choose my preferred solution, there will be many changes in the
> > current sln/vcproj/vsprops files. Who is maintaining this files at the
> > moment? I'd like to hear his/her opinion on this before.
> You can use svn/git log to see who commits changes to these files.  I know
>  Apple uses them for their Windows build, but we're on break until Jan 4,
>  so please don't expect a reply until after that date.  (I don't work on
>  the Windows port much, so I don't have an opinion about your proposal.)
Break is over and I didn't find a better working buildsystem for WincE than 
vcproj in the meantime. :-/

In the current trunk the vcproj files all use the Win32 defines. Because Win32 
an WinCE have some parts in common i'd like to split the current vsprop files. 
To keep the vcproj files readable i prefer to add a second vcproj file for 
e.g. JavaScriptCore and a solution file with this new vcproj file.
I'd like to start with the JavaScriptCore for "STANDARDSDK_500 (ARMV4I)".

The last blocker for WinCE JavascriptCore is the missing TextCodec (see 
https://bugs.webkit.org/show_bug.cgi?id=32169) with a pending review request 
for a month.

- Patrick

More information about the webkit-dev mailing list