On 07/01/2011 01:53 PM, John Wolfe wrote: > 1. Is it a bug that configure did not check for the presence > of glibmm, gtkmm and sigc++ ?
Probably. Most probably the dependency was added some time after configure.ac was written in its current form, and never reflected in the configure script. > Should I have not attempted to build the unity plugin? > > I saw no way that a Solaris build would have bypassed the > Unity plugin build - with or without the --without-gtkmm I don't think I've compiled Unity on Solaris (last I tried I ran into weird errors from Solaris gcc and the sigc headers). But my question would be: why do you need unity on SCO in the first place? I doubt you'll be running desktop VMs with SCO OpenServer VMs inside Fusion or Workstation, so the unity plugin will just be useless overhead... Unity is also completely untested outside of Linux, so even if it compiles it may not even work. > 2. Is there a comprehensive list of the open-source packages > that are required for the various features of open-vm-tools? Nothing like that; closest thing would be deriving the information from the configure script. From a high level: UI features will need gtk/gtkmm, non-UI features will just need glib. -- - Marcelo ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ open-vm-tools-devel mailing list open-vm-tools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/open-vm-tools-devel
