[jumbo] avoid g_next_id collision in cc
We can avoid the jumbo build error mentioned below, by replacing these (translation unit) global g_next_id variables with static class variables: ./../../cc/paint/raw_memory_transfer_cache_entry.cc:13:28: error: redefinition of 'g_next_id' base::AtomicSequenceNumber g_next_id; ^ ./../../cc/paint/image_transfer_cache_entry.cc:15:28: note: previous definition is here base::AtomicSequenceNumber g_next_id; Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel Change-Id: I320f03d6147ca0d2e29ad75573735e9860c4ee99 Reviewed-on: https://chromium-review.googlesource.com/823032 Commit-Queue: Mostyn Bramley-Moore <mostynb@vewd.com> Reviewed-by:danakj <danakj@chromium.org> Cr-Commit-Position: refs/heads/master@{#523616}
Showing
Please register or sign in to comment