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
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
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
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
@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
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
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
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
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
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
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
11 matches
Mail list logo
