[Webkit-unassigned] [Bug 85739] Building and debugging WebKit in the Xcode IDE requires a lot of setup

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon May 14 20:02:03 PDT 2012


https://bugs.webkit.org/show_bug.cgi?id=85739





--- Comment #12 from Alexis Menard (darktears) <alexis.menard at openbossa.org>  2012-05-14 20:01:05 PST ---
(In reply to comment #11)
> (In reply to comment #9)
> > (In reply to comment #8)
> > > Which scheme did you try to build with? The All Tools scheme currently depends on one of the All Source schemes to have been built.
> > 
> > I actually selected the All Sources scheme and run build. It compiled WTF correctly, LLInt Offsets but JSCLLIntOffsetsExtractor target failed to compile (then the build stop) as LLIntOffsetsExtractor.cpp include <wtf/Platform.h> which is not found :(.
> 
> Can you file a new bug about this?

Sure here it is : https://bugs.webkit.org/show_bug.cgi?id=86430

> 
> > 
> > But really it is a very welcomed patch and makes life easier for people who work occasionally on the Mac port.
> > 
> > Some other questions :
> > 
> > - How to specify the output dir like build-webkit? I have a single git checkout but shadow build all the ports. Is is possible? Can I do it for the entire workspace?
> 
> This is answered in <http://www.webkit.org/building/debug.html>:
> “Ensure that the Products and Intermediates locations for the workspace match those used by build-webkit by choosing File > Workspace Settings and clicking the Advanced button, selecting Custom, Relative to Workspace, and entering WebKitBuild both for Products and for Intermediates.”

Sorry about that :(. 

> 
> 
> > - What is the All Source (target WebProcess). What is the use case?
> 
> That scheme builds the same targets, but runs WebProcess in a configuration that makes it launch Safari as its client. This makes it easier to debug WebProcess, which is useful for people working on WebCore and JavaScriptCore. It is equivalent to “debug-safari --target-web-process”.
> 
> > 
> > - If I want to run/debug with Safari, positioning the All Source scheme and then click debug is enough I believe?
> 
> Yes, but if you are interested in debugging WebCore or JavaScriptCore, you probably want to debug WebProcess, using the aforementioned scheme. Either way, Xcode allows you to attach to the other process and debug both simultaneously.

Ok thanks for the explanation.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.


More information about the webkit-unassigned mailing list