Re: [webkit-dev] build system for wince port
Hi, Can someone please decide how i should create a WinCE build system! Adam Roben: That sounds like a maintenance headache. Any new files will have to be added to both .vcproj files. Of course! The Apple and Cairo/libCURL ports of WebKit are already sharing .vcproj files. Can WinCE share these files, too? It is possible, but i'm not sure if it's the best solution: There will uncountable ExcludeFromBuild in the vcproj files and if we will add additional platforms i will grow further. If you add the STANDARDSDK_500 (ARMV4I) platform to the solution it might throw a warning if the SDK isn't installed. - Patrick ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] build system for wince port
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 ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] build system for wince port
On Jan 6, 2010, at 5:28 AM, Patrick Roland Gansterer wrote: 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. That sounds like a good idea. 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. That sounds like a maintenance headache. Any new files will have to be added to both .vcproj files. The Apple and Cairo/libCURL ports of WebKit are already sharing .vcproj files. Can WinCE share these files, too? -Adam ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] build system for wince port
Adam Roben: That sounds like a maintenance headache. Any new files will have to be added to both .vcproj files. Of course! The Apple and Cairo/libCURL ports of WebKit are already sharing .vcproj files. Can WinCE share these files, too? It is possible, but i'm not sure if it's the best solution: There will uncountable ExcludeFromBuild in the vcproj files and if we will add additional platforms i will grow further. If you add the STANDARDSDK_500 (ARMV4I) platform to the solution it might throw a warning if the SDK isn't installed. - Patrick ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] build system for wince port
Hi Patrick, We have a working wince build for all components right now including javascrtipcore, webcore and webkit COM layers. We'd like to help contribute this back in as well and work together with you on this. Right now we are using a separate vcproj file for each of the components (solution 1(b) below). Our build is a wince-cairo configuration and follows the windows build configuration very closely so we are not dependent on a lot of the current WINCE files in the tree (in fact I don't think we are using almost any of these except in a couple of places). We'd like to contribute this back using a new build flag such as WINCE_CAIRO. Best regards, Jason -Original Message- From: webkit-dev-boun...@lists.webkit.org [mailto:webkit-dev-boun...@lists.webkit.org] On Behalf Of Patrick Roland Gansterer Sent: Wednesday, December 23, 2009 5:41 PM To: webkit-dev@lists.webkit.org Subject: [webkit-dev] build system for wince port Currently the Windows CE port has no working build system. I'd like to contribute one, but i need to know the preferred solution: (1) Add the port to the current sln/vsproj/vsprops files a) Extend the sln/vsproj with the additional platforms and add many FileConfiguration ExcludedFromBuild=true and split the vspops. b) Add a separate main vsproj file (JavaScriptCore.vcproj, WebCore.vcproj) for the port (like code.staikos.net) c) Split the current main vspoj files into a platform dependent and independent file (2) Add it to a other build system like gyp or bkl. Which one provides good cross compiling features for wince? (3) Add a completely independent build system Which one is the least ugly one? I prefer 1a in the moment. I'd like to start with STANDARDSDK_500 (ARMV4I) and then add other supported STANDARDSDK_500 platforms. Because the wince port isn't finished right now, it's only possible to provide it for WTF and JavaScriptCore (including tests). Is already anything in the repository with support for cross compiling (something like Scripts/build-webkit)? Is anybody _active_ working on the wince port? Most of the related bugs are inactive for months now. Does anybody have the last git repository form git://code.staikos.net/WebKit- CE before it has gone offline? (my last log message is from 2009-07-30) I'd like to do some additional work in porting the remaining parts, when i have a working build system for it. - Patick ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] build system for wince port
Jason Rukman: We have a working wince build for all components right now including javascrtipcore, webcore and webkit COM layers. We'd like to help contribute this back in as well and work together with you on this. Can you give me a snapshot of your code or better publish it? When you use cairo (and curl for network?) it is only a cairo port. The qt port is working on WinCE too. During the last days i have begun finishing most of the work from Tourch Mobile. In my opinion the missing buildsystem is the biggest problem in the moment. I'm very interested in all of your WinCE work! If you can share your code i can also help with creating patches. Which WinCE SDK(s) do you use? - Patrick ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] build system for wince port
On Thu, Dec 24, 2009 at 02:53:18, Adam Barth: Please try to avoid this option if at all possible. The number of build systems in the tree is out of control already. Are there any plans to cleanup and use only one? 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. - Patrick ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] build system for wince port
Please try to avoid this option if at all possible. The number of build systems in the tree is out of control already. Are there any plans to cleanup and use only one? It was intended to use the newly introduced gypi files (from the Chromium port). More informations about GYP http://code.google.com/p/gyp/. The Haiku port had volunteered to be guinea pigs for using them as well (it's just required to write a backend). Sadly the one who was responsible to do it has been overloaded and didn't have time to do so. Regards, -- Maxime ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] build system for wince port
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.) Dave ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
[webkit-dev] build system for wince port
Currently the Windows CE port has no working build system. I'd like to contribute one, but i need to know the preferred solution: (1) Add the port to the current sln/vsproj/vsprops files a) Extend the sln/vsproj with the additional platforms and add many FileConfiguration ExcludedFromBuild=true and split the vspops. b) Add a separate main vsproj file (JavaScriptCore.vcproj, WebCore.vcproj) for the port (like code.staikos.net) c) Split the current main vspoj files into a platform dependent and independent file (2) Add it to a other build system like gyp or bkl. Which one provides good cross compiling features for wince? (3) Add a completely independent build system Which one is the least ugly one? I prefer 1a in the moment. I'd like to start with STANDARDSDK_500 (ARMV4I) and then add other supported STANDARDSDK_500 platforms. Because the wince port isn't finished right now, it's only possible to provide it for WTF and JavaScriptCore (including tests). Is already anything in the repository with support for cross compiling (something like Scripts/build-webkit)? Is anybody _active_ working on the wince port? Most of the related bugs are inactive for months now. Does anybody have the last git repository form git://code.staikos.net/WebKit- CE before it has gone offline? (my last log message is from 2009-07-30) I'd like to do some additional work in porting the remaining parts, when i have a working build system for it. - Patick ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] build system for wince port
On Wed, Dec 23, 2009 at 5:40 PM, Patrick Roland Gansterer par...@paroga.com wrote: (3) Add a completely independent build system Please try to avoid this option if at all possible. The number of build systems in the tree is out of control already. I'm worried that the port will rot without an active maintainer, no matter which build system you choose. Adam ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
