Re: [webkit-dev] !ENABLE(INSPECTOR)

2010-11-13 Thread Yury Semikhatsky
I don't think there is a particular person who maintains that option. Instead if you cannot find the change which broke it and file a bug against the author you could file a bug against the web inspector component( webkit.org/new-inspector-bug) and we'll take care of it. In this particular case it

Re: [webkit-dev] !ENABLE(INSPECTOR)

2010-11-13 Thread Patrick Gansterer
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 W

Re: [webkit-dev] !ENABLE(INSPECTOR)

2010-11-13 Thread 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 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 mai

[webkit-dev] !ENABLE(INSPECTOR)

2010-11-13 Thread Patrick Gansterer
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 in