fwiw I did restart VS, as I pretty much always shut down VS completely when
gclient syncing. Maybe there was some other confounding change and/or dumb
mistake on my part. I thought it was caused by this but on second thought I
don't have solid grounds for saying that :)

On Thu, Feb 19, 2009 at 4:39 PM, Darin Fisher <[email protected]> wrote:

> Sounds like the kind of error Visual Studio sometimes produces after asking
> to reload projects.  A restart of VS usually helps clear that.  It doesn't
> always handle environment variables that appear in a Files section properly
> after a vcproj reload.
> -Darin
>
>
> On Thu, Feb 19, 2009 at 3:20 PM, Tim Steele <[email protected]> wrote:
>
>> Im not exactly sure how I got myself into the situation I got myself into
>> or what that situation was exactly, but I deleted this folder, clobbered my
>> build dir, synced and tried to build, and was faced with tons of file not
>> found errors for things like V8somethingsomething.cpp, SVGNames.h,... and
>> wanted to cry.
>>
>> I then repeated the steps but used gclient sync --force, and things seem
>> to be building smoothly now. Just mentioning in case someone else is
>> suffering from this, sorry Im not being very precise!
>>
>>  On Thu, Feb 19, 2009 at 10:54 AM, Darin Fisher <[email protected]>wrote:
>>
>>>  You should also just edit your .gclient_entries file, to remove the
>>> "src/third_party/WebKit/WebKit" line.  Otherwise, "gclient sync" will
>>> complain about it after each run.
>>> -Darin
>>>
>>>
>>> On Thu, Feb 19, 2009 at 8:55 AM, Darin Fisher <[email protected]>wrote:
>>>
>>>> With a change that I have just committed, it is now necessary to delete 
>>>> src/third_party/WebKit/WebKit
>>>> and re-run gclient sync.
>>>> Sorry for any inconvenience!!
>>>>
>>>> -Darin
>>>>
>>>
>>>
>>> >>>
>>>
>>
>

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

Reply via email to