Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Building PPAPI #10

Open
GoogleCodeExporter opened this issue Jun 21, 2015 · 3 comments
Open

Building PPAPI #10

GoogleCodeExporter opened this issue Jun 21, 2015 · 3 comments

Comments

@GoogleCodeExporter
Copy link

I'm trying to create a PPAPI plugin (dll, .so, etc) similar to the Flash Player 
(but much simpler). I need this in order to work around the deprecation of 
NPAPI :(

I don't want it to be inside NaCl. That's why I believe that the NaCl SDK is 
useless for this? Reason being I need access to read/write to the file system.

I've checked out the code, but have pretty much no idea how to build it. All 
guides out there seem to be talking about building NaCl rather than pure 
pepper. I created a VS 2010 project and added the files, but it's giving me so 
many errors.

"expecting an interface name or DispatchInterfaceName or CoclassName or 
ModuleName or LibraryName or ContractName or a type specification near "label" 
(ppb_audio_input_dev.idl)"

Is there a toolchain or guide for doing this?

Thanks!

Original issue reported on code.google.com by ash...@o-minds.com on 15 Dec 2014 at 4:40

@GoogleCodeExporter
Copy link
Author

i am facing same problem as you. did you find anything that can help with this?
thanks

Original comment by gau.ko...@gmail.com on 12 May 2015 at 8:30

@GoogleCodeExporter
Copy link
Author

Dead end. Don't bother. All in all, pepper without nacl will be killed except 
for a number of pre-select pepper plugins (e.g. Flash), and the only way to 
install a pepper plugin without nacl is through command line arguments, and as 
I was informed by some, Chrome may remove these command line arguments any 
minute since they might decide they're a security risk.

Your best bet is the Chrome messaging API which allows your extension to 
register a program and communicate with it. The program has access to 
everything.

https://developer.chrome.com/extensions/nativeMessaging

For me, I've dropped support for the Chrome browser altogether.

Original comment by ash...@o-minds.com on 12 May 2015 at 8:37

@GoogleCodeExporter
Copy link
Author

thanks for your time 

Original comment by gau.ko...@gmail.com on 12 May 2015 at 10:00

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant