I'm pretty new to NaCl, but I've had no problems getting Chrome to run .nexe files.
I've started to look into PNaCl, because the idea of having a single binary rather than three is very desirable. However, I have yet to successfully get any version of Chrome to run a .pexe file directly.
So, I'm assuming Chrome simply doesn't support this yet. If I'm correct, does anyone have a guess as to when it will be supported?
If I'm incorrect, can someone point me to a working example of loading a .pexe file directly?
Thanks... I've enabled the flag, but I've tried pretty much everything I can think of to get Chrome 26 (dev channel) to load the .pexe file directly, with no luck. If I use pnacl-translate to convert the .pexe to .nexe files manually, the .nexe files load just fine.
Have you actually gotten this flag to work properly?
> native-client-discuss+unsub...@googlegroups.com.
I'm not sure if the PNaCl translator binaries are shipped with chrome. Chrome won't be able to use the version that is in the SDK, I don't think. You might have to build chromium from sources-- possibly changing the build config-- in order to try it. NB: I've never tried this either.
plz xqz tpos, rplyng by fone
To view this discussion on the web visit https://groups.google.com/d/msg/native-client-discuss/-/XAMZKfzrk4EJ.
To post to this group, send email to native-cli...@googlegroups.com.
To unsubscribe from this group, send email to native-client-di...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/native-client-discuss?hl=en.
--
Fernando
Chrome doesn't yet support .pexe files directly, but if you want to experiment with this early preview of PNaCl, the toolchain includes a tool to translate .pexe files into architecture-specific .nexe files. Take a look at the hello_world example to see how to build a .pexe file and translate it into multiple .nexe files. Note that PNaCl is currently restricted to the newlib C standard library – if your application uses glibc, you can't build it with PNaCl.
To view this discussion on the web visit https://groups.google.com/d/msg/native-client-discuss/-/XAMZKfzrk4EJ.
To unsubscribe from this group, send email to native-client-di...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/native-client-discuss?hl=en.
--
Fernando
--
You received this message because you are subscribed to the Google Groups "Native-Client-Discuss" group.
To view this discussion on the web visit https://groups.google.com/d/msg/native-client-discuss/-/XAMZKfzrk4EJ.
To post to this group, send email to native-cli...@googlegroups.com.
To unsubscribe from this group, send email to native-client-discuss+unsub...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/native-client-discuss?hl=en.
--
Christian Stefansen
To view this discussion on the web visit https://groups.google.com/d/msg/native-client-discuss/-/6CeOQWIgevwJ.
To unsubscribe from this group, send email to native-client-di...@googlegroups.com.