Bug 31178 - ObjC DOM build succeeds the second time after public API failure
Summary: ObjC DOM build succeeds the second time after public API failure
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: DOM (show other bugs)
Version: 528+ (Nightly build)
Hardware: Mac OS X 10.6
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-05 11:06 PST by Timothy Hatcher
Modified: 2012-10-11 16:36 PDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Timothy Hatcher 2009-11-05 11:06:08 PST 
From bug 29972:

> The first build runs CodeGeneratorObjC.pm to generate the ObjC bindings, and
> then checks if public interfaces changed (PublicDOMInterfaces.h). Since the API
> of DOMHTMLAnchorElement changed, the script simply dies. (CodeGeneratorObjC.pm
> line 297).
> 
> The second time, the ObjC bindings are already generated, so there is no check
> of SDK API, and the build succeeds. 

We likely need to remove the generated file that has the API failure, so it keeps getting rebuilt until resolved.