wrote:
Hi,
Patrick Gansterer írta:
On 31.01.2014, at 22:10, Anders Carlsson ander...@apple.com wrote
looks like the last legitimate commit to the Windows CE port was on
November 3rd November 2013, almost 3 months ago.
What's the minimum upstream interval for downstream fixes to show ongoing
On 19.03.2014, at 17:35, Brent Fulgham bfulg...@apple.com wrote:
Hi All,
I’m arriving to this conversation a bit late, but had a few comments:
On Mar 16, 2014, at 11:06 AM, Patrick Gansterer par...@paroga.com wrote:
DerivedSources.make depends heavily on UNIX command line tools (cat
It might be possible to achieve, but it will remove a lot of the benefits from
CMake.
You have two options:
a) Invoke make on DerivedSources.make and add a lot of custom target for that
to CMake
b) Parse the DerivedSources.make and create CMake rules out of it
Since (b) would require a kind of
On 16.03.2014, at 16:10, Darin Adler da...@apple.com wrote:
On Mar 16, 2014, at 3:01 AM, Patrick Gansterer par...@paroga.com wrote:
a) Invoke make on DerivedSources.make and add a lot of custom target for
that to CMake
I’d like to see what this would look like before deciding it’s a bad
On 16.03.2014, at 16:28, Darin Adler da...@apple.com wrote:
On Mar 16, 2014, at 8:18 AM, Patrick Gansterer par...@paroga.com wrote:
On 16.03.2014, at 16:10, Darin Adler da...@apple.com wrote:
On Mar 16, 2014, at 3:01 AM, Patrick Gansterer par...@paroga.com wrote:
a) Invoke make
On 16.03.2014, at 17:37, Darin Adler da...@apple.com wrote:
On Mar 16, 2014, at 9:12 AM, Patrick Gansterer par...@paroga.com wrote:
The big point is Windows.
So the core issue isn’t really about CMake at all! It’s that the base Windows
tool set doesn’t include GNU make or an equivalent
Gansterer par...@paroga.com wrote:
On 16.03.2014, at 17:37, Darin Adler da...@apple.com wrote:
On Mar 16, 2014, at 9:12 AM, Patrick Gansterer par...@paroga.com wrote:
The big point is Windows.
So the core issue isn’t really about CMake at all! It’s that the base
Windows tool set doesn’t
On 16.03.2014, at 19:32, Darin Adler da...@apple.com wrote:
On Mar 16, 2014, at 11:06 AM, Patrick Gansterer par...@paroga.com wrote:
DerivedSources.make depends heavily on UNIX command line tools (cat, sed,
sort, …)
I’m not sure what heavily means here. This seems really easy to fix.
I
On 16.03.2014, at 22:08, Darin Adler da...@apple.com wrote:
On Mar 16, 2014, at 12:01 PM, Patrick Gansterer par...@paroga.com wrote:
rm does not exist on Windows and scripts can not uses shebang.
OK, I think I’ll scrub the rm commands out. Perl can do rm easily.
What does shebang
On 16.03.2014, at 22:23, Darin Adler da...@apple.com wrote:
On Mar 16, 2014, at 2:19 PM, Patrick Gansterer par...@paroga.com wrote:
On 16.03.2014, at 22:08, Darin Adler da...@apple.com wrote:
What does shebang have to do with the makefile?
You can not run a script by ./script
On 31.01.2014, at 22:10, Anders Carlsson ander...@apple.com wrote
looks like the last legitimate commit to the Windows CE port was on November
3rd November 2013, almost 3 months ago.
What's the minimum upstream interval for downstream fixes to show ongoing
activity?
I also seem to remember
On 05.10.2013, at 19:13, Brent Fulgham wrote:
The WinCairo port is as close to the AppleWin port as possible. It uses ICU
and I have no intention of changing that.
The WinCE port is maintained by Patrick Gangsterer. I believe that this port
does not want to use ICU, preferring to use the
On 07.10.2013, at 18:28, Darin Adler wrote:
On Oct 7, 2013, at 1:34 AM, Patrick Gansterer par...@paroga.com wrote:
On 05.10.2013, at 19:13, Brent Fulgham wrote:
The WinCairo port is as close to the AppleWin port as possible. It uses ICU
and I have no intention of changing
Since WinCairo has no working Buildbot there is no easy way to get such
version. You must be able to fix small build problems on your own at the
moment. Feel free to create bugs at https://bugs.webkit.org/ (with patch to fix
it) if you see such problems.
-- Patrick
On 24.09.2013, at 15:47,
.
Thanks,
Roger
On Apr 9, 2013, at 9:34 AM, Patrick Gansterer par...@paroga.com wrote:
Hi,
On Mon, 08 Apr 2013 18:10:29 -0700, Mark Rowe wrote:
On 2013-04-08, at 17:45, Patrick Gansterer par...@paroga.com wrote:
Hmm, I'll try to set up an example for WTF + JavaScriptCore. Maybe you can
Am 13.04.2013 um 03:22 schrieb Benjamin Poulain:
On Fri, Apr 12, 2013 at 6:15 PM, Maciej Stachowiak m...@apple.com wrote:
On Apr 12, 2013, at 4:09 PM, Karen Shaeffer shaef...@neuralscape.com wrote:
As others have said, we are definitely eager to use C++11 across the board
but are limited
Am 11.04.2013 um 00:30 schrieb Roger Fong:
Hi Patrick,
A few questions I have about the CMake system, being someone who's never used
it before.
-I would like to keep all of the unified properties settings that the VS2010
property sheets hierarchy provided.
Can we still maintain that
Hi,
On Mon, 08 Apr 2013 18:10:29 -0700, Mark Rowe wrote:
On 2013-04-08, at 17:45, Patrick Gansterer par...@paroga.com wrote:
Hmm, I'll try to set up an example for WTF + JavaScriptCore. Maybe
you can have a look at it then to check if I understand the concept
correctly before I move
Am 08.04.2013 um 21:26 schrieb Roger Fong:
Unfortunately this would cause a lot of complication in our internal build
setup that we currently don’t really have the resources to deal with right
now.
Please don't get me wrong, but I only get a some internal problems answer
always. Can
Am 09.04.2013 um 00:58 schrieb Mark Rowe:
On 2013-04-08, at 15:44, Patrick Gansterer par...@paroga.com wrote:
Am 08.04.2013 um 21:26 schrieb Roger Fong:
Unfortunately this would cause a lot of complication in our internal build
setup that we currently don’t really have the resources
Am 09.04.2013 um 02:29 schrieb Mark Rowe:
On 2013-04-08, at 17:16, Patrick Gansterer par...@paroga.com wrote:
Am 09.04.2013 um 00:58 schrieb Mark Rowe:
On 2013-04-08, at 15:44, Patrick Gansterer par...@paroga.com wrote:
Am 08.04.2013 um 21:26 schrieb Roger Fong
Hi,
since the Chromium code is getting removed step by step I think that the GYP
build system won't have a shiny future in the WebKit repository. In the GYP vs.
CMake match CMake gets an additional point: There is no WebKit port working
with GYP, but at least 3 with CMake. Accordantly to [1]
Hi,
Am 31.01.2013 um 09:25 schrieb Mark Rowe:
CMake was originally considered a non-starter for chromium since the
XCode and VS projects it produced didn't look or feel like native
projects. However, we've since switched to ninja for most things so
I'm less sure how important this is now.
Am 31.01.2013 um 10:37 schrieb Ryosuke Niwa:
On Thu, Jan 31, 2013 at 1:17 AM, Jochen Eisinger joc...@chromium.org wrote:
Another option is to add a webkit-patch command for modifying the build
files. That way, the syntax doesn't need to be overly human friendly. There
was also some attempt
Am 31.01.2013 um 17:17 schrieb Maciej Stachowiak:
On Jan 31, 2013, at 1:56 AM, Patrick Gansterer par...@paroga.com wrote:
Am 31.01.2013 um 10:37 schrieb Ryosuke Niwa:
On Thu, Jan 31, 2013 at 1:17 AM, Jochen Eisinger joc...@chromium.org
wrote:
Another option is to add a webkit-patch
Am 31.01.2013 um 21:07 schrieb Dirk Pranke:
On Thu, Jan 31, 2013 at 11:48 AM, Hugo Parente Lima
hugo.l...@openbossa.org wrote:
On Wednesday, January 30, 2013 04:15:48 PM Maciej Stachowiak wrote:
On Jan 30, 2013, at 3:24 PM, Dirk Pranke dpra...@chromium.org wrote:
On Wed, Jan 30, 2013 at
Hi,
Am 30.01.2013 um 22:28 schrieb Eric Seidel:
I wish we only had one build system (it were easy to add/remove/move files).
I've created CMake files for two different ports at [1] and [2] already, but
did't get positive feedback from the port-maintainer. So I stopped working on
it. If any
On Tue, 04 Sep 2012 22:26:52 -0700, Adam Barth wrote:
On Tue, Sep 4, 2012 at 10:06 PM, Christophe Dumez
christophe.du...@intel.com wrote:
On Sep 5, 2012, at 2:22 AM, Adam Barth aba...@webkit.org wrote:
Removing operator+= will likely require changes to a number of
port-specific files. I'll do
Hi,
On Thu, 02 Aug 2012 10:53:30 +0200, Martin Robinson wrote:
Hi all,
What's the procedure for adding a blog to the WebKit Planet? I often
post material interesting to some of the WebKit community, but not
suitable for Surfin' Safari since it is often specific to WebKitGTK+
or to just a
But the author rewrite hook for commit-qu...@webkit.org does not work.
-- Patrick
On Fri, 27 Jul 2012 09:33:49 -0700, William Siegrist wrote:
Sorry about that, put the wrong address in the new hook. :( Should be
fixed now.
-Bill
On Jul 27, 2012, at 9:30 AM, Brady Eidson beid...@apple.com
Hi,
Am 24.07.2012 um 22:08 schrieb Patrick East:
So I can see from JITStackFrame stackFrame =
*reinterpret_castJITStackFrame*( args) that the args parameter is supposed
to be the address of the JITStackFrame. If my understanding is correct, there
needs to be some assembly code to setup the
IMHO only setting up a bot won't help that much. Someone must keep it green.
From my experience with the WinCE build slave (which has some common features
turned of by default) I don't see many people caring about it.
E.g. WinCE build slaves builds with JIT turned of, which leads to much redness
, but I suspect the reason folks from the community don't put
much effort into keeping the WinCE bot green is because the port seems
to be somewhat in a holding pattern.
Adam
On Mon, Jun 25, 2012 at 1:45 PM, Patrick Gansterer par...@paroga.com wrote:
IMHO only setting up a bot won't help
tomorrow @ 10am.
Interested parties should definitely be there. Especially ones who
know something about CMake (since I know nothing). :)
-eric
On Thu, Apr 12, 2012 at 5:41 AM, Patrick Gansterer par...@paroga.com wrote:
Hi,
it's more than a year since the last discussion about the build
Am 12.04.2012 um 20:06 schrieb Dirk Pranke:
Patrick, have you documented what all you need to install on a Win box
in order to be able to run CMake and do the build?
You need to install CMake and the same tools listed at
http://trac.webkit.org/wiki/WinCE#Build and
Am 19.04.2012 um 03:46 schrieb Mark Rowe:
Is it possible to get a (detailed) list of requirements? It's hard for
people don't knowing the internal Apple build process to work on it.
We don't have anything of this nature available for external consumption at
this time.
Does that mean
Hi,
it's more than a year since the last discussion about the build system of
Apple's Windows port. In the meantime I merged most of the general changes into
the CMake files in the repository and have a working patch with a few CMake
files at [1] as written in [2]. I don't think that it is
Hi,
On Tue, 27 Mar 2012 17:14:55 +0530, M Rahaman wrote:
When I build WebKit code for Windows using VS2008, there are several
issues I am facing
1. We need to re-generate the webkit.sln file with VS2008
2. VS2008 has strict warning checking, because all the .vcproj has
Treat warning as
My git fetch transfer rates seam to depend on the time and day of the week.
Last weekend I fetched with about 800 KiB/s, now I get about 250 KiB/s, but I
reach only about 40 KiB/s during US working hours 1-2 weeks ago.
The traceroute looks the same from Austria:
9
Am 08.03.2012 um 23:30 schrieb Alexis Menard:
On Thu, Mar 8, 2012 at 7:10 PM, Maciej Stachowiak m...@apple.com wrote:
It seems like there are a couple of different issues here that affect how we
do version control. Currently we have an SVN primary repository, some
contributors use SVN, and
Some of my thought on this, since I have the same problems with my WinCE bot:
1) Is there any real benefit in the CoreBuilders concept (since it's not used
as intended as Eric already wrote)?
2) When we still want the CoreBuilder concept: Can we make the core/non-core
transition without any
the missing parts. At least for me it's easier to fix
compiler errors than answering questions about a possible build break on
webkit-dev. ;-)
- Patrick
Am 14.09.2011 um 21:08 schrieb Geoffrey Garen:
Hi Patrick.
On Tue, Sep 13, 2011 at 2:38 PM, Patrick Gansterer par...@paroga.com wrote:
How do
was acquired by RIM).
AFAIR, Patrick Gansterer (paroga) is still working on the WinCE port. He
usually informally reviews CMake-related changes.
I believe this is correct. He also maintains a buildbot:
http://build.webkit.org/builders/WinCE%20Release%20%28Build%29
Yes, that's correct.
How do
On Tue, Sep 13, 2011 at 11:41 PM, Ryosuke Niwa rn...@webkit.org wrote:
On Tue, Sep 13, 2011 at 2:38 PM, Patrick Gansterer par...@paroga.com
wrote:
Yes, that's correct.
How do we measure an active port??? I maintain a buildbot for WinCe and
usually fix problems with the port within hours
I'm not sure if it's that easy. ;-)
We have different CPU(), OS(), PLATFORM() and USE() defines and they can be
combined in many different ways, even if some ports are already handled via an
simple PLATFORM(XY) macro.
Patrick
Am 14.09.2011 um 00:06 schrieb Leandro Pereira:
On 09/13/2011
The new XML parser isn't finished yet (see webkit.org/b/64396).
An ENABLE_NEW_XML=1 preprocessor definition should work, but you need to hack
this into your build system on your own at the moment. Some build system don't
contain the required source file, so there might be more work needed.
So
Hi,
Am 13.07.2011 um 22:38 schrieb Brent Fulgham:
Can we please move away from VS2005 in the near future? What can we
(outside of Apple) do to help make this possible?
I've created already a CMake based version of AppleWindows port. I've compiled
it with VS2010, but it should work with the
On Mon, 11 Jul 2011 21:30:44 -0700, Brent Fulgham bfulg...@gmail.com
wrote:
Is the WinCE port still active?
I don't know about your other questions, but Patrick Gansterer (paroga)
maintains the WinCE port. I believe it is active.
Correct, I still maintain the WinCE port and provide
IMO [Conditional=XXX] does not generate correct output (only tried JSC). It
adds top many header includes.
Example with DOMWindow.idl:
The line
attribute [Conditional=DATABASE] SQLExceptionConstructor SQLException;
adds #include JSSQLException.h independently of ENABLE_DATABASE.
The lines
#if
, but I suspect there are lots of configurations
that don't actually build.
Adam
On Sun, Jul 3, 2011 at 2:12 AM, Patrick Gansterer par...@paroga.com wrote:
IMO [Conditional=XXX] does not generate correct output (only tried JSC). It
adds top many header includes.
Example
Am 03.07.2011 um 17:33 schrieb Alexey Proskuryakov:
I see three possible solutions:
1) Always generate all IDL files.
2) Change all [Conditional=XXX] to #if define(ENABLE_XXX).
3) Add the correct #if ENABLE(XXX) around the header includes.
(1) used to be the preferred solution. It's so
I had the same idea a year ago, and got only negative feedback.
My main intention was/is the performance of the parser (see [1]). I improved
the performance of it a lot in the meantime (see dependencies of [2])
[2] tries to remove this UTF-8 - UTF-16 - UTF-8 overhead. The patch isn't
perfect at
Am 13.05.2011 um 23:07 schrieb Lucas De Marchi:
Humn... now I see what you're saying. I don't know if it's worth
because that would give the user the option to turn it on. Not all
options work with every port and doing so will result in a build
break.
So what we did is let all options
This is not the right mailing list for discussion of how to use WebKit or work
around bugs. This mailing list is for people involved in the development of
WebKit to work together. For an GTK-specific issue I suggest webkit-gtk
mailinglist. See http://www.webkit.org/contact.html.
- Patrick
Am
Hi,
Sometimes folks commit changes without bug numbers. If those changes breaks
things it's hard to find the correct context for the change.
Can we make the bug number a requirement for a commit when it has a
corresponding bug?
IMHO it would be great if the style bot and the reviewer complain
to blame you directly! :-)
Am 26.03.2011 um 21:32 schrieb Ryosuke Niwa:
On Sat, Mar 26, 2011 at 10:41 AM, Darin Adler da...@apple.com wrote:
On Mar 26, 2011, at 3:24 AM, Patrick Gansterer wrote:
Sometimes folks commit changes without bug numbers. If those changes breaks
things it's hard
I'm experiencing a link failure when attempting to compile the jsc for an
embedded platform.
If you write a mail to this list: Please provide more information! What is
embedded platform? Which architecture? Which port?
BTW: This is more a question for webkit-help and not form webkit-dev. See
Please have a look at [1] and [2]. You need to run build-webkit first.
BTW: If provide error messages instead of fails to compile only, it's easier
for other people to help you.
[1] http://webkit.org/building/build.html
[2] http://webkit.org/building/debug.html
- Patrick
Won J Jeon:
Thanks,
Congratulation!
Adam Barth:
If you own one of the files below, please consider moving it from the
root directory to the Source directory:
cmakeconfig.h.cmake
CMakeLists.txt
I'd like to move the CMake related files into Source, but they also require
some files from the Tools directory
Adam Barth:
Otherwise we need to keep the files in the root directory. :-(
I'm not sure I understand the connection. For example,
cmakeconfig.h.cmake seems to be entirely concerned with WebCore
concepts (essentially which features are enabled):
Hi,
Brent Fulgham:
Hi Patrick,
On Jan 10, 2011, at 12:37 PM, Patrick Gansterer wrote:
André Pedralho:
Hi Fred, my bad! Sorry, it is only available in the Qt port.
If you have a look at the Qt port you see the following:
JSC::JSValue v =
d-frame-script()-executeScript
André Pedralho:
Hi Fred, my bad! Sorry, it is only available in the Qt port.
If you have a look at the Qt port you see the following:
JSC::JSValue v =
d-frame-script()-executeScript(ScriptSourceCode(scriptSource)).jsValue();
There's a Frame::script() method where get the ScriptController.
-
Alex Milowski:
On Tue, Jan 4, 2011 at 7:05 PM, Alexey Proskuryakov a...@webkit.org wrote:
04.01.2011, в 18:40, Alex Milowski написал(а):
Looking at the libxml2 API, I've been baffled myself about how to
control the character encoding from the outside. This looks like a
serious lack of
Darin Adler:
On Jan 5, 2011, at 5:07 AM, Patrick Gansterer wrote:
Is there a reason why we can't pass the raw data to libxml2?
Because libxml2 does its own encoding detection which is not even close to
what’s specified in HTML5, and supports far fewer encodings. If you make a
test
Eric Seidel:
The more you turn off, the less the binary you create is WebKit. It
tells servers its WebKit via its useragent, but then it doesn't have
the features that pages have come to expect from WebKit -- this is bad
for WebKit and bad for your users.
Feature detection by user agent is
Hi all,
I'm glad to say that WebKit-WinCE is finally merged and got a working build
slave [1] today.
Many, many thanks to the people from TorchMobile who did the original WinCE
port and all the friends that reviewed my patches to make this possible. Thanks!
It would be nice if we can try to
Hi,
also thank you for leading the reorg.
Adam Barth:
Here's a snapshot of my current thinking on where the files and
folders currently in the top-level directory might go.
There are a bunch of build-system related files that are currently in
the root. I'm not sure whether we should
Hi,
Does anybody compile WebKit with inspector disabled?
It's not possible with the current trunk (since weeks). I'm not sure what's the
correct solution to fix this.
The main problem is that Console.cpp (e.g. at [1]) uses ScriptCallStack and
ScriptCallStackFrame, but this classes should go
I filed bug 49500 (including patch).
But I'm still interested if there is someone who maintains the
ENABLE(INSPECTOR) option.
Simon Fraser:
Please file a bugzilla bug on this issue.
Simon
On Nov 13, 2010, at 8:15 AM, Patrick Gansterer wrote:
Hi,
Does anybody compile WebKit
69 matches
Mail list logo
