Just to close the issue, VS2008 is working fine here at the moment.

On Thu, Mar 19, 2009 at 9:18 PM, Bradley Nelson <[email protected]> wrote:
>>
>> We are not using 2.6?
>
> Not at the moment.
> Thanks, at a loss to explain it.
> Let me know if this happens again.
> Has anyone else seen this sort of thing?
> -BradN
>
>
>
>
>>
>>
>> On Thu, Mar 19, 2009 at 1:42 PM, Bradley Nelson <[email protected]>
>> wrote:
>> > Very mysterious.
>> > These are gyp related:
>> > ..\base\base.vcproj
>> > ..\base\base_gfx.vcproj
>> > ..\base\base_unittests.vcproj
>> > ..\third_party\bzip2\bzip2.vcproj
>> > ..\net\crash_cache.vcproj
>> > ..\base\debug_message.vcproj
>> > But these are not:
>> > ..\googleurl\build\googleurl.vcproj
>> > ..\v8\tools\visual_studio\v8.vcproj
>> > ..\v8\tools\visual_studio\v8_base.vcproj
>> > ..\v8\tools\visual_studio\v8_mksnapshot.vcproj
>> > ..\v8\tools\visual_studio\v8_shell_sample.vcproj
>> > ..\v8\tools\visual_studio\v8_snapshot.vcproj
>> > ..\v8\tools\visual_studio\v8_snapshot_cc.vcproj
>> >
>> > Do you recall roughly when this was time wise?
>> > Did you have a local python installed, if so, what version?
>> > Let me know if this crops up again.
>> > -BradN
>> >
>> > On Wed, Mar 18, 2009 at 11:11 PM, Mohamed Mansour
>> > <[email protected]>
>> > wrote:
>> >>
>> >> Hi, I did what you said, and now getting other files which failed:
>> >>
>> >> ..\googleurl\build\googleurl.vcproj
>> >> ..\v8\tools\visual_studio\v8.vcproj
>> >> ..\v8\tools\visual_studio\v8_base.vcproj
>> >> ..\v8\tools\visual_studio\v8_mksnapshot.vcproj
>> >> ..\v8\tools\visual_studio\v8_shell_sample.vcproj
>> >> ..\v8\tools\visual_studio\v8_snapshot.vcproj
>> >> ..\v8\tools\visual_studio\v8_snapshot_cc.vcproj
>> >>
>> >> I did a gclient sync, and then got these previous errors (again):
>> >> ..\base\base.vcproj
>> >> ..\base\base_gfx.vcproj
>> >> ..\base\base_unittests.vcproj
>> >> ..\third_party\bzip2\bzip2.vcproj
>> >> ..\net\crash_cache.vcproj
>> >> ..\base\debug_message.vcproj
>> >>
>> >> So I deleted the complete folder associated with these projects which
>> >> were:
>> >> - googleurl
>> >> - v8
>> >> - base
>> >> - third_party\bzip2
>> >> - net
>> >> - base
>> >>
>> >> Then did a gclient sync, to grab them back, and it works now...
>> >>
>> >> So what caused this hickup? I never touched any of those files. If
>> >> someone knows why, it would be nice to know, so I can learn from my
>> >> mistakes.
>> >>
>> >> Thanks!
>> >>
>> >> -m0
>> >>
>> >> On Thu, Mar 19, 2009 at 12:09 AM, Alpha (Hin-Chung) Lam
>> >> <[email protected]> wrote:
>> >> > Looks like those project files are missing.
>> >> > After gclient sync, do:
>> >> > gclient runhooks --force
>> >> > to generate the project files from gyp.
>> >> >
>> >> > See if that helps.
>> >> >
>> >> > Alpha
>> >> >
>> >> > 2009/3/18 Mohamed Mansour <[email protected]>
>> >> >>
>> >> >> Hey there,
>> >> >>
>> >> >> I have some questions regarding the current build. It might be GYP
>> >> >> related, but I don't know yet ...
>> >> >>
>> >> >> Three days ago, the build was doing just fine. Today, I did a
>> >> >> gclient
>> >> >> sync and while converting the solution to VS2008, I am receiving a
>> >> >> bunch of errors. It wasn't doing so 3 days ago.
>> >> >>
>> >> >> I am receiving errors that has the following description "Failed to
>> >> >> upgrade project file. Please make sure the file exists and is not
>> >> >> write-protected." for these files:
>> >> >> ..\base\base.vcproj
>> >> >> ..\base\base_gfx.vcproj
>> >> >> ..\base\base_unittests.vcproj
>> >> >> ..\third_party\bzip2\bzip2.vcproj
>> >> >> ..\net\crash_cache.vcproj
>> >> >> ..\base\debug_message.vcproj
>> >> >>
>> >> >> Anyone has any idea what may have caused this?
>> >> >>
>> >> >>
>> >> >> -- m0
>> >> >>
>> >> >> >>
>> >> >
>> >> >
>> >>
>> >> >>
>> >
>> >
>
>
> >
>

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

Reply via email to