Hi,all!
After I workaround the bug "input will choke output",I'm glad to
release the USABLE androidSpice-0.1.4 on google code:
http://code.google.com/p/spice-client-android/
You shall check the wiki page of it for the build/install/use of it.
Any use or improvement will be appreciated!
Best Reg
Hi,
Well,since I really don't want to get into the dirt of coroutine_*()
funcs, I force the input-channel to be ready in spice-channel.c by
change
ret = g_io_wait_interruptable(&c->wait, c->sock, G_IO_IN);
to
ret = G_IO_IN;
Now,anyway,IT WORKS,it will never hesitate to receive data from
server,t
Now confirmed,it will fall in dead loop in spice_channel_iterate() for
g_io_wait_interruptable()-->coroutine_yield()-->coroutine_swap() because
coroutine_swap() always returns NULL, how to fix this? Any spice-gtk guys
can help me?
Rgrds.
On Mon, Apr 25, 2011 at 9:08 PM, Shuxiang Lim wrote:
> A
When trying to port the alsa-lib to OS/X while porting Spice to OS/X I am
having some difficulties resolving issues with alsa-lib. I am using
alsa-lib-1.0.24.1
After doing a ./configure - I have also tried
./configure --enable-shared=no --enable-static=yes
Either way I get the following error
Hi,
>
> I am confused, because the git master branch had the version 0.8
> bumped only last week.
A 0.8 branch was created from master in late February/early March, and the
version number was changed in that branch shortly *after* the branch was
created. So the version number between the branc
Hi,Kai,
Yep,all the sin of Android is its framework: Java UI layer. But since
there are the ARM optimization for dalvik VM, as well as the opengl
ES/alsalib APIs for Java in Android, it's worthy trying to achieve
a completely Java porting ONLY IF your have enough time/energy/bugget of
this...
- Original Message -
> Hi,
>
> On 04/24/2011 07:21 PM, Marc-André Lureau wrote:
> > Hi,
> >
> > Doh! I forgot to bump the minimal spice-protocol dependency to 0.8.
> > Unfortunately, this release is yet to be made.
> >
>
> Erm, spice-protocol-0.8.0 has been released for a while now, so I
After some tracing work: I found that,when no input occurs in the
client,the output flow from server to client may be jammed by the slow
network but will never be choked.But when there's input, the client
will always fall soon in the endless calling for coroutine_yield() and
coroutine_swap() in cor
Hi,
On 04/24/2011 07:21 PM, Marc-André Lureau wrote:
Hi,
Doh! I forgot to bump the minimal spice-protocol dependency to 0.8.
Unfortunately, this release is yet to be made.
Erm, spice-protocol-0.8.0 has been released for a while now, so I don't
understand what you mean with "this release is y
