A C and Java API are provided (the Java API is a JNI wrapper to the C API).
You can use the gpt tools (version 1 or 2) or configure/make manually.

If you're using gpt2 the command is

  gpt-build [-force] globus_rls_client-1.1.tar.gz gcc32dbgpthr

or if you've already unpacked the sources:

  gpt-build [-force] -srcdir=. gcc32dbgpthr

If you're using gpt1 the command is:

  globus-build gcc32dbgpthr [-force] -srcdir=.

If you wish to configure the Java API (included in the java subdirectory)
you must specify where Java is installed on your system.  You may do this
by either setting the environment variable JAVA_HOME to the toplevel Java
directory, or run configure with the option "--with-jdk-path=<path-to-jdk>".
If you're using GPT (gpt-build or globus-build) you can pass options
to configure by setting CONFIGOPTS_GPTMACRO, eg:

  CONFIGOPTS_GPTMACRO="--with-jdk-path=<path to jdk>"

If you want to configure and build the API(s) manually you can run configure,
make and "make install" directly:

  ./configure --with-flavor=gcc32dbgpthr --enable-debug --with-threads=pthreads

or

  ./configure --with-jdk-path=<path to your jdk> --with-flavor=gcc32dbgpthr \
	--enable-debug --with-threads=pthreads

  make
  make install

Client programs that use this API should be linked with

  -lglobus_rls_client_FLAVOR

where FLAVOR is the flavor specified in the configure command, eg
"gcc32dbgpthr".

The Java API is a JNI wrapper for the C API.  It needs to load the library
libglobus_rls_client_jni_FLAVOR at runtime.  By default it will try
flavors gcc32dbgpthr, gcc32dbg, gcc32pthr and gcc32.  If your flavor is
not one of these you can specify the property "globus.flavor" when you
run your application, eg

	java -Dglobus.flavor=myflavor ...

The shell script testrls (made from testrls.in) uses this to set
the Globus flavor appropriately.
