No, symlinks would not work since upstream gyp files still depend on
downstream gyps (skia, icu, etc). Working on it.

On Fri, Sep 25, 2009 at 12:45 PM, Andrew Scherkus <[email protected]>wrote:

> It also appears you can no longer use a symlink to point
> /src/third_party/WebKit at a different checkout.  I think relative paths are
> to blame but I haven't fully debugged the issue yet.
>
>
> On Fri, Sep 25, 2009 at 12:20 PM, Jeremy Orlow <[email protected]>wrote:
>
>> I updated
>> http://sites.google.com/a/chromium.org/dev/developers/contributing-to-webkit
>>
>>
>> On Fri, Sep 25, 2009 at 12:14 PM, Andrew Scherkus 
>> <[email protected]>wrote:
>>
>>> For those that use third_party/WebKit as a full WebKit checkout, you'll
>>> need to add the following line to your .gclient:
>>>  "src/third_party/WebKit/WebKit/chromium": None,
>>>
>>> Andrew
>>>
>>>
>>> On Fri, Sep 25, 2009 at 11:51 AM, Marc-Antoine Ruel <[email protected]
>>> > wrote:
>>>
>>>>
>>>> Yep, I specified one directory too deep.
>>>>
>>>> On Fri, Sep 25, 2009 at 2:50 PM, Mike Pinkerton <[email protected]>
>>>> wrote:
>>>> > To get mine to work, I had to
>>>> >
>>>> >  rm -rf src/third_party/WebKit/WebKit
>>>> >
>>>> > just doing "chromium" wasn't enough to stop the hangs.
>>>> >
>>>> > On Fri, Sep 25, 2009 at 2:36 PM, Marc-Antoine Ruel <
>>>> [email protected]> wrote:
>>>> >>
>>>> >> Your next gclient sync will probably hang. The easiest way to fix it
>>>> is to:
>>>> >>  rm -rf src/third_party/WebKit/WebKit/chromium
>>>> >> or
>>>> >>  rd /q /s src\third_party\WebKit\WebKit\chromium
>>>> >>
>>>> >> before syncing.
>>>> >>
>>>> >> Sorry for the trouble,
>>>> >>
>>>> >> M-A
>>>> >>
>>>> >> >>
>>>> >>
>>>> >
>>>> >
>>>> >
>>>> > --
>>>> > Mike Pinkerton
>>>> > Mac Weenie
>>>> > [email protected]
>>>> >
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: [email protected] 
View archives, change email options, or unsubscribe: 
    http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---

Reply via email to