Use of AccessibilityAllInOne in Xcode builds was introduced in <http://trac.webkit.org/r77878> to address bug 53681, an issue with 32-builds on Leopard. That’s no longer a supported configuration, so the all-in-one workaround shouldn’t be necessary anymore.
Created attachment 243782 [details] Stop using AccessibilityAllInOne.cpp
(The downside of using AccessibilityAllInOne.cpp is that any change in any file included by any of the 23 .cpp files it includes requires all 23 files to be recompiled).
Comment on attachment 243782 [details] Stop using AccessibilityAllInOne.cpp OK. Why?
Oh, I see why.
Committed <http://trac.webkit.org/r177781>.
(In reply to comment #5) > Committed <http://trac.webkit.org/r177781>. I reverted this change in <http://trac.webkit.org/r177784>, because it seems to have caused something like bug 139609 on iOS. I am going to attempt this again once the iOS issue is understood.
(In reply to comment #6) > (In reply to comment #5) > > Committed <http://trac.webkit.org/r177781>. > > I reverted this change in <http://trac.webkit.org/r177784>, because it seems > to have caused something like bug 139609 on iOS. The issue on iOS turned out to be a configuration issue that is different from bug 139609.
Committed <http://trac.webkit.org/r177834>.