New issue
Advanced search Search tips

Issue 611548 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Apr 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Investigate video_decode and video_decode_dev targets in chromeos-chrome ebuild

Project Member Reported by steve...@chromium.org, May 12 2016

Issue description

In the chromeos-chrome ebuild with -gn (GYP build), we currently get the following error when we build:

chromeos-chrome-52.0.2730.0_rc-r1: x86_64-cros-linux-gnu-strip: '/var/cache/chromeos-chrome/chrome-src/src/out_amd64-generic/Release/ppapi_example_video_decode': No such file

Looking for files with 'video_decode', the following file is generated:
obj/ppapi/examples/video_decode

According to ihf@:

"Actually there should be 2 binaries, video_decode and video_decode_dev. video_decode_dev is more important, as it mimics Flash's behavior, at least a little."

However there is no sign of video_decode_dev being built.

We should investigate:
* Why video_decode_dev is not getting built
* Confirm that video_decode and/or video_decode_dev are getting copied from the correct location to the correct destination for both GYP and GN

At the moment, with https://chromium-review.googlesource.com/#/c/344420, the ebuild will build ppapi_example_video_decode  in GYP, ppapi/examples/video_decode in GN, and copy Release/out/ppapi/examples/video_decode to the staging directory.

 
I couldn't find any users of these targets by casually grepping "ppapi_example_video_decode", "video_decode", and "video_decode_dev" in Chrome OS checkout.
How are they going to be used?
For manual testing?

Comment 3 by ihf@chromium.org, May 13 2016

Will need their own autotest. Boilerplate.

Comment 4 by ihf@chromium.org, Apr 22 2017

Obsolete.

Comment 5 by ihf@chromium.org, Apr 22 2017

Status: WontFix (was: Assigned)
Obsolete.

Sign in to add a comment