Yes, that would be the ultimate solution (i.e. a single binary).
However, trying to build glib (as fluidsynth requires glib) using
pepper30 sdk, I could only manage to build it for x86_32 and x86_64 but
not for arm nor pnacl (i.e. it is just considered as a target
architecture for the tools). I
You guys heard Portable Native Client (PNaCl)?
On Wed, Nov 13, 2013 at 3:19 AM, Alexandre Roux Tekartik
wrote:
> Thanks for the responses. That sounds all good to motivate me to start on
> it. I started to play with both fluidsynth and nacl sdk.
> The first blocker I had was that glib is needed
Thanks for the responses. That sounds all good to motivate me to start
on it. I started to play with both fluidsynth and nacl sdk.
The first blocker I had was that glib is needed for fluidsynth but
fortunately I did found a nacl port for it.
https://code.google.com/p/naclports/ contains port of
I've actually been thinking about doing the same thing (although I haven't
started or done any kind of feasibility study).
However, I know my way around NaCl/Pepper pretty well (I have been working
with the Pepper team to add new APIs). I can't think of a reason why this
would be a problem (other
On 11/12/2013 12:48 AM, Alexandre Roux Tekartik wrote:
> Hi all,
> I'm interested in playing midi files/event from a web application in the
> chrome desktop application.
> As anyone considered compiling fluidsynth as a native Chrome extension?
> Does NaCl SDK ( https://developers.google.com/native-
