Refer internal PIEX library by using <include> tag in piex.pexe.txt.

Refer internal PIEX library by using <include> tag in piex.pexe.txt.

We put PIEX internal library in ui/file_manager/internal directory. The
problem is we cannot access the resources in the directory by using
chrome-extension:// URL because it's not under extension directory.

Previously we prepared the dummy file of PIEX file in image_loader
extension, and assigns the same resource ID both to the dummy file and
internal library. It enabled the image loader extension to access
internal library via the URL of dummy file.

The CL removes the hack and adds <include> tag to the dummy file. The
contents of dummy file is replaced with the internal library by
<include> tag at the compile time.

BUG=642924
TEST=load raw file with official chrome

Committed: https://crrev.com/55e10010b0e3c851165f7b8af4465d05d525d729
Cr-Commit-Position: refs/heads/master@{#416358}

[hirono, 2016-09-02 05:13:32]

hirono@chromium.org changed reviewers:
+ fukino@chromium.org, thestig@chromium.org

[hirono, 2016-09-02 05:13:33]

PTAL, thank you!

[fukino, 2016-09-02 05:22:01]

LGTM. Thank you for the fix.

[hirono, 2016-09-02 05:22:56]

The CQ bit was checked by hirono@chromium.org

[hirono, 2016-09-02 05:23:11]

On 2016/09/02 05:22:01, fukino wrote:
> LGTM. Thank you for the fix.

Thank you for reviewing!

[commit-bot: I haz the power, 2016-09-02 05:23:11]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-09-02 05:27:19]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-09-02 05:27:20]

Try jobs failed on following builders:
  linux_chromium_chromeos_compile_dbg_ng on master.tryserver.chromium.linux
(JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
  linux_chromium_chromeos_ozone_rel_ng on master.tryserver.chromium.linux
(JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
  linux_chromium_chromeos_rel_ng on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
  linux_chromium_clobber_rel_ng on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
  linux_chromium_compile_dbg_ng on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
  linux_chromium_rel_ng on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[Lei Zhang, 2016-09-02 21:13:31]

The CQ bit was checked by thestig@chromium.org

[commit-bot: I haz the power, 2016-09-02 21:13:59]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-09-02 21:59:51]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-09-02 22:03:39]

Description was changed from

==========
Refer internal PIEX library by using <include> tag in piex.pexe.txt.

We put PIEX internal library in ui/file_manager/internal directory. The
problem is we cannot access the resources in the directory by using
chrome-extension:// URL because it's not under extension directory.

Previously we prepared the dummy file of PIEX file in image_loader
extension, and assigns the same resource ID both to the dummy file and
internal library. It enabled the image loader extension to access
internal library via the URL of dummy file.

The CL removes the hack and adds <include> tag to the dummy file. The
contents of dummy file is replaced with the internal library by
<include> tag at the compile time.

BUG=642924
TEST=load raw file with official chrome
==========

to

==========
Refer internal PIEX library by using <include> tag in piex.pexe.txt.

We put PIEX internal library in ui/file_manager/internal directory. The
problem is we cannot access the resources in the directory by using
chrome-extension:// URL because it's not under extension directory.

Previously we prepared the dummy file of PIEX file in image_loader
extension, and assigns the same resource ID both to the dummy file and
internal library. It enabled the image loader extension to access
internal library via the URL of dummy file.

The CL removes the hack and adds <include> tag to the dummy file. The
contents of dummy file is replaced with the internal library by
<include> tag at the compile time.

BUG=642924
TEST=load raw file with official chrome

Committed: https://crrev.com/55e10010b0e3c851165f7b8af4465d05d525d729
Cr-Commit-Position: refs/heads/master@{#416358}
==========

[commit-bot: I haz the power, 2016-09-02 22:03:40]

Patchset 1 (id:??) landed as
https://crrev.com/55e10010b0e3c851165f7b8af4465d05d525d729
Cr-Commit-Position: refs/heads/master@{#416358}