| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
Not so many systems require gtk+ 2.0 these days, let's move on.
This drops the old python bindings (non-gir based), and the
unsteady/experimental gtk2-only XShm support.
Signed-off-by: Marc-André Lureau <marcandre.lureau@gmail.com>
Acked-by: Fabiano Fidêncio <fidencio@redhat.com>
|
|
|
|
|
| |
For historical reasons, the code was placed under gtk/ subdirectory.
If it was always bugging you, bug no more!
|
|
|
|
|
| |
libspice-client-glib is useful as a client library on platforms that
don't support GTK.
|
| |
|
|
|
|
|
| |
Spice-GTK provides SPICE-specific command line options. This man page
describes these options as well as the format of SPICE URIs.
|
|
|
|
|
|
|
| |
The tests rely on static linking in order to get access to symbols which
are not exported in spice-gtk shared libraries. When build of static
libraries is disabled with --disable-static, we should not attempt to build
the tests as this will result in link errors.
|
|
|
|
| |
This is probably not exhaustive enough, but better than nothing.
|
| |
|
|
|
|
| |
It shouldn't be installed when controller support is disabled.
|
|
|
|
|
|
|
|
|
|
| |
With this iteration, all the spice_codegen.py/proto/marshaller
generation has been moved to spice-common.
The spice-common directory will ship spice-protocol, since it's needed
there too to build libspice-common.
Again, make distcheck passes. Build with mingw & fedora linux.
|
|
|
|
| |
Don't use DIST_SUBDIRS, it's not needed anyway.
|
| |
|
|
|
|
|
| |
gtk-doc.make is created by autogen.sh, therefore it should
not be deleted in distclean, only maintainerclean
|
|
|
|
|
|
| |
Spice protocol contains only headers. We would like to be able to use
a protocol update without having to wait for the release, a git
submodule works well for this purpose.
|
| |
|
|
|
|
|
|
|
|
|
| |
Currently, building vala bindings from a tarball is broken because
spice-client-glib-2.0.deps is missing from the tarball. This commit
adds it to EXTRA_DIST and also makes sure the vala bindings don't
get built/installed unless --enable-vala has been passed to configure.
This means vala must be installed to build the vala bindings from a
tarball. Fixes fdo bug #44000.
|
|
|
|
|
| |
They were work in progress and not meant to be committed, apologies
for the noise :-/
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Disable usbredir, since it wants to install file in /.
Disable vala for distcheck for 2 reasons: not needed after dist and
binding build issue.
Ship with spice-gtk-3.0 vala bindings
https://bugs.freedesktop.org/show_bug.cgi?id=44000
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The new configure flag '--with-gtk' can be used to choose
which GTK version to build against, defaulting to GTK2.
To enable GTK3 use
./configure --with-gtk=3.0
The libspice-client-glib-2.0.la library is unchanged, building
against glib-2.0 at all times.
The GTK3 build will produce a libspice-client-gtk-3.0.la
The include files will also live in $prefix/spice-client-gtk-3.0
and the pkgconfig is called spice-client-gtk-3.0 too.
This allows for full parallel install of GTK2 and GTK3 builds
|
|
|
|
|
|
|
|
|
|
|
| |
To allow easy parallel install of spice-gtk builds against GTK2
and GTK3, include the ABI version in the library names.
libspice-gtk.la -> libspice-gtk-2.0.la
libspice-glib.la -> libspice-glib-2.0.la
The PyGtk module doesn't change because that is obsolete and
unused in GTK3 world.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|