Thread necromancy: ARISE!
Sorry, was winding through old threads and came across this one. I just
did the whole protobuffer library --> javascript process yesterday, and i
didn't really have major issues.
One thing i _did_ need to do though was to make minor modifications to the
atomic_* portions of the codebase (basically, implement the most basic
possible primitives, since JS is single threaded) and make that file be
linked.
Was there a specific issue you were having?
-dave-
(Fair disclosure: I actually was emscripting a superset of the protobuffer
library called protorpc, easily found via google. However, for the JS
portion, i excluded the RPC additions and only emcc-compiled the
protobuffer stuff itself. Not out-of-the-box, but still no major problems)
On Friday, September 6, 2013 6:19:50 PM UTC-4, Jonathan Berling wrote:
>
> Sorry to side tract this discussion, but were you able to compile protobuf
> using emscripten? Or are you coding the javascript serialization of
> protobuf messages by hand?
>
> If you were able to compile protobuf using emscripten, do you have any
> pointers?
>
> Thanks!
>
> On Tuesday, March 26, 2013 4:02:28 AM UTC-7, Marcos Scriven wrote:
>>
>> Thanks for the suggestion, I've not heard about 'bump allocators', but if
>> I can copy a chunk of memory like that that's just going to be so much
>> faster.
>>
>> Incidentally I'm using Google protobuf (also obviously compiled to
>> Javascript) for the other simpler objects (which still requires manual
>> mapping from objects to protobuf messages) and that's lightning fast.
>>
>
--
You received this message because you are subscribed to the Google Groups
"emscripten-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
