Using NACL plugin

[madana gopal]

Hi Team,

 

I am new to NACL and working with it for a web application. I am seeing the NACL plugin is coming .a file (libnacl_trusted_plugin.a), with recent version of chromium instead of libppGoogleNaClPluginChrome.so (i.e no GYP target for it). So, if we are not using register-pepper-plugins for it, then how can initiate/invoke with static library (i.e how to make NACL plugin to load). Please help on this. Thanks.

 

Regards,

Madan

 

[madana gopal]

Hi,

Could anybody please provide hint for my above query. Thanks.

 

Regards,

Madan

[Sam Clegg]

NaCl/PNaCl ships as part of chromium. There should be no need to use
--register-pepper-plugins. NaCl itself is a only available to
packaged apps, while PNaCl is available on the open web.

cheers,
sam

> --
> You received this message because you are subscribed to the Google Groups
> "Native-Client-Discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to native-client-di...@googlegroups.com.
> To post to this group, send email to native-cli...@googlegroups.com.
> Visit this group at http://groups.google.com/group/native-client-discuss.
> For more options, visit https://groups.google.com/d/optout.

[madana gopal]

Fine. One more doubt on this.

When i give chrome://plugins, it is telling Native client path as

/opt/google/chrome/internal-nacl-plugin. But there is no such file with the above name. If you know, could you please tell how it picks the library. Thanks. Regards, Madan

[Jan Voung]

Right, there isn't such a file. As you said earlier:

"I am seeing the NACL plugin is coming .a file (libnacl_trusted_plugin.a), with recent version of chromium instead of libppGoogleNaClPluginChrome.so (i.e no GYP target for it)."

The NaCl chrome integration implementation code is now in a static library and statically linked into the chrome renderer. There isn't a mechanism for dynamically overriding that implementation code. You would have to relink. What is it that you would like to do?

The "location" shown in chrome://plugins/ is just filler to fill in that field of the UI.The location might be able to be shortened to just "internal-nacl-plugin" to make that clear. The chrome://plugins/ UI still shows NaCl so that you can enable/disable it, despite it being statically linked in.

[madana gopal]

Thanks for the information. We have a requirement to integrate NACL to CEF based browser. There we are facing some problems  in integration and comparing chrome browser for the same. Also, nexe files is not being read. I suspect the problem is sel_dlr process is not launched. Do you have some ideas on this?.

Regards,

Madan

[Jan Voung]

Ah, you want NaCl support with CEF.

Please see comment 7 in https://bitbucket.org/chromiumembedded/cef/issue/705.

You may need to do a build with the GYP variable DISABLE_NACL=0 instead of =1. Quote: "Usage of the "DISABLE_NACL" macro in src/chrome can provide rough guidance on the necessary changes". I haven't looked at the CEF code, so I'm not sure if they use gyp and simply set DISABLE_NACL=1 in CEF, or what is meant by "rough guidance".

In standard chromium, DISABLE_NACL=1 will prevent libnacl_trusted_plugin.a from being built and linked into the renderer. It also prevents other required artifacts from being built like the NaCl IRT. Other notes: http://stackoverflow.com/questions/23645503/does-cef3-support-nacl.

- Jan

--

[madana gopal]

Thanks. Yes,we have already done the changesasper the link you shared.It is good.

 

But some how manifest file contents are not getting loaded. So, we suspect some problem with integration with sel_ldr. Another thing is NaClLog() is not coming. If we are able to get that output, we can see where exactly it is failing. Do you have idea on how to enable it?. I gone through a link where they have mentioned to set some log verbosity and it will generate log files. Please share if you have any idea on this.