e2e5c3a1cc
2000-01-12 Martin Baulig <martin@home-of-linux.org> * include/glibtop/backend.h (glibtop_backend_entry): New type. (glibtop_backend_module): New private type. * lib/backend.c (glibtop_register_backend): This now takes a `glibtop_backend_entry' argument, not a `glibtop_backend_info' one. (glibtop_backend_by_id): Return a `glibtop_backend_entry' type, not a `glibtop_backend_info' one. (glibtop_backend_by_name): Likewise. * lib/init-backends.c: If we have libxml, read all `.backend' files in $(LIBGTOP_BACKEND_DIR), XML parse them and register them via `glibtop_backend_register'. This builds a list of all currently supported backends without actually loading them into memory. * lib/open-backend.c (glibtop_open_backend_l): GModule load the backend if it's not already in memory.
This is the *development* branch of LibGTop. It is indended for people who want to help with the development of LibGTop and not for end-users. Please use the LIBGTOP_STABLE_1_0 branch (which is LibGTop 1.0.x) unless you're really a developer. If you're using LibGTop from CVS simply do a cvs update -r LIBGTOP_STABLE_1_0 to get the latest version from the stable branch. However, I'll periodically make snapshot releases from the development branch for Solaris users of LibGTop. They can be found at ftp://ftp.home-of-linux.org/pub/libgtop/1.1/ in near future. Using released tarballs from the development branch is a lot better than compiling directly from CVS since things in CVS may not always work as expected. Note that releases from the developer branch are neither binary nor fully source compatible; you'll normally have to recompile everything that use them. October 1999 Martin Baulig