|
|
Created:
6 years, 4 months ago by Alpha Left Google Modified:
6 years, 3 months ago CC:
chromium-reviews, hclam+watch_chromium.org, imcheng+watch_chromium.org, chromoting-reviews_chromium.org, hguihot+watch_chromium.org, jasonroberts+watch_google.com, avayvod+watch_chromium.org, pwestin+watch_google.com, feature-media-reviews_chromium.org, miu+watch_chromium.org, hubbe+watch_chromium.org, mikhal+watch_chromium.org Base URL:
svn://svn.chromium.org/chrome/trunk/src Project:
chromium Visibility:
Public. |
DescriptionDon't use libvpx if it is disabled in GN build
This change excludes libvpx from linking if it is disabled. This is
needed to enable linking Chrome with GN, since libvpx is not building
with GN yet.
Committed: https://crrev.com/a14f01541605edd7538b2faa24b766060f0d5d46
Cr-Commit-Position: refs/heads/master@{#292457}
Patch Set 1 #
Total comments: 2
Patch Set 2 : fake codec #
Total comments: 2
Patch Set 3 : fixed comments #Patch Set 4 : fix build #
Messages
Total messages: 46 (0 generated)
hclam@chromium.org changed reviewers: + hubbe@chromium.org, sergeyu@chromium.org
brettw@chromium.org changed reviewers: + brettw@chromium.org
lgtm https://codereview.chromium.org/501153003/diff/1/media/cast/sender/video_enco... File media/cast/sender/video_encoder_impl.cc (right): https://codereview.chromium.org/501153003/diff/1/media/cast/sender/video_enco... media/cast/sender/video_encoder_impl.cc:89: #endif // if !defined(MEDIA_DISABLE_LIBVPX) Did you mean to wrap the fake one in this block as well?
On 2014/08/26 01:08:26, Alpha wrote: What's the point of building cast without vpx?
On 2014/08/26 17:51:53, hubbe wrote: > On 2014/08/26 01:08:26, Alpha wrote: > > What's the point of building cast without vpx? It's not converted to GN yet and will take some more time to convert.
https://codereview.chromium.org/501153003/diff/1/media/cast/sender/video_enco... File media/cast/sender/video_encoder_impl.cc (right): https://codereview.chromium.org/501153003/diff/1/media/cast/sender/video_enco... media/cast/sender/video_encoder_impl.cc:89: #endif // if !defined(MEDIA_DISABLE_LIBVPX) On 2014/08/26 03:14:21, brettw wrote: > Did you mean to wrap the fake one in this block as well? Acknowledged.
That's only for the GN build. GYP build has libvpx support. GN build is work in progress.
On 2014/08/26 17:59:21, Alpha wrote: > That's only for the GN build. GYP build has libvpx support. GN build is work in > progress. But building cast without VPX is like a hedgehog without spines: pointless.
On 2014/08/26 18:33:26, hubbe wrote: > On 2014/08/26 17:59:21, Alpha wrote: > > That's only for the GN build. GYP build has libvpx support. GN build is work > in > > progress. > > But building cast without VPX is like a hedgehog without spines: pointless. Being able to build and link Chrome with GN is not pointless. GN is work in progress. It's not going to have all features in one go. The alternative is to exclude cast related source files from linking in Chrome but that affects a lot more files.
On 2014/08/26 18:33:26, hubbe wrote: > On 2014/08/26 17:59:21, Alpha wrote: > > That's only for the GN build. GYP build has libvpx support. GN build is work > in > > progress. > > But building cast without VPX is like a hedgehog without spines: pointless. It's very important that we can link chrome ASAP so that the buildbots will catch errors when people introduce linker errors in the GN build. Currently it's easy to add a file to the GYP build and forget to add it to the GN build, and no error will be thrown because there is no final target linking everything together. This and webrtc at the only things preventing this at this point.
On 2014/08/26 19:21:05, brettw wrote: > On 2014/08/26 18:33:26, hubbe wrote: > > On 2014/08/26 17:59:21, Alpha wrote: > > > That's only for the GN build. GYP build has libvpx support. GN build is work > > in > > > progress. > > > > But building cast without VPX is like a hedgehog without spines: pointless. > > It's very important that we can link chrome ASAP so that the buildbots will > catch errors when people introduce linker errors in the GN build. Currently it's > easy to add a file to the GYP build and forget to add it to the GN build, and no > error will be thrown because there is no final target linking everything > together. > > This and webrtc at the only things preventing this at this point. LGTM As long as this is reverted once VPX actually works, since it's not a configuration we actually want to support.
Thanks. This will be reverted once we have libvpx building with GN. ping sergeyu@.
Ideally remoting/protocol/session_config.cc should be updated to disabled VP8 codec when libvpx is disabled (see CandidateSessionConfig::CreateDefault()). LGTM with that change. https://codereview.chromium.org/501153003/diff/20001/remoting/client/software... File remoting/client/software_video_renderer.cc (right): https://codereview.chromium.org/501153003/diff/20001/remoting/client/software... remoting/client/software_video_renderer.cc:20: #include "remoting/codec/video_decoder_vpx.h" nit: remove if. It should look as follows #endif // !defined(MEDIA_DISABLE_LIBVPX) https://codereview.chromium.org/501153003/diff/20001/remoting/client/software... remoting/client/software_video_renderer.cc:158: #endif // if !defined(MEDIA_DISABLE_LIBVPX) Same here
On 2014/08/26 20:32:41, Sergey Ulanov wrote: > Ideally remoting/protocol/session_config.cc should be updated to disabled VP8 > codec when libvpx is disabled (see CandidateSessionConfig::CreateDefault()). > LGTM with that change. > > https://codereview.chromium.org/501153003/diff/20001/remoting/client/software... > File remoting/client/software_video_renderer.cc (right): > > https://codereview.chromium.org/501153003/diff/20001/remoting/client/software... > remoting/client/software_video_renderer.cc:20: #include > "remoting/codec/video_decoder_vpx.h" > nit: remove if. It should look as follows > #endif // !defined(MEDIA_DISABLE_LIBVPX) > > https://codereview.chromium.org/501153003/diff/20001/remoting/client/software... > remoting/client/software_video_renderer.cc:158: #endif // if > !defined(MEDIA_DISABLE_LIBVPX) > Same here Done all.
The CQ bit was checked by hclam@chromium.org
CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/hclam@chromium.org/501153003/40001
FYI, CQ is re-trying this CL (attempt #1). The failing builders are: android_clang_dbg on tryserver.chromium.linux (http://build.chromium.org/p/tryserver.chromium.linux/builders/android_clang_d...)
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: android_clang_dbg on tryserver.chromium.linux (http://build.chromium.org/p/tryserver.chromium.linux/builders/android_clang_d...)
The CQ bit was checked by hclam@chromium.org
CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/hclam@chromium.org/501153003/40001
FYI, CQ is re-trying this CL (attempt #1). The failing builders are: android_clang_dbg on tryserver.chromium.linux (http://build.chromium.org/p/tryserver.chromium.linux/builders/android_clang_d...)
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: android_clang_dbg on tryserver.chromium.linux (http://build.chromium.org/p/tryserver.chromium.linux/builders/android_clang_d...)
The CQ bit was checked by hclam@chromium.org
CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/hclam@chromium.org/501153003/40001
FYI, CQ is re-trying this CL (attempt #1). The failing builders are: android_clang_dbg on tryserver.chromium.linux (http://build.chromium.org/p/tryserver.chromium.linux/builders/android_clang_d...)
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: android_clang_dbg on tryserver.chromium.linux (http://build.chromium.org/p/tryserver.chromium.linux/builders/android_clang_d...)
The CQ bit was checked by hclam@chromium.org
CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/hclam@chromium.org/501153003/40001
FYI, CQ is re-trying this CL (attempt #1). The failing builders are: android_arm64_dbg_recipe on tryserver.chromium.linux (http://build.chromium.org/p/tryserver.chromium.linux/builders/android_arm64_d...) android_clang_dbg_recipe on tryserver.chromium.linux (http://build.chromium.org/p/tryserver.chromium.linux/builders/android_clang_d...)
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: android_arm64_dbg_recipe on tryserver.chromium.linux (http://build.chromium.org/p/tryserver.chromium.linux/builders/android_arm64_d...) android_clang_dbg_recipe on tryserver.chromium.linux (http://build.chromium.org/p/tryserver.chromium.linux/builders/android_clang_d...)
The CQ bit was checked by hclam@chromium.org
CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/hclam@chromium.org/501153003/40001
FYI, CQ is re-trying this CL (attempt #1). The failing builders are: android_arm64_dbg_recipe on tryserver.chromium.linux (http://build.chromium.org/p/tryserver.chromium.linux/builders/android_arm64_d...) android_clang_dbg_recipe on tryserver.chromium.linux (http://build.chromium.org/p/tryserver.chromium.linux/builders/android_clang_d...)
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: android_arm64_dbg_recipe on tryserver.chromium.linux (http://build.chromium.org/p/tryserver.chromium.linux/builders/android_arm64_d...) android_clang_dbg_recipe on tryserver.chromium.linux (http://build.chromium.org/p/tryserver.chromium.linux/builders/android_clang_d...)
The CQ bit was checked by hclam@chromium.org
The CQ bit was unchecked by hclam@chromium.org
The CQ bit was checked by hclam@chromium.org
CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/hclam@chromium.org/501153003/60001
Message was sent while issue was closed.
Committed patchset #4 (id:60001) as 70b18bc45630f53206b6b464d8516d6e4a958efd
Message was sent while issue was closed.
Patchset 4 (id:??) landed as https://crrev.com/a14f01541605edd7538b2faa24b766060f0d5d46 Cr-Commit-Position: refs/heads/master@{#292457} |