If it was code in JavaScriptCore that was no longer used I could see the point,
But since it's WTF functionality that isn't being used in another component
atm. I would tend to keep it.
But then I've always hated ( and been bitten by ) things like its allways
going to be 32bit, chars are
I agree, the time taken to build is not really a good reason for the change or
lack of - as you point out there, are many other ways to optimize the build
process/server which will have wider benefits.
But does anybody consider size to be an issue? SVG adds a fair chunk to the
size of a binary
:20 AM, Steven Coul (scoul) sc...@cisco.com wrote:
I agree, the time taken to build is not really a good reason for the change
or lack of - as you point out there, are many other ways to optimize the
build process/server which will have wider benefits.
But does anybody consider size
Would this be simplify as in tidy up existing code, get down to a simple subset
of required functionality, and maybe abstracting the (E)GL part?
Or are you considering a simplification by just saying it will be EGL version
X, and OpenGL version Y from now on and nothing else?
Steve Harry
Is there an alternative to levelDB without going to webkit2 ?
Steve Harry Coul
sc...@cisco.commailto:sc...@cisco.com
On Apr 28, 2014, at 4:20 AM, ryuan Choi
ryuan.c...@webkit.orgmailto:ryuan.c...@webkit.org wrote:
WebKit/Efl dropped level db dependency (and disabled leveldb)
2014-04-28
Or just remove them? They’ll be available in the repo anyhow.
Steve Harry Coul
sc...@cisco.com
On May 7, 2014, at 4:20 PM, Zoltan Horvath zol...@webkit.org wrote:
Hi there,
We're having more and more 'archived' change log files in our tree. Can't me
move/archive these files into their
Naive question(s) here.
Why does the physical number of cores ( and that is not necessarily the number
of actionable native threads ) matter?
I would expect a mature system to do the best it can with hardware, in what the
software has asked for it. Some tasks are sleepy, some are IO bound,
Would [Conditional] use through out also not allow us to perform the IDL
compile without running the c preprocessor on each file?
Can [Conditional] not be fixed to support multiple flags?
The compiling of IDL is a significant portion of the total build time, and
ccache distcc et al cannot
On Mar 9, 2015, at 2:52 PM, Darin Adler da...@apple.com wrote:
On Mar 9, 2015, at 5:39 AM, Steven Coul (scoul) sc...@cisco.com wrote:
Would [Conditional] use through out also not allow us to perform the IDL
compile without running the c preprocessor on each file?
Possibly.
Can
way to avoid having to
revert or fix stuff too often.
Over the last 10 weeks, these builds have averaged 6m24s. So 34 seconds there
is more significant.
Steve Harry Coul
sc...@cisco.com
On Mar 10, 2015, at 11:09 AM, Darin Adler da...@apple.com wrote:
On Mar 9, 2015, at 5:02 PM, Steven Coul
10 matches
Mail list logo
