I think it’s a great idea to do this.
But once we are ready to throw the switch I would like to review the difference
between what’s going to be exported without the .exp files and what will be
exported afterwards to look for problems. We did something like that with
JavaScriptCore. If we manag
Fixed in r172816.
Dean
> On 15 Aug 2014, at 1:56 am, Info wrote:
>
> This seems to be a bug... that has been fixed in Chromium: see
> chromium\src\third_party\WebKit\Source\modules\webaudio
>
>
> Zitat von Info :
>
>> In order to understand the idiotic differences between the data ranges of
That sounds like an excellent project! Symbols files are so annoying.
On Wednesday, August 20, 2014, Alex Christensen
wrote:
> I'm attempting to remove WebCore.exp.in, WebKitExports.def.in, and the
> associated build steps of processing these files. I'd like to continue
> (more carefully than
I’m attempting to remove WebCore.exp.in, WebKitExports.def.in, and the
associated build steps of processing these files. I’d like to continue (more
carefully than I did earlier) unless anyone has any objections. This would
involve the use of the new WEBCORE_EXPORT macro instead of maintaining
4 matches
Mail list logo