summaryrefslogtreecommitdiffstats
path: root/configure.ac
Commit message (Collapse)AuthorAgeFilesLines
* Bring back libvirt-glib dependencyFabiano Fidêncio2016-02-251-1/+4
| | | | | | | | | | | | | | | libvirt-glib dependency was dropped in commit 296f91c in favor to maintain the full glib event loop integration into virt-viewer tree. This decision was taken because libvirt-glib was not mature enough at that time, which is not the case nowadays. The libvirt-glib version chosen as dependency (0.1.8) is the first release that includes the fixes for the glib event loop integration that were backported to virt-viewer last year. Signed-off-by: Fabiano Fidêncio <fidencio@redhat.com> Acked-by: Eduardo Lima (Etrunko) <etrunko@redhat.com> Acked-by: Victor Toso <victortoso@redhat.com>
* Use GDK_VERSION_MAX_ALLOWEDFabiano Fidêncio2016-02-241-1/+8
| | | | | | | In order to avoid using a too new Gtk API. Signed-off-by: Fabiano Fidêncio <fidencio@redhat.com> Acked-by: Pavel Grunt <pgrunt@redhat.com>
* Use GLIB_VERSION_MAX_ALLOWEDFabiano Fidêncio2016-02-241-1/+9
| | | | | | | In order to avoid using a too new GLib API. Signed-off-by: Fabiano Fidêncio <fidencio@redhat.com> Acked-by: Pavel Grunt <pgrunt@redhat.com>
* Port to GtkApplication API'sEduardo Lima (Etrunko)2016-02-181-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Most of this patch consists in code being shuffled around to fit the expected flow while using the new APIs. I tried my best to make this patch the less intrusive as possible. Main changes are: - Updated build requirements * glib version 2.38 * gtk+ version 3.10 * gio - VirtViewerApp is now a subclass of GtkApplication. Some mainloop calls were replaced: * gtk_main() -> g_application_run() * gtk_quit() -> g_application_quit() - Unified command line option handling. The logic has moved from the main functions and split in common options, and specific ones for each application. With this, the main functions were highly simplified, and now basically responsible for instantiating the App object and running the main loop. - All Window objects must be associated with the Application. With this, there is no need to emit our own 'window-added'/'window- removed' signals, as those will be emited by GtkApplication whenever gtk_application_add_window() and gtk_application_remove_window() are called. Also, 'window-removed' was not being used anywhere. Signed-off-by: Eduardo Lima (Etrunko) <etrunko@redhat.com>
* Drop support to gtk2Fabiano Fidêncio2016-02-151-48/+9
| | | | | | | | The 3.0 release was the last one that still supports GTK2. For the Windows builds the support to GTK2 was dropped in the previous release. Let's do the same for the entire project now. Signed-off-by: Eduardo Lima (Etrunko) <etrunko@redhat.com>
* Bump spice-gtk dep to 0.30.0 to avoid dep on git snapshot releaseDaniel P. Berrange2015-12-031-1/+1
|
* Add new functions to enable/disable a displayJonathon Jongsma2015-09-101-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously, there was a single function for controlling the enabled state of a display: virt_viewer_display_set_enabled(). Unfortunately, this function is used for two slightly different things: A. It informs the local display widget that the display has become disabled or enabled on the server. In other words, it tries to synchronize the 'enabled' state of the local widget with the actual state of the remote display. OR B. It tries to actively enable a currently-disabled display (or vice versa) due to some action by the user in the client application. This causes the client to send a new configuration down to the server. In other words, it tries to change the state of the remote display. There is some conflict between these two scenarios. If the change is due to a notification from the server, there is no need to send a new configuration back down to the server, so this results in unnecessary monitor configuration messages and can in fact cause issues that are a little bit hard to track down. Because of this, I decided that it was really necessary to have two separate functions for these two different scenarios. so the existing _set_enabled() function will be used for scenario A mentioned above. I added two new functions (_enable() and _disable()) that are used to send new configurations down to the server.
* configure: Use default error message when package is missingPavel Grunt2015-07-291-51/+36
| | | | | | | | | | | To make clear why configure failed - e.g.: Package requirements (spice-client-gtk-2.0 >= 0.28) were not met Requested 'spice-client-gtk-2.0 >= 0.28' but version of spice-client-gtk-2.0 is 0.25 instead of spice-gtk requested but not found Related: https://bugzilla.redhat.com/show_bug.cgi?id=1214577
* configure: Enable spice-gtk when have all necessary spice packagesPavel Grunt2015-07-291-1/+2
| | | | | | | | | When neither --with-spice-gtk=yes nor --with-spice-gtk=no is used, spice-gtk is supposed to be automatically enabled/disabled depending on its availability. However, this is not perfectly working as once spice-gtk has been detected as available, configure will fail if spice-protocol or spice-controller are too old. In this case, spice-gtk support should just be disabled rather than configure failing
* configure: Require spice-protocol 0.12.7Pavel Grunt2015-06-161-1/+1
| | | | We are already using SPICE_CHANNEL_WEBDAV from spice/enums.h
* build-sys: Add --with-osidChristophe Fergeau2015-06-091-0/+6
| | | | | | | | | This new configure flag allows to specify a string ID (eg fedora22, ubuntu10.04, ..) identifying the OS this remote-viewer build will be for. This will be used in combination with the new 'versions' field in .vv files in order to make it possible for the creator of the .vv file to specify which version it expects for the various OSes which may connect.
* build-sys: Always prepend '-' to BUILDIDChristophe Fergeau2015-06-091-2/+2
| | | | | | | | | | | | | This was removed by commit 28a6bd6 as WINDOWS_PRODUCTVERSION needs a buildid without a dash. Apart from this variable, all other uses of buildid/BUILDID in virt-viewer source tree need a dash between the version number and the buildid to avoid getting output like "3.01" instead of "3.0-1" Rather than patching every location where BUILDID is used, this commit appends the "-" before substituting/defining BUILDID in configure.ac. This does not modifies the buildid configure.ac variable, this way WINDOWS_PRODUCTVERSION won't get an unwanted '-'.
* build-sys: Don't substitute buildid when it was not setChristophe Fergeau2015-06-091-2/+7
| | | | | Since it defaults to being 0, we'll get a spurious 0 on remote-viewer --version if we AC_DEFINE/AC_SUBST it when the user did not specify it.
* ovirt: Allow to cancel authentication without showing error dialogPavel Grunt2015-04-141-1/+12
| | | | Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1201604
* Bump spice-gtk to 0.28Marc-André Lureau2015-03-041-1/+1
| | | | The following patches will only work with spice-gtk >= 0.28.
* Bump release to 3.0 for next dev cycleDaniel P. Berrange2015-01-121-1/+1
|
* msi: add gtk3 supportFabiano Fidêncio2014-12-151-0/+1
| | | | | | | | | Add support to build the virt-viewer's msi using GTK3. For the GTK3 build, in order to provide all used icons for Windows systems we have to include manually all the icons we want to or add adwaita-icon-theme as dependency. I've decided to go with the first approach, what can be improved when we have "foreach" support in msitools (https://bugzilla.gnome.org/show_bug.cgi?id=741296).
* ovirt: Allow to remove CD imagesChristophe Fergeau2014-10-091-1/+1
| | | | | | | | | | | | | It turns out this is supposed to be done through update requests with a CD image with an empty name, which is what the current code tries to do. The only reason it's not working is because of server-side bugs with oVirt < 3.5 The requirement on libgovirt is raised to 0.3.2 as a small change is needed as well in libgovirt to allow empty filenames: https://git.gnome.org/browse/libgovirt/commit/?id=bdb788fcc Without this change, nothing too bad will happen, but the CD won't be removed and warnings will be logged in the console.
* Prefer virDomainOpenGraphicsFD for --attachJán Tomko2014-10-011-0/+8
| | | | | | | | | | | | | | | The virDomainOpenGraphics API cannot label the socket we pass to it. Prefer virDomainOpenGraphicsFD (if building with libvirt 1.2.8 or later) which creates the socket for us and works with SELinux too. Fall back to the old API if the new one is unsupported (i.e. the libvirtd on the host is older than the libvirt version virt-viewer was compiled against). Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1141228 Signed-off-by: Ján Tomko <jtomko@redhat.com>
* ovirt: Add OvirtForeignMenu classChristophe Fergeau2014-08-181-1/+2
| | | | | | | This class is used to implement the so-called oVirt 'foreign menu' which is a menu populated with ISO images available on the oVirt instance that the user can dynamically insert into the virtual machine he is currently viewing.
* Bump version to 2.0 for next dev cycleDaniel P. Berrange2014-07-211-1/+1
|
* build-sys: Use automake 'subdir-objects' optionChristophe Fergeau2014-06-261-1/+1
| | | | | | | | | | | | | | | | | | | | | | | This silences an automake 1.14 warning: src/Makefile.am:35: warning: source file 'view/autoDrawer.c' is in a subdirectory, src/Makefile.am:35: but option 'subdir-objects' is disabled automake: warning: possible forward-incompatibility. automake: At least a source file is in a subdirectory, but the 'subdir-objects' automake: automake option hasn't been enabled. For now, the corresponding output automake: object file(s) will be placed in the top-level directory. However, automake: this behaviour will change in future Automake versions: they will automake: unconditionally cause object files to be placed in the same subdirectory automake: of the corresponding sources. automake: You are advised to start using 'subdir-objects' option throughout your automake: project, to avoid future incompatibilities.
* Bump version 1.0 to simplify Windows MSI versioningDaniel P. Berrange2014-06-231-14/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The Windows MSI product version is restricted to a 3 component version number, whose fields are a max value of 255.255.65536 Since the main virt-viewer version takes up 3 components already, we have the munge the micro version together with the first component of the release version. eg we have $VERSION[0].$VERSION[1].($VERSION[2] << 8 + $RELEASE[0]) This causes problems for RHEL which needs to have 2-component release versions to deal with z-stream builds. eg a RHEL version might be virt-viewer-0.5.6-2.el6_4.3 and we've no easy way of adding the final '.3' to the Windows product version. If we reduce the primary virt-viewer version to just 2 components, then we can leave the 3rd component for exclusive use by the RPM release number. eg so we'd make product version up using $VERSION[0].$VERSION[1].($RELEASE[0] << 8 + $RELEASE[1]) In course of normal development, we'd increase the $VERSION[0] for each release. ie next release is 1.0, then 2.0, then 3.0. This means we retain the ability to put out "stable" branch releases for any historical version by doing 1.1, 1.2 instead of having to re-add a 3rd component. Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
* msi: move up micro version in x.x.build productversionMarc-André Lureau2014-06-101-1/+3
| | | | | | | This allows 12 bits to form a buildid, ex in RHEVM builds: --with-buildid=$(release << 4 + zrelease) https://bugzilla.redhat.com/show_bug.cgi?id=1105650
* build-sys: Always prepend '-' to build idChristophe Fergeau2014-04-041-4/+5
| | | | | | | | | | | | | | | | | When using the --with-buildid configure paramater, the build id which is substituted in the MSI wxs file is automatically prepended by a '-', but the build id which is used in the C files does not get this '-' automatically. Currently, the linux and mingw spec files prepend a '-' on their own to the --with-buildid argument, but this causes the MSI installer to show 2 '-' during installation: "Please wait while Windows configures VirtViewer 0.6.0--1" This commit always prepends a '-' to the buildid strings, and removes the '-' from the spec files. This is to ensure the separator between version number and buildid is not forgotten, which could give a confusing version number.
* Update for 0.6.0 releasev0.6.0Daniel P. Berrange2014-01-241-1/+1
| | | | Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
* spec: Get BuildRequires min versions from configure.acChristophe Fergeau2013-12-181-1/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We currently duplicate the minimum requirements for the various virt-viewer dependencies in configure.ac, virt-viewer.spec.in and mingw-virt-viewer.spec.in This commit uses the versions set in configure.ac in the 2 .spec.in files so that it's easier to keep them in sync Before/after diff of the .spec files are: --- virt-viewer.spec.or 2013-12-18 14:14:14.304285905 +0100 +++ virt-viewer.spec 2013-12-18 14:19:20.217072678 +0100 @@ -47,14 +47,14 @@ BuildRequires: libtool %endif -BuildRequires: glib2-devel >= 2.22 +BuildRequires: glib2-devel >= 2.22.0 %if %{with_gtk3} -BuildRequires: gtk3-devel >= 3.0.0 +BuildRequires: gtk3-devel >= 3.0 %else -BuildRequires: gtk2-devel >= 2.12.0 +BuildRequires: gtk2-devel >= 2.18.0 %endif -BuildRequires: libvirt-devel >= 0.9.7 -BuildRequires: libxml2-devel +BuildRequires: libvirt-devel >= 0.10.0 +BuildRequires: libxml2-devel >= 2.6.0 %if %{with_gtk3} BuildRequires: gtk-vnc2-devel >= 0.4.0 %else --- mingw-virt-viewer.spec.or 2013-12-18 14:14:23.656401693 +0100 +++ mingw-virt-viewer.spec 2013-12-18 14:20:57.007270507 +0100 @@ -12,22 +12,22 @@ BuildRequires: mingw32-filesystem >= 23 BuildRequires: mingw64-filesystem >= 23 -BuildRequires: mingw32-glib2 >= 2.22 -BuildRequires: mingw64-glib2 >= 2.22 +BuildRequires: mingw32-glib2 >= 2.22.0 +BuildRequires: mingw64-glib2 >= 2.22.0 BuildRequires: mingw32-gstreamer-plugins-bad-free BuildRequires: mingw64-gstreamer-plugins-bad-free BuildRequires: mingw32-gstreamer-plugins-good BuildRequires: mingw64-gstreamer-plugins-good -BuildRequires: mingw32-gtk2 -BuildRequires: mingw64-gtk2 +BuildRequires: mingw32-gtk2 >= 2.18.0 +BuildRequires: mingw64-gtk2 >= 2.18.0 BuildRequires: mingw32-libusbx BuildRequires: mingw64-libusbx -BuildRequires: mingw32-libvirt >= 0.9.7 -BuildRequires: mingw64-libvirt >= 0.9.7 -BuildRequires: mingw32-libxml2 -BuildRequires: mingw64-libxml2 -BuildRequires: mingw32-gtk-vnc >= 0.4.3 -BuildRequires: mingw64-gtk-vnc >= 0.4.3 +BuildRequires: mingw32-libvirt >= 0.10.0 +BuildRequires: mingw64-libvirt >= 0.10.0 +BuildRequires: mingw32-libxml2 >= 2.6.0 +BuildRequires: mingw64-libxml2 >= 2.6.0 +BuildRequires: mingw32-gtk-vnc >= 0.3.8 +BuildRequires: mingw64-gtk-vnc >= 0.3.8 BuildRequires: mingw32-readline BuildRequires: mingw64-readline BuildRequires: mingw32-spice-glib
* Update shared mime database on install/uninstallChristophe Fergeau2013-12-181-0/+10
| | | | | | | | | | | | | | remomte-viewer installs a file to $datadir/share/mime to register a mime-type for its .vv files. However, after installing this file, update-mime-database must be run in order to update the shared mime database. This commit (inspired by what Nautilus/planner are doing) adds what is needed for that. If the mime type is not correctly registered, gvfs-info console.vv will not return the correct mime type, and xdg-open console.vv will fail to start remote-viewer, and will fall back to running gedit as the .vv file is a text file. https://bugzilla.redhat.com/show_bug.cgi?id=1044209
* build-sys: require spice-gtk >= 0.22Marc-André Lureau2013-12-161-1/+1
| | | | Require 0.22 fro spice_uuid_to_string()
* build-sys: Use gtk+ 3.0 by defaultChristophe Fergeau2013-11-131-2/+2
| | | | | | virt-viewer currenty builds with gtk+ 2.0 by default. Nowadays, gtk+ 2.0 is legacy, and this default is inconsistent with spice-gtk which defaults to gtk+ 3.0. This commit switches the default to gtk+ 3.0
* ovirt: Remove use of deprecated APIsChristophe Fergeau2013-10-301-1/+1
| | | | | ovirt_proxy_fetch_vms/ovirt_proxy_lookup_vm have been deprecated in govirt 0.3.0
* Update min spice-gtk dep to 0.20v0.5.7Daniel P. Berrange2013-07-311-1/+1
| | | | | | | The spice_smartcard_manager_get_readers method was only added in spice-gtk 0.20. Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
* msi: use ProductVersion compatible with Windows InstallerMarc-André Lureau2013-07-301-0/+14
| | | | | | | | | Windows Installer expects version of form major.minor.build in order to perform updates. Following Daniel Berrange suggestion, compute a ProductVersion compatible with this scheme by shifting virt-viewer "micro" release number and adding the extra "buildid".
* ovirt: Set host subject if neededChristophe Fergeau2013-06-111-1/+1
| | | | | | | | | | For some VMs, setting host subject on SpiceSession is needed to be able to connect to it using SPICE/SSL. Until recently, this was not exposed in oVirt REST API/libgovirt. Since oVirt 3.2/libgovirt 0.1.0, the host subject is available, this patch makes use of it. This should fix connection to oVirt VMs that were migrated to a different host than the one they were started on.
* Post release version bumpDaniel P. Berrange2013-05-011-1/+1
|
* msi: build correct 64-bit msiMarc-André Lureau2013-04-151-0/+9
|
* build-sys: Simplify setting of optional CFLAGS/LDFLAGSChristophe Fergeau2013-04-121-1/+0
| | | | | | | They don't need to be wrapped inside if HAVE_XXX blocks in Makefile.am as when XXX is not available, XXX_CFLAGS and XXX_LIBS will expand to the empty string, and thus we can carry them unconditionally in our app_CFLAGS/app_LDFLAGS variables.
* Add oVirt supportChristophe Fergeau2013-04-121-0/+18
| | | | | | This commit adds support for ovirt:// URIs. It does so by using libgovirt to get the spice/vnc connection information through oVirt xmlrpc API.
* Delete browser plugin entirelyDaniel P. Berrange2013-03-131-24/+0
| | | | | | | | | | | The browser plugin code has been effectively unmaintained since the day it was merged. There has always been a caveat that the code has not been properly audited to ensure it is secure, and being unmaintained doesn't give a warm secure feeling. These days there are better solutions for the browser which are pure HTML5 code, noVNC and SPICE-HTML5. Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
* Post release version bumpDaniel P. Berrange2013-02-131-1/+1
|
* Update for 0.5.5 releasev0.5.5Daniel P. Berrange2013-02-131-1/+1
|
* win: add virt-viewer.msi build ruleMarc-André Lureau2013-02-131-0/+1
| | | | | | | | In order to build the MSI, you will need msitools: http://ftp.gnome.org/pub/GNOME/sources/msitools/ The MANUFACTURER environment variable is mandatory and should be set to the manufacturer/author of the MSI build.
* build-sys: add --with-buildid to details build versionMarc-André Lureau2013-02-121-0/+4
| | | | | | Add a configure argument to append build version details, similar to what Daniel Berrange proposed in the "use finer package version in mingw-virt-viewer" thread on the ML.
* configure: Update with autoupdateMichal Privoznik2013-02-041-3/+4
|
* Make compilation work with automake 1.13Martin Kletzander2013-02-041-1/+1
| | | | | | Just one thing needs to be changed for virt-viewer to build with automake 1.13, AM_CONFIG_HEADER is deprecated and should be AC_CONFIG_HEADERS.
* remote-viewer: controller sets spice session proxyMarc-André Lureau2013-01-311-1/+1
| | | | | Trivial change since spice-gtk now has proxy session property and controller message, just forward it.
* spice: add proxy configuration to connection fileMarc-André Lureau2013-01-291-1/+1
|
* Add virt-viewer-debug.exe NSIS installerMarc-André Lureau2012-11-231-0/+1
| | | | | | This installer will provide with the tools and configuration needed to debug virt-viewer & remote-viewer. It will install itself by default in virt-viewer directory.
* build-sys: add min libvirt version requirement checkMarc-André Lureau2012-11-161-1/+1
|
* Fix spice-gtk check in configure.acChristophe Fergeau2012-11-151-1/+1
| | | | | | | | The check that at least one of spice-gtk and gtk-vnc is present uses a wrong variable name to check for spice-gtk presence, which causes the check to think it's never present. This would make gtk-vnc presence mandatory. This commit fixes the name of the spice-gtk variable ($have_gtk_spice -> $have_spice_gtk).
generated by cgit (git 2.34.1) at 2024-05-25 15:07:31 +0000