Move plugin messages to content.

Move plugin messages to content.

TBR=tsepez

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=78099

[Tom Sepez, 2011-03-14 19:58:24]

LGTM once it links.  One thing to try is to preserve a plugin_messages.cc file,
so that the chrome_frame_unittests, when it pulls in common_message_generator.o
doesn't have to resolve the plugin dependencies.

[jam, 2011-03-14 20:22:02]

On 2011/03/14 19:58:24, Tom Sepez wrote:
> LGTM once it links.  One thing to try is to preserve a plugin_messages.cc
file,
> so that the chrome_frame_unittests, when it pulls in
common_message_generator.o
> doesn't have to resolve the plugin dependencies.

I fixed the chrome_frame_unittest linking by adding more functions to
renderer_glue.cc.  I find how that target links is very fragile.  I don't think
we should make plugin_messages generation more complicated than necessary
because of this target though.

[jam, 2011-03-14 20:29:44]

CCing Ananta: can we add the necessary dependencies on
chrome_frame_unittests?

On Mon, Mar 14, 2011 at 1:22 PM, <jam@chromium.org> wrote:

> On 2011/03/14 19:58:24, Tom Sepez wrote:
>
>> LGTM once it links.  One thing to try is to preserve a plugin_messages.cc
>>
> file,
>
>> so that the chrome_frame_unittests, when it pulls in
>>
> common_message_generator.o
>
>> doesn't have to resolve the plugin dependencies.
>>
>
> I fixed the chrome_frame_unittest linking by adding more functions to
> renderer_glue.cc.  I find how that target links is very fragile.  I don't
> think
> we should make plugin_messages generation more complicated than necessary
> because of this target though.
>
>
> http://codereview.chromium.org/6682033/
>