Each subdir (common, client and server) can "make dist".
This commit adds configure.ac.shared and autogen.sh to the tar file.
Above files are copied from .. (spice/ directory)
Also added configure.ac.shared (which is not part of "distribution" tarball)
that only imports ../configure.ac.shared such that ./autogen.sh still
works (on "git directories").
Signed-off-by: Uri Lublin <uril@redhat.com>
Define them with ./configure PATCHID=id DISTRIBUTION=dist
They appear in config.h
Add them to your version-printing function.
Signed-off-by: Uri Lublin <uril@redhat.com>
Run ./configure --with-spice-common to use spice-common sources from
spice-common package, instead of source in spice/common/ directory.
This is usefull when building the spice client or spice server out
of a "distribution" tarball, when ../common directory does not exist.
Install source files in $(prefix)/src/spice-common/
Install linux/ffmpeg_inc.h in $(prefix)/src/spice-common/linux/
Install spice-common.pc in $(libdir)/pkgconfig/
Signed-off-by: Uri Lublin <uril@redhat.com>
The package-config file is to be used when ../common
is not available, e.g. when building each subdir
separately.
Signed-off-by: Uri Lublin <uril@redhat.com>
That's about all the work configure.ac does.
Moved config.pc.in to server, and updated Makefile.am and
server/Makefile.am accordingly
Signed-off-by: Uri Lublin <uril@redhat.com>
If ffmpeg-spice exists use ffmpeg-spice.
If ffmpeg-spice does not exist and ffmpeg exists, use ffmpeg
If none exist, fail.
Signed-off-by: Uri Lublin <uril@redhat.com>
The follwing files exist in client directory but not in RED_COMMON_SRCS,
thus they are not part of distribution tarball (make dist).
Adding them fixes building the spice client out of a distribution tarball.
Those files are:
icon.h
process_loop.h
red_gdi_canvas.cpp
red_gdi_canvas.h
red_pixmap_gdi.h
gdi_canvas.cpp
Similarly, the following files were added to spicec_SOURCES in
client/x11/Makefile.am:
event_sources_p.h
We compile with -I$(COMMON_DIR) (which currently is ../common), so there is
no need for that.
Later we would like to be able to have a different COMMON_DIR.
Signed-off-by: Uri Lublin <uril@redhat.com>
Replace all "$(top_srcdir)/common" with "$(SPICE_COMMON_DIR)"
and all "$(top_srcdir)/client" with ".." (relative to x11)
This would (after following patches) enables building the client from
either spice/ (top directory) or spice/client.
Signed-off-by: Uri Lublin <uril@redhat.com>
Replace all $(top_srcdir)/common.
This would (after following patches) enables building the server from
either spice/ (top directory) or spice/server.
Signed-off-by: Uri Lublin <uril@redhat.com>
... and m4_include it in configure.ac
Later all configure.ac in subdirs will m4_include it too.
This patch changes nothing really, just moves lines from one file to another.
Signed-off-by: Uri Lublin <uril@redhat.com>
subdirs are defined in configure.ac
Note we also mkdir m4 (just in case)
And touch some needed files (README NEWS ...) to prevent warnings/errors.
It may be better to add those files and commit them, or copy from parent dir.
Signed-off-by: Uri Lublin <uril@redhat.com>
3 available mechanisms: by public key, by host name, and by certificate subject name.
In the former method, chain of trust verification is not performed.
The CA certificate files are looked for under <spice-config-dir>/spice_truststore.pem
windows <spice-config-dir>=%APPDATA%\spicec\
linux <spice-config-dir>=$HOME/.spicec
-move _focused & _pointer_in_window from RedWindow to RedWindow_p's
-move shadow focus & cursor handling to sync()
-add reset_cursor_pos() to Platform
-Monitor set_mode()/restore() use virtual do_set_mode()/do_restore()
Beacuse that XShem internal checks wont fail when using the spice client
from remote, we are adding check on the socket family to see if it is
unix domain socket and fail in case it is not.
Signed-off-by: Izik Eidus <ieidus@redhat.com>
Increase client timeout in order to prevent unnecessary
disconnecting of client while the connection is over WAN.
Tested by changing WinXP resolution (with desktop background) while
connecting over WAN (1.5Mbit 150Kbit)
