Free glib software for linux

glib-java is a Java-Gnome library.

Installation:

The simplest way to compile this package is:

1. `cd to the directory containing the packages source code and type `./configure to configure the package for your system. If youre using `csh on an old version of System V, you might need to type `sh ./configure instead to prevent `csh from trying to execute `configure itself.

Running `configure takes awhile. While running, it prints some messages telling which features it is checking for.

2. Type `make to compile the package.

3. Optionally, type `make check to run any self-tests that come with the package.

4. Type `make install to install the programs and any data files and documentation.

5. You can remove the program binaries and object files from the source code directory by typing `make clean. To also remove the files that `configure created (so you can compile the package for a different kind of computer), type `make distclean. There is also a `make maintainer-clean target, but that is intended mainly for the packages developers. If you use it, you may have to get all sorts of other programs in order to regenerate files that came with the distribution.

Glib::CodeGen is a code generation utilities for Glib-based bindings.

SYNOPSIS

# usually in Makefile.PL
use Glib::CodeGen;

# most common, use all defaults
Glib::CodeGen->parse_maps (myprefix);
Glib::CodeGen->write_boot;

# more exotic, change everything
Glib::CodeGen->parse_maps (foo,
input => foo.maps,
header => foo-autogen.h,
typemap => foo.typemap,
register => register-foo.xsh);
Glib::CodeGen->write_boot (filename => bootfoo.xsh,
glob => Foo*.xs,
ignore => ^(Foo|Foo::Bar)$);

# add a custom type handler (rarely necessary)
Glib::CodeGen->add_type_handler (FooType => ≥n_foo_stuff);
# (see the section EXTENDING TYPE SUPPORT for more info.)

This module packages some of the boilerplate code needed for performing code generation typically used by perl bindings for gobject-based libraries, using the Glib module as a base.

The default output filenames are in the subdirectory build, which usually will be present if you are using ExtUtils::Depends (as most Glib-based extensions probably should).

Glib::MakeHelper is a Perl module for Makefile.PL utilities for Glib-based extensions.

SYNOPSIS

eval "use Glib::MakeHelper; 1"
or complain_that_glib_is_too_old_and_die();

%xspod_files = Glib::MakeHelper->do_pod_files (@xs_files);

package MY;
sub postamble {
return Glib::MakeHelper->postamble_clean ()
. Glib::MakeHelper->postamble_docs (@main::xs_files)
. Glib::MakeHelper->postamble_rpms (
MYLIB => $build_reqs{MyLib},
);
}

The Makefile.PL for your typical Glib-based module is huge and hairy, thanks to all the crazy hoops you have to jump through to get things right. This module wraps up some of the more intense and error-prone bits to reduce the amount of copied code and potential for errors.

Glib Binding Properties library adds an implementation of binding properties to GLib / GTK+ library (it also includes Ada 95 for GtkAda GTK bindings, GtkAda was made by ACT corp.)

Binding properties is automatic synchronizing values of several properties to keep their values correspondingly to each other, so that when a property changes properties bound with it automatically change accordingly. Also bindings with value transformation functions are supported.

Binding properties much reduces development time of desktop applications and increases reliability as frees you from time consuming and error-prone writing callback handlers of property changes. (Probably wrong property change handlers is the most often cause of errors in GUI applications!)

Current version 0.9.1 is an alpha version. Please test it.

LibSoup is an HTTP client/server library for GNOME. LibSoup library uses GObjects and the glib main loop, to integrate well with GNOME applications.
Main features:
- Both asynchronous (GMainLoop and callback-based) and synchronous APIs
- Automatically caches connections
- SSL Support using GnuTLS
- Proxy support, including authentication and SSL tunneling
- Client support for Digest, NTLM, and Basic authentication
- Server support for Digest and Basic authentication
See the test programs in tests/ for simple examples of how to use the code, or evolution-data-server and evolution-exchange for more complicated examples.
Enhancements:
- The soup_headers_parse_status_line() was fixed, so WebDAV response parsing will work again.
- A bug was fixed in the header-parsing regression test that caused the test to fail sometimes, even though the actual header-parsing code was fine.

linda is a simple library implementation of the Linda parallel programming system.

To write a parallel program with linda, you have to know only 6 functions: spawn, out, in, inp, rd, and rdp. linda was originally written by Wong Weng Fai. It has been improved by making it a real library by using GNU autotools, by adding timeout functions, and by using glib/gthread.

Gabriel is a simple utility to enable D-Bus clients to connect to a D-Bus daemon running on a remote machine, through SSH.

Installing Gabriel

(0) To build Gabriel client, you need to have libssh (>= 0.2) [1] and glib (> 2.10) installed.

For Gabriel server scripts, you need socat and D-Bus (> 1.0.2) installed on your machine.

(1) Type:

./configure

(2) make
(3) make install

Usage Notes

Gabriel is composed of a client-side and a server side:

The server side is actually just a small dbus configuration file and a pair of scripts that start and shut-down a dbus-daemon with that configuration file.

Here is the usage for the Gabriel server scripts:

gabriel-server-start [PID_FILE]
gabriel-server-stop [PID_FILE]

Where PID_FILE is the path to the file where the PID of the dbus-daemon will be stored. If no PID_FILE is specified, /tmp/gabriel-server.pid is assumed.

The client side is the actual thing and is therefore a binary named, gabriel. Following is its usage:

gabriel [OPTION...] - Gabriel

Help Options:

-?, --help Show help options

Application Options:

-h, --host=HOSTNAME Hostname or IP of the remote host
-u, --username=USERNAME Username on the remote host
-p, --password=PASSWORD Password on the remote host
-b, --bind=LOCALHOST The address to listen for DBus client connections on
-t, --port=PORT The TCP port to listen for DBus client connections on

Upon successful launch, gabriel will inform you about the D-Bus Bus address you need to use for your D-Bus clients. If you launch gabriel without any arguments, it will try to connect to the localhost, bind TCP socket it listens on to the localhost at port 1337. The output from gabriel on successful launch in this case would be:

Listening to D-Bus clients on: "tcp:host=localhost,port=1337"

Now to make your D-Bus clients connect to it, you either pass this as an argument to dbus_connection_open() in the clients code or simply set the environment variable DBUS_SESSION_BUS_ADDRESS like this:

DBUS_SESSION_BUS_ADDRESS="tcp:host=localhost,port=1337" your_dbus_client

Tada! Your dbus client is manipulating objects on a remote machine over a secure channel.

Known Issues

* Only one client can connect at one time. I already have a fix for this but unfortunately it doesnt work since libssh is not thread-safe. However the developer has promised to make things better in this respect in the next release.

* The server (dbus-daemon actually) should be launched by the same user account as used by gabriel to authenticate to the server. This is because of some strange authentication mechanism of D-Bus that I dont really understand.