Hi,
that worked, but I had to change it in all configure.ac files:
configure.ac
spice-common/configure.ac
spice-common/spice-protocol/configure.ac
After that I ran into the next issue:
make[4]: Entering directory `/usr/src/spice-gtk-20140507/spice-common/common'
Makefile:511: .deps/gen
Hi
- Original Message -
> But for spice-gtk I always get this error when running autoconf.sh (or
> actually autoreconf -v --force --install):
>
> …
I am not sure what's going on, but you should check the "Fix build with
automake 1.14" thread: patches are still missing in git (although
Hi,
I just tried to build spice from source.
spice and spice-protocol worked without problem.
But for spice-gtk I always get this error when running autoconf.sh (or actually
autoreconf -v --force --install):
...
automake: warnings are treated as errors
common/Makefile.am:4: warning: source file
Hi,
I just had a look at the spice repositories and I saw that the last spice
(server) release was done 10 month ago and a lot of changes were done since
then.
Is there any plan to release a "new" version of spice and spice-protocol?
Thanks, Klaus
___
On 05/06/2014 02:35 PM, Marc-André Lureau wrote:
Hi
- Original Message -
I patched gtk3 with the attached and the problem seems fixed. Note: I
added the cairo_surface_destroy in gdkcursor.c because:
1) symmetry - it's allocated there
2) looking at a few of the different backends, the
Hi
- Original Message -
>
> I patched gtk3 with the attached and the problem seems fixed. Note: I
> added the cairo_surface_destroy in gdkcursor.c because:
>
> 1) symmetry - it's allocated there
> 2) looking at a few of the different backends, they don't appear to have
> a cairo_surface
On 05/06/2014 11:12 AM, Marc-André Lureau wrote:
- Original Message -
Hi
- Original Message -
On 05/06/2014 09:49 AM, David Mansfield wrote:
On 05/06/2014 06:04 AM, Marc-André Lureau wrote:
Hi
- Original Message -
On 05/05/2014 04:10 PM, Marc-André Lureau wrote:
- Original Message -
> Hi
>
> - Original Message -
> >
> > On 05/06/2014 09:49 AM, David Mansfield wrote:
> > >
> > > On 05/06/2014 06:04 AM, Marc-André Lureau wrote:
> > >> Hi
> > >>
> > >> - Original Message -
> > >>> On 05/05/2014 04:10 PM, Marc-André Lureau wrote:
>
Hi
- Original Message -
>
> On 05/06/2014 09:49 AM, David Mansfield wrote:
> >
> > On 05/06/2014 06:04 AM, Marc-André Lureau wrote:
> >> Hi
> >>
> >> - Original Message -
> >>> On 05/05/2014 04:10 PM, Marc-André Lureau wrote:
> Hi
>
> - Original Message -
>
Yeah, lack of documentation and lack of hardware level development experience
is now the biggest problem for me.
The five documents on spice-space website have been read over and over again by
me, trying to figure out something that will help understand the source code.
Sadly, I just got somethi
On 05/06/2014 09:49 AM, David Mansfield wrote:
On 05/06/2014 06:04 AM, Marc-André Lureau wrote:
Hi
- Original Message -
On 05/05/2014 04:10 PM, Marc-André Lureau wrote:
Hi
- Original Message -
Any way to easily trace memory leaks in remote-viewer? A naive
attempt
at "val
On 05/06/2014 06:04 AM, Marc-André Lureau wrote:
Hi
- Original Message -
On 05/05/2014 04:10 PM, Marc-André Lureau wrote:
Hi
- Original Message -
Any way to easily trace memory leaks in remote-viewer? A naive attempt
at "valgrind remote-viewer spice://blah" didn't turn up a
Hi
- Original Message -
> Then, I got another question. If all the commands are sent to client
> gennerally as long as the network is not so bad, does spice need to
> evaluate
> client resource in advance, or it just checks network congestion situation？
Take what I say with some distance
Then, I got another question. If all the commands are sent to client gennerally
as long as the network is not so bad, does spice need to evaluate
client resource in advance, or it just checks network congestion situation？
For now, I know that file spice/server/red_worker.c and
spice/server/red
Hi
- Original Message -
> Hi all,
>
> During the past days, I was dedicated to build, configure the spice source
> code to achieve the desired performance. But several questions, or you can
> call them suggestions, occurred to me when the remote desktop did as they
> were expected.
>
> s
Hi
- Original Message -
>
> On 05/05/2014 04:10 PM, Marc-André Lureau wrote:
> > Hi
> >
> > - Original Message -
> >> Any way to easily trace memory leaks in remote-viewer? A naive attempt
> >> at "valgrind remote-viewer spice://blah" didn't turn up anything in
> >> particular.
>
Hi all,
During the past days, I was dedicated to build, configure the spice source code
to achieve the desired performance. But several questions, or you can call them
suggestions, occurred to me when the remote desktop did as they were expected.
spice is claimed to be able to "intelligently as
17 matches
Mail list logo
