On Thu, Apr 9, 2015 at 7:15 PM, cesar pachon <
cesar...@gmail.com> wrote:
> hello Sam, thank you for replying!
>
> as in understand, ppapi_simple is the interface between js and native code,
> and it is by nature async.. so, yes, I am using it.
>
> but, as you mention, in the native code, the file I/O operations seems to be
> required to be used in another (native) thread. I am using that too.
If you are using ppapi_simple then your main function is already
running on a background thread. You don't need to create another.
> as you guess correctly, ffmpeg has methods that are supposed to create the
> output file based on a string (path), but when you try these methods inside
> NACL, they fail with a message that says something like "native operations
> are not implemented" or similar. my understanding is that all the standard
> fopen, fread, etc methods had been overrided to empty impliementations in
> NACL for security reasons, and you are forced to use the nacl_io versions,
> that are not directly consumible for the normal ffmpeg methods.
nacl_io, allows applications to use standard POSIX file I/O APIs such
as fopen/open fread/read, etc. So if you are linking it in and
initializing it correctly ffmpeg should not be getting such error
messages. Also, ppapi_simple will initialize nacl_io on startup for
you. Are you sure you use linking the ppapi_simple library and
using it to run your main function?
>> > email to
native-client-di...@googlegroups.com.
> --
> 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.