Hi Norman, Robert,
In the long run, it would seem a good idea to make it possible to
disable these
new peers, just as users can disable gcjappletviewer, the gtk and qt
peers, etc.
Cheers,
Andrew
On 19 Jun 2006, at 11:50, Robert Schuster wrote:
Hi Norman,
sorry that this stopped your development but with CVS sources stuff
like that
can happen from time to time.
On Ubuntu and Debian GNU/Linux-based distros you need to install
libgconf2-dev.
This will download and install C header files which are needed to
compile the
native side of the GConf-based backend for java.util.prefs.
Now you know for what it it used. java.util.prefs is a API that allows
applications to conveniently store preferences and other
configuration data. The
RI on Windows machines can use the so-called registry on that
system. On
GNU/Linux systems they have a simple file based implementation.
GNU Classpath can write the data to plain files (no dependencies)
or use the
GConf library for that task. The latter was made the default
because it is
technically nicer and integrates better in the GNU environment.
Btw: I have a patch that mentions the new library dependency in
INSTALL here.
:)
cya
Robert
Norman Hendrich wrote:
Hello Roman,
thanks for your quick reply.
Orbit is usually installed as part of Gnome. Of which gconf is the
configuration management. So if you have gconf you usually also have
Gnome and with it you'll have Orbit.
OK. So far, I only have those parts of gnome required to building
classpath. So much for my priorities :-)
classpath configure now requires gconf >= 2.11.2:
./configure --with-jikes --disable-plugin --prefix=/opt/classpath
[...]
checking for gconf-2.0 >= 2.11.2... Package gconf-2.0 was not
found in the
pkg-config search path.
Perhaps you should add the directory containing `gconf-2.0.pc'
to the PKG_CONFIG_PATH environment variable
No package 'gconf-2.0' found
while building gconf 2.11.92 fails with
./configure
No package 'ORBit-2.0' found
configure: error: Package requirements (gmodule-2.0 >= 2.7.0
gobject-2.0 >=
2.7.0 ORBit-2.0 >= 2.4.0) were not met.
and building a fresh gconf 2.14.0 fails with:
./configure
checking for DEPENDENT... Requested 'glib-2.0 > 2.9.0' but version
of GLib is
2.8.6
configure: error: Package requirements (glib-2.0 > 2.9.0
gmodule-2.0 >= 2.7.0
gobject-2.0 >= 2.7.0 ORBit-2.0 >= 2.4.0) were not met:
I don't use GNOME. Seems like --disable-gconf-peer is the way to go.
What are the gconf peers supposed to do anyway?
Thanks, Norman
--
Andrew :)
Department of Computer Science
University of Sheffield
