Which build was this? I checked in a change that changes how grit
generates IDs. This type of change requires a clobber since I don't
think we depend on all the grit .py files. I think these changes are
rare enough that we can just clobber as needed.
On Thu, Sep 24, 2009 at 12:03 PM, Paweł Hajdan Jr.
<phajdan...@chromium.org> wrote:
> We still have problems with resources, examples:
>
> [FATAL:tab_renderer.cc(132)] Check failed: waiting_animation_frames->width()
> % waiting_animation_frames->height() == 0.
>
> [FATAL:image_operations.cc(373)] Check failed: rgb.width() == alpha.width().
>
> [FATAL:resource_bundle_win.cc(155)] Check failed: false. unable to find
> resource: 1495
>
> [FATAL:resource_bundle_win.cc(152)] Check failed: false. unable to find
> resource: 1500
>
> And of course these are intermittent. :(
> Can we rebuild the resources always, on Windows? I know it's going to
> increase the compile time. How much?
> >
>
--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
