[cairo-commit] cairo-java autogen.sh, NONE, 1.1 .project, NONE, 1.1 AUTHORS, NONE, 1.1 COPYING, NONE, 1.1 .classpath, NONE, 1.1 Makefile.am, NONE, 1.1 configure.ac, NONE, 1.1 ChangeLog, NONE, 1.1 INSTALL, NONE, 1.1 README, NONE, 1.1 .cvsignore, NONE, 1.1 cairo-java.pc.in, NONE, 1.1 NEWS, NONE, 1.1

[Jeffrey Morgan]

Committed by: kuzman

Update of /cvs/cairo/cairo-java
In directory gabe:/tmp/cvs-serv32536

Added Files:
	autogen.sh .project AUTHORS COPYING .classpath Makefile.am 
	configure.ac ChangeLog INSTALL README .cvsignore 
	cairo-java.pc.in NEWS 
Log Message:
Initial import

--- NEW FILE: autogen.sh ---
#!/bin/sh
# Run this to generate all the initial makefiles, etc.

srcdir=`dirname $0`
test -z "$srcdir" && srcdir=.

ORIGDIR=`pwd`
cd $srcdir
PROJECT=cairo-java
TEST_TYPE=-f
FILE=cairo-java.pc.in

DIE=0

have_libtool=false
if libtoolize --version < /dev/null > /dev/null 2>&1 ; then
	libtool_version=`libtoolize --version | sed 's/^[^0-9]*\([0-9.][0-9.]*\).*/\1/'`
	case $libtool_version in
	    1.4*|1.5*)
		have_libtool=true
		;;
	esac
fi
if $have_libtool ; then : ; else
	echo
	echo "You must have libtool 1.4 installed to compile $PROJECT."
	echo "Install the appropriate package for your distribution,"
	echo "or get the source tarball at http://ftp.gnu.org/gnu/libtool/"
	DIE=1
fi

(autoconf --version) < /dev/null > /dev/null 2>&1 || {
	echo
	echo "You must have autoconf installed to compile $PROJECT."
	echo "Install the appropriate package for your distribution,"
	echo "or get the source tarball at http://ftp.gnu.org/gnu/autoconf/"
	DIE=1
}

if automake-1.9 --version < /dev/null > /dev/null 2>&1 ; then
    AUTOMAKE=automake-1.9
    ACLOCAL=aclocal-1.9
else
	echo
	echo "You must have automake 1.9.x installed to compile $PROJECT."
	echo "Install the appropriate package for your distribution,"
	echo "or get the source tarball at http://ftp.gnu.org/gnu/automake/"
	DIE=1
fi

if test "$DIE" -eq 1; then
	exit 1
fi

test $TEST_TYPE $FILE || {
	echo "You must run this script in the top-level $PROJECT directory"
	exit 1
}

if test -z "$AUTOGEN_SUBDIR_MODE"; then
        if test -z "$*"; then
                echo "I am going to run ./configure with no arguments - if you wish "
                echo "to pass any to it, please specify them on the $0 command line."
        fi
fi

rm -rf autom4te.cache

libtoolize --force || exit $?

GTKJAVA_MACROS=`pkg-config --variable macro_dir gtk2-java`
aclocal -I $GTKJAVA_MACROS


$AUTOMAKE --add-missing || exit $?
autoconf || exit $?
cd $ORIGDIR || exit $?

if test -z "$AUTOGEN_SUBDIR_MODE"; then
        $srcdir/configure --enable-maintainer-mode $AUTOGEN_CONFIGURE_ARGS "$@" || exit $?

        echo 
        echo "Now type 'make' to compile $PROJECT."
fi



--- NEW FILE: .project ---
<?xml version="1.0" encoding="UTF-8"?>
<projectDescription>
	<name>cairo-java</name>
	<comment></comment>
	<projects>
	</projects>
	<buildSpec>
		<buildCommand>
			<name>org.eclipse.jdt.core.javabuilder</name>
			<arguments>
			</arguments>
		</buildCommand>
	</buildSpec>
	<natures>
		<nature>org.eclipse.jdt.core.javanature</nature>
	</natures>
</projectDescription>

--- NEW FILE: AUTHORS ---
Jeffrey Morgan <kuzman at gmail.com>
Massi Fr <massifr at fastwebnet.it>
Soorya Kuloor <sooryak at otii.com>



--- NEW FILE: COPYING ---
		    GNU GENERAL PUBLIC LICENSE
		       Version 2, June 1991

 Copyright (C) 1989, 1991 Free Software Foundation, Inc.
     59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
 Everyone is permitted to copy and distribute verbatim copies
 of this license document, but changing it is not allowed.

			    Preamble

  The licenses for most software are designed to take away your
freedom to share and change it.  By contrast, the GNU General Public
License is intended to guarantee your freedom to share and change free
software--to make sure the software is free for all its users.  This
General Public License applies to most of the Free Software
Foundation's software and to any other program whose authors commit to
using it.  (Some other Free Software Foundation software is covered by
the GNU Library General Public License instead.)  You can apply it to
your programs, too.

  When we speak of free software, we are referring to freedom, not
price.  Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
this service if you wish), that you receive source code or can get it
if you want it, that you can change the software or use pieces of it
in new free programs; and that you know you can do these things.

  To protect your rights, we need to make restrictions that forbid
anyone to deny you these rights or to ask you to surrender the rights.
These restrictions translate to certain responsibilities for you if you
distribute copies of the software, or if you modify it.

  For example, if you distribute copies of such a program, whether
gratis or for a fee, you must give the recipients all the rights that
you have.  You must make sure that they, too, receive or can get the
source code.  And you must show them these terms so they know their
rights.

  We protect your rights with two steps: (1) copyright the software, and
(2) offer you this license which gives you legal permission to copy,
distribute and/or modify the software.

  Also, for each author's protection and ours, we want to make certain
that everyone understands that there is no warranty for this free
software.  If the software is modified by someone else and passed on, we
want its recipients to know that what they have is not the original, so
that any problems introduced by others will not reflect on the original
authors' reputations.

  Finally, any free program is threatened constantly by software
patents.  We wish to avoid the danger that redistributors of a free
program will individually obtain patent licenses, in effect making the
program proprietary.  To prevent this, we have made it clear that any
patent must be licensed for everyone's free use or not licensed at all.

  The precise terms and conditions for copying, distribution and
modification follow.

		    GNU GENERAL PUBLIC LICENSE
   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

  0. This License applies to any program or other work which contains
a notice placed by the copyright holder saying it may be distributed
under the terms of this General Public License.  The "Program", below,
refers to any such program or work, and a "work based on the Program"
means either the Program or any derivative work under copyright law:
that is to say, a work containing the Program or a portion of it,
either verbatim or with modifications and/or translated into another
language.  (Hereinafter, translation is included without limitation in
the term "modification".)  Each licensee is addressed as "you".

Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope.  The act of
running the Program is not restricted, and the output from the Program
is covered only if its contents constitute a work based on the
Program (independent of having been made by running the Program).
Whether that is true depends on what the Program does.

  1. You may copy and distribute verbatim copies of the Program's
source code as you receive it, in any medium, provided that you
conspicuously and appropriately publish on each copy an appropriate
copyright notice and disclaimer of warranty; keep intact all the
notices that refer to this License and to the absence of any warranty;
and give any other recipients of the Program a copy of this License
along with the Program.

You may charge a fee for the physical act of transferring a copy, and
you may at your option offer warranty protection in exchange for a fee.

  2. You may modify your copy or copies of the Program or any portion
of it, thus forming a work based on the Program, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:

    a) You must cause the modified files to carry prominent notices
    stating that you changed the files and the date of any change.

    b) You must cause any work that you distribute or publish, that in
    whole or in part contains or is derived from the Program or any
    part thereof, to be licensed as a whole at no charge to all third
    parties under the terms of this License.

    c) If the modified program normally reads commands interactively
    when run, you must cause it, when started running for such
    interactive use in the most ordinary way, to print or display an
    announcement including an appropriate copyright notice and a
    notice that there is no warranty (or else, saying that you provide
    a warranty) and that users may redistribute the program under
    these conditions, and telling the user how to view a copy of this
    License.  (Exception: if the Program itself is interactive but
    does not normally print such an announcement, your work based on
    the Program is not required to print an announcement.)

These requirements apply to the modified work as a whole.  If
identifiable sections of that work are not derived from the Program,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works.  But when you
distribute the same sections as part of a whole which is a work based
on the Program, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote it.

Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Program.

In addition, mere aggregation of another work not based on the Program
with the Program (or with a work based on the Program) on a volume of
a storage or distribution medium does not bring the other work under
the scope of this License.

  3. You may copy and distribute the Program (or a work based on it,
under Section 2) in object code or executable form under the terms of
Sections 1 and 2 above provided that you also do one of the following:

    a) Accompany it with the complete corresponding machine-readable
    source code, which must be distributed under the terms of Sections
    1 and 2 above on a medium customarily used for software interchange; or,

    b) Accompany it with a written offer, valid for at least three
    years, to give any third party, for a charge no more than your
    cost of physically performing source distribution, a complete
    machine-readable copy of the corresponding source code, to be
    distributed under the terms of Sections 1 and 2 above on a medium
    customarily used for software interchange; or,

    c) Accompany it with the information you received as to the offer
    to distribute corresponding source code.  (This alternative is
    allowed only for noncommercial distribution and only if you
    received the program in object code or executable form with such
    an offer, in accord with Subsection b above.)

The source code for a work means the preferred form of the work for
making modifications to it.  For an executable work, complete source
code means all the source code for all modules it contains, plus any
associated interface definition files, plus the scripts used to
control compilation and installation of the executable.  However, as a
special exception, the source code distributed need not include
anything that is normally distributed (in either source or binary
form) with the major components (compiler, kernel, and so on) of the
operating system on which the executable runs, unless that component
itself accompanies the executable.

If distribution of executable or object code is made by offering
access to copy from a designated place, then offering equivalent
access to copy the source code from the same place counts as
distribution of the source code, even though third parties are not
compelled to copy the source along with the object code.

  4. You may not copy, modify, sublicense, or distribute the Program
except as expressly provided under this License.  Any attempt
otherwise to copy, modify, sublicense or distribute the Program is
void, and will automatically terminate your rights under this License.
However, parties who have received copies, or rights, from you under
this License will not have their licenses terminated so long as such
parties remain in full compliance.

  5. You are not required to accept this License, since you have not
signed it.  However, nothing else grants you permission to modify or
distribute the Program or its derivative works.  These actions are
prohibited by law if you do not accept this License.  Therefore, by
modifying or distributing the Program (or any work based on the
Program), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying
the Program or works based on it.

  6. Each time you redistribute the Program (or any work based on the
Program), the recipient automatically receives a license from the
original licensor to copy, distribute or modify the Program subject to
these terms and conditions.  You may not impose any further
restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties to
this License.

  7. If, as a consequence of a court judgment or allegation of patent
infringement or for any other reason (not limited to patent issues),
conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License.  If you cannot
distribute so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you
may not distribute the Program at all.  For example, if a patent
license would not permit royalty-free redistribution of the Program by
all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Program.

If any portion of this section is held invalid or unenforceable under
any particular circumstance, the balance of the section is intended to
apply and the section as a whole is intended to apply in other
circumstances.

It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system, which is
implemented by public license practices.  Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.

This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.

  8. If the distribution and/or use of the Program is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Program under this License
may add an explicit geographical distribution limitation excluding
those countries, so that distribution is permitted only in or among
countries not thus excluded.  In such case, this License incorporates
the limitation as if written in the body of this License.

  9. The Free Software Foundation may publish revised and/or new versions
of the General Public License from time to time.  Such new versions will
be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.

Each version is given a distinguishing version number.  If the Program
specifies a version number of this License which applies to it and "any
later version", you have the option of following the terms and conditions
either of that version or of any later version published by the Free
Software Foundation.  If the Program does not specify a version number of
this License, you may choose any version ever published by the Free Software
Foundation.

  10. If you wish to incorporate parts of the Program into other free
programs whose distribution conditions are different, write to the author
to ask for permission.  For software which is copyrighted by the Free
Software Foundation, write to the Free Software Foundation; we sometimes
make exceptions for this.  Our decision will be guided by the two goals
of preserving the free status of all derivatives of our free software and
of promoting the sharing and reuse of software generally.

			    NO WARRANTY

  11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN
OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS
TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE
PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
REPAIR OR CORRECTION.

  12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.

		     END OF TERMS AND CONDITIONS

	    How to Apply These Terms to Your New Programs

  If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.

  To do so, attach the following notices to the program.  It is safest
to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.

    <one line to give the program's name and a brief idea of what it does.>
    Copyright (C) <year>  <name of author>

    This program is free software; you can redistribute it and/or modify
    it under the terms of the GNU General Public License as published by
    the Free Software Foundation; either version 2 of the License, or
    (at your option) any later version.

    This program is distributed in the hope that it will be useful,
    but WITHOUT ANY WARRANTY; without even the implied warranty of
    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
    GNU General Public License for more details.

    You should have received a copy of the GNU General Public License
    along with this program; if not, write to the Free Software
    Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA


Also add information on how to contact you by electronic and paper mail.

If the program is interactive, make it output a short notice like this
when it starts in an interactive mode:

    Gnomovision version 69, Copyright (C) year  name of author
    Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
    This is free software, and you are welcome to redistribute it
    under certain conditions; type `show c' for details.

The hypothetical commands `show w' and `show c' should show the appropriate
parts of the General Public License.  Of course, the commands you use may
be called something other than `show w' and `show c'; they could even be
mouse-clicks or menu items--whatever suits your program.

You should also get your employer (if you work as a programmer) or your
school, if any, to sign a "copyright disclaimer" for the program, if
necessary.  Here is a sample; alter the names:

  Yoyodyne, Inc., hereby disclaims all copyright interest in the program
  `Gnomovision' (which makes passes at compilers) written by James Hacker.

  <signature of Ty Coon>, 1 April 1989
  Ty Coon, President of Vice

This General Public License does not permit incorporating your program into
proprietary programs.  If your program is a subroutine library, you may
consider it more useful to permit linking proprietary applications with the
library.  If this is what you want to do, use the GNU Library General
Public License instead of this License.

--- NEW FILE: .classpath ---
<?xml version="1.0" encoding="UTF-8"?>
<classpath>
	<classpathentry kind="src" path="src/java"/>
	<classpathentry kind="src" path="src/jni"/>
	<classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
	<classpathentry kind="src" path="/java-gnome"/>
	<classpathentry kind="output" path="bin"/>
</classpath>

--- NEW FILE: Makefile.am ---
AUTOMAKE_OPTIONS = subdir-objects

if BUILD_GCJ
lib_LTLIBRARIES = libcairojava.la libcairojni.la
else
lib_LTLIBRARIES = libcairojni.la
endif

java_cairo_source_files = \
	src/java/org/freedesktop/cairo/Affine.java \
	src/java/org/freedesktop/cairo/BoundingBox.java \
	src/java/org/freedesktop/cairo/Cairo.java \
	src/java/org/freedesktop/cairo/CairoException.java \
	src/java/org/freedesktop/cairo/CairoObject.java \
	src/java/org/freedesktop/cairo/Distance.java \
	src/java/org/freedesktop/cairo/Extend.java \
	src/java/org/freedesktop/cairo/FillRule.java \
	src/java/org/freedesktop/cairo/Filter.java \
	src/java/org/freedesktop/cairo/Font.java \
	src/java/org/freedesktop/cairo/FontExtents.java \
	src/java/org/freedesktop/cairo/FontSlant.java \
	src/java/org/freedesktop/cairo/FontWeight.java \
	src/java/org/freedesktop/cairo/Format.java \
	src/java/org/freedesktop/cairo/FreetypeFont.java \
	src/java/org/freedesktop/cairo/Glyph.java \
	src/java/org/freedesktop/cairo/ImageSurface.java \
	src/java/org/freedesktop/cairo/LineCap.java \
	src/java/org/freedesktop/cairo/LineJoin.java \
	src/java/org/freedesktop/cairo/Matrix.java \
	src/java/org/freedesktop/cairo/Operator.java \
	src/java/org/freedesktop/cairo/Pattern.java \
	src/java/org/freedesktop/cairo/PdfSurface.java \
	src/java/org/freedesktop/cairo/PngSurface.java \
	src/java/org/freedesktop/cairo/Point.java \
	src/java/org/freedesktop/cairo/PsSurface.java \
	src/java/org/freedesktop/cairo/RGBColor.java \
	src/java/org/freedesktop/cairo/Status.java \
	src/java/org/freedesktop/cairo/Surface.java \
	src/java/org/freedesktop/cairo/TextExtents.java

jni_cairo_source_files = \
	src/jni/org_freedesktop_cairo_Cairo.c \
	src/jni/org_freedesktop_cairo_Font.c \
	src/jni/org_freedesktop_cairo_FontExtents.c \
	src/jni/org_freedesktop_cairo_FreetypeFont.c \
	src/jni/org_freedesktop_cairo_Glyph.c \
	src/jni/org_freedesktop_cairo_ImageSurface.c \
	src/jni/org_freedesktop_cairo_Matrix.c \
	src/jni/org_freedesktop_cairo_Pattern.c \
	src/jni/org_freedesktop_cairo_PdfSurface.c \
	src/jni/org_freedesktop_cairo_PngSurface.c \
	src/jni/org_freedesktop_cairo_PsSurface.c \
	src/jni/org_freedesktop_cairo_Surface.c \
	src/jni/org_freedesktop_cairo_TextExtents.c

examples =

example_files =

if BUILD_GCJ
libcairojava_la_SOURCES = $(java_cairo_source_files)
nodist_libcairojava_la_SOURCES = src/java/org/freedesktop/cairo/Config.java
libcairojava_la_GCJFLAGS = -fjni -I$(srcdir)/src/java -Isrc/java --classpath=$(GTKJAR):$(srcdir)/src/java
libcairojava_la_LDFLAGS = $(GTKJAVA_LIBS) -release $(apiversion)
endif

libcairojni_la_SOURCES = $(jni_cairo_source_files)
libcairojni_la_CFLAGS = $(CAIRO_CFLAGS) $(FONTCONFIG_CFLAGS) $(GTK_CFLAGS) $(GTKJAVA_CFLAGS) -I$(includedir)
libcairojni_la_LDFLAGS = $(CAIRO_LIBS) $(FONTCONFIG_LIBS) $(GTKJNI_LIBS) -release $(apiversion)

# automake should support generating versioned jars
cairo_jardir = $(jardir)
cairo_jar_DATA = cairo$(apiversion).jar

cairo_jar_class_files = $(java_cairo_source_files:.java=.class)

$(cairo_jar_class_files): %.class: %.java
	$(JAVAC) -classpath $(GTKJAR):$(srcdir)/src/java:src/java -d src/java $<

# all_cairo_jar_class_files includes inner-class generated .class files
# the sed command protects dollar signs in file names from shell expansion
all_cairo_jar_class_files = $(shell find src/java -name '*.class' | sed 's%\$$%\\$$%g')

cairo$(apiversion).jar: $(cairo_jar_class_files)
	$(JAR) cf $@ $(patsubst src/java/%.class,-C src/java %.class,$(all_cairo_jar_class_files))

# install pkg-config file
pkgconfigdir = $(libdir)/pkgconfig
pkgconfig_DATA = cairo-java.pc

# install examples script
exampledir = $(datadir)/doc/cairo-java-$(VERSION)/examples

# build api docs
apidir = $(datadir)/doc/cairo-java-$(VERSION)/api

if BUILD_JAVADOC
all-local: $(top_builddir)/doc-stamp
else
all-local:
endif

if BUILD_JAVADOC
doc-stamp: $(java_cairo_source_files)
	$(JAVADOC) \
		-d doc/api \
		$(JAVADOC_OPTIONS) \
		-sourcepath $(srcdir)/src/java \
		-windowtitle "Cairo-Java $(VERSION) API Reference" \
		-doctitle "Cairo-Java $(VERSION) API Reference" \
		-footer "$(JAVADOC_FOOTER)" \
		org.freedesktop.cairo
	touch doc-stamp
endif

# install other docs
docdir = $(datadir)/doc/cairo-java-$(VERSION)
doc_DATA = $(srcdir)/AUTHORS $(srcdir)/COPYING \
	$(srcdir)/NEWS $(srcdir)/README 

all_dest_cairo_javadoc_html_files = $(patsubst doc/api/%.html,%.html,$(shell find doc/api -name '*.html'))
dest_cairo_javadoc_dirs = $(patsubst doc/api/%,%,$(shell find doc/api -mindepth 1 -type d))

install-data-hook:
	cd $(DESTDIR)$(datadir)/java && \
		mv -f cairo$(apiversion).jar cairo$(apiversion)-$(VERSION).jar && \
		$(LN_S) cairo$(apiversion)-$(VERSION).jar cairo$(apiversion).jar

# install api documentation
if BUILD_JAVADOC
	$(mkinstalldirs) $(DESTDIR)$(apidir)
	@for dir in $(dest_cairo_javadoc_dirs); \
	do \
	   $(mkinstalldirs) $(DESTDIR)$(apidir)/$${dir}; \
	done
	@for file in $(all_dest_cairo_javadoc_html_files); \
	do \
	   $(INSTALL_DATA) doc/api/$${file} $(DESTDIR)$(apidir)/$${file}; \
	done
endif

# install examples
	@for dir in $(examples); \
	do \
	   $(mkinstalldirs) $(DESTDIR)$(exampledir)/$${dir}; \
	done
	@for file in $(example_files); \
	do \
	   $(INSTALL_DATA) $(srcdir)/$${file} $(DESTDIR)$(exampledir)/`echo $${file} | \
	      sed 's%^doc/examples/%%'`; \
	done

uninstall-local:
	-rm -rf $(DESTDIR)$(datadir)/doc/cairo-java-$(VERSION)
	-rm -f $(DESTDIR)$(cairo_jardir)/cairo$(apiversion)-$(VERSION).jar

BUILT_SOURCES = \
	cairo-java.pc \
	src/java/org/freedesktop/cairo/Config.java

EXTRA_DIST = \
	src/java/org/freedesktop/cairo/Config.java.in \
	$(example_files) 

clean-local:
	-rm -rf doc/api

distclean-local:
	-rm -rf $(srcdir)/autom4te.cache

DISTCLEANFILES = \
	cairo-java.pc \
	src/java/org/freedesktop/cairo/Config.java \
	$(srcdir)/Makefile.in \
	$(srcdir)/aclocal.m4 \
	$(srcdir)/compile \
	$(srcdir)/config.guess \
	$(srcdir)/config.sub \
	$(srcdir)/configure \
	$(srcdir)/depcomp \
	$(srcdir)/install-sh \
	$(srcdir)/ltmain.sh \
	$(srcdir)/missing

CLEANFILES = \
	doc-stamp \
	src/java/org/freedesktop/cairo/Config.class \
	$(all_cairo_jar_class_files) \
	$(cairo_javadoc_html_files) \
	$(shell find doc -name '*.html') \
	doc/api/package-list \
	doc/api/stylesheet.css \
	doc/api/resources/inherit.gif \
	cairo$(apiversion).jar


--- NEW FILE: configure.ac ---
dnl Process this file with autoconf to produce a configure script.
dnl
dnl This file is part of Java-GNOME.
dnl
dnl Java-GNOME is free software; you can redistribute it and/or modify it
dnl under the terms of the GNU General Public License as published by
dnl the Free Software Foundation; either version 2, or (at your option)
dnl any later version.
dnl
dnl Java-GNOME is distributed in the hope that it will be useful, but
dnl WITHOUT ANY WARRANTY; without even the implied warranty of
dnl MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
dnl GNU General Public License for more details.
dnl
dnl You should have received a copy of the GNU General Public License
dnl along with Jade; see the file COPYING.  If not, write to
dnl the Free Software Foundation, 675 Mass Ave, Cambridge, MA 02139, USA.

AC_INIT(src/jni/org_freedesktop_cairo_Cairo.c)
AC_CONFIG_AUX_DIR(.)
AM_INIT_AUTOMAKE(cairo-java, 0.3.0)

AM_PROG_GCJ

AC_DISABLE_STATIC
AC_PROG_LIBTOOL

apiversion="0.3"
VERSION="0.3.0"

INSTALLED_CLASSPATH=\${prefix}/share/java/cairo${apiversion}-${VERSION}.jar 
INSTALLED_JNI_DIR=\${prefix}/lib/
AC_SUBST(INSTALLED_CLASSPATH)
AC_SUBST(INSTALLED_JNI_DIR)

AC_SUBST(apiversion)

BUILDDIR=`pwd`

INSTALLED_CLASSPATH_BUILDPLACE=$BUILDDIR/lib/cairo${apiversion}-${VERSION}.jar 
INSTALLED_JNI_DIR_BUILDPLACE=$BUILDDIR/lib/
AC_SUBST(INSTALLED_CLASSPATH_BUILDPLACE)
AC_SUBST(INSTALLED_JNI_DIR_BUILDPLACE)

JG_GTK_JAVA(2.5)

JG_COMMON
AM_PROG_CC_C_O

PKG_CHECK_MODULES(CAIRO, cairo >= 0.3.0)
AC_SUBST(CAIRO_CFLAGS)
AC_SUBST(CAIRO_LIBS)

PKG_CHECK_MODULES(FONTCONFIG, fontconfig >= 2.2.99)
AC_SUBST(FONTCONFIG_CFLAGS)
AC_SUBST(FONTCONFIG_LIBS)

AC_CONFIG_FILES([Makefile])
AC_CONFIG_FILES([cairo-java.pc])
AC_CONFIG_FILES([src/java/org/freedesktop/cairo/Config.java])
AC_OUTPUT


--- NEW FILE: ChangeLog ---
2005-02-23  Jeffrey Morgan  <kuzman at gmail.com>

	* cairo-java:
	Initial import.

--- NEW FILE: INSTALL ---
Installation Instructions
*************************

Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004 Free
Software Foundation, Inc.

This file is free documentation; the Free Software Foundation gives
unlimited permission to copy, distribute and modify it.

Basic Installation
==================

These are generic installation instructions.

   The `configure' shell script attempts to guess correct values for
various system-dependent variables used during compilation.  It uses
those values to create a `Makefile' in each directory of the package.
It may also create one or more `.h' files containing system-dependent
definitions.  Finally, it creates a shell script `config.status' that
you can run in the future to recreate the current configuration, and a
file `config.log' containing compiler output (useful mainly for
debugging `configure').

   It can also use an optional file (typically called `config.cache'
and enabled with `--cache-file=config.cache' or simply `-C') that saves
the results of its tests to speed up reconfiguring.  (Caching is
disabled by default to prevent problems with accidental use of stale
cache files.)

   If you need to do unusual things to compile the package, please try
to figure out how `configure' could check whether to do them, and mail
diffs or instructions to the address given in the `README' so they can
be considered for the next release.  If you are using the cache, and at
some point `config.cache' contains results you don't want to keep, you
may remove or edit it.

   The file `configure.ac' (or `configure.in') is used to create
`configure' by a program called `autoconf'.  You only need
`configure.ac' if you want to change it or regenerate `configure' using
a newer version of `autoconf'.

The simplest way to compile this package is:

  1. `cd' to the directory containing the package's source code and type
     `./configure' to configure the package for your system.  If you're
     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 package's 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.

Compilers and Options
=====================

Some systems require unusual options for compilation or linking that the
`configure' script does not know about.  Run `./configure --help' for
details on some of the pertinent environment variables.

   You can give `configure' initial values for configuration parameters
by setting variables in the command line or in the environment.  Here
is an example:

     ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix

   *Note Defining Variables::, for more details.

Compiling For Multiple Architectures
====================================

You can compile the package for more than one kind of computer at the
same time, by placing the object files for each architecture in their
own directory.  To do this, you must use a version of `make' that
supports the `VPATH' variable, such as GNU `make'.  `cd' to the
directory where you want the object files and executables to go and run
the `configure' script.  `configure' automatically checks for the
source code in the directory that `configure' is in and in `..'.

   If you have to use a `make' that does not support the `VPATH'
variable, you have to compile the package for one architecture at a
time in the source code directory.  After you have installed the
package for one architecture, use `make distclean' before reconfiguring
for another architecture.

Installation Names
==================

By default, `make install' will install the package's files in
`/usr/local/bin', `/usr/local/man', etc.  You can specify an
installation prefix other than `/usr/local' by giving `configure' the
option `--prefix=PREFIX'.

   You can specify separate installation prefixes for
architecture-specific files and architecture-independent files.  If you
give `configure' the option `--exec-prefix=PREFIX', the package will
use PREFIX as the prefix for installing programs and libraries.
Documentation and other data files will still use the regular prefix.

   In addition, if you use an unusual directory layout you can give
options like `--bindir=DIR' to specify different values for particular
kinds of files.  Run `configure --help' for a list of the directories
you can set and what kinds of files go in them.

   If the package supports it, you can cause programs to be installed
with an extra prefix or suffix on their names by giving `configure' the
option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.

Optional Features
=================

Some packages pay attention to `--enable-FEATURE' options to
`configure', where FEATURE indicates an optional part of the package.
They may also pay attention to `--with-PACKAGE' options, where PACKAGE
is something like `gnu-as' or `x' (for the X Window System).  The
`README' should mention any `--enable-' and `--with-' options that the
package recognizes.

   For packages that use the X Window System, `configure' can usually
find the X include and library files automatically, but if it doesn't,
you can use the `configure' options `--x-includes=DIR' and
`--x-libraries=DIR' to specify their locations.

Specifying the System Type
==========================

There may be some features `configure' cannot figure out automatically,
but needs to determine by the type of machine the package will run on.
Usually, assuming the package is built to be run on the _same_
architectures, `configure' can figure that out, but if it prints a
message saying it cannot guess the machine type, give it the
`--build=TYPE' option.  TYPE can either be a short name for the system
type, such as `sun4', or a canonical name which has the form:

     CPU-COMPANY-SYSTEM

where SYSTEM can have one of these forms:

     OS KERNEL-OS

   See the file `config.sub' for the possible values of each field.  If
`config.sub' isn't included in this package, then this package doesn't
need to know the machine type.

   If you are _building_ compiler tools for cross-compiling, you should
use the `--target=TYPE' option to select the type of system they will
produce code for.

   If you want to _use_ a cross compiler, that generates code for a
platform different from the build platform, you should specify the
"host" platform (i.e., that on which the generated programs will
eventually be run) with `--host=TYPE'.

Sharing Defaults
================

If you want to set default values for `configure' scripts to share, you
can create a site shell script called `config.site' that gives default
values for variables like `CC', `cache_file', and `prefix'.
`configure' looks for `PREFIX/share/config.site' if it exists, then
`PREFIX/etc/config.site' if it exists.  Or, you can set the
`CONFIG_SITE' environment variable to the location of the site script.
A warning: not all `configure' scripts look for a site script.

Defining Variables
==================

Variables not defined in a site shell script can be set in the
environment passed to `configure'.  However, some packages may run
configure again during the build, and the customized values of these
variables may be lost.  In order to avoid this problem, you should set
them in the `configure' command line, using `VAR=value'.  For example:

     ./configure CC=/usr/local2/bin/gcc

will cause the specified gcc to be used as the C compiler (unless it is
overridden in the site shell script).

`configure' Invocation
======================

`configure' recognizes the following options to control how it operates.

`--help'
`-h'
     Print a summary of the options to `configure', and exit.

`--version'
`-V'
     Print the version of Autoconf used to generate the `configure'
     script, and exit.

`--cache-file=FILE'
     Enable the cache: use and save the results of the tests in FILE,
     traditionally `config.cache'.  FILE defaults to `/dev/null' to
     disable caching.

`--config-cache'
`-C'
     Alias for `--cache-file=config.cache'.

`--quiet'
`--silent'
`-q'
     Do not print messages saying which checks are being made.  To
     suppress all normal output, redirect it to `/dev/null' (any error
     messages will still be shown).

`--srcdir=DIR'
     Look for the package's source code in directory DIR.  Usually
     `configure' can determine that directory automatically.

`configure' also accepts some other, not widely useful, options.  Run
`configure --help' for more details.


--- NEW FILE: README ---
Java-GNOME
==========

Java-GNOME is a set of Java bindings for GNOME and GTK libraries,
so GNOME applications can be written in Java.  It is implemented
as a JNI layer that delegates the Java calls out to the underlying
C library.

The official web site is:
  http://java-gnome.sourceforge.net


  Installation
  ============

  See the INSTALL file


  How to report bugs
  ==================

  You can submit bugs at the following url:
    http://bugzilla.gnome.org/enter_bug.cgi?product=java-gnome
     
     Please indicate what version of the library you were using when
     you encountered the bug.  

     Please include the following information in your bug report:

     1) The type of system and version of the operating system you are using.
     2) The version of GTK/GNOME you are using.
     3) A detailed description of the bug.  If the bug is reporducable, please
     indicate haw to reproduce.

     You can also submit enhancement requests at the same location.


     CVS access
     ==========

     The source is available via anonymous cvs. To checkout you can use the
     following command:

       cvs -d:pserver:anonymous at anoncvs.gnome.org:/cvs/gnome login

       When prompted for a password hit enter.

       After login you can checkout the code with this command:

         cvs -z3 -d:pserver:anonymous at anoncvs.gnome.org:/cvs/gnome co java-gnome


	 How to submit patches
	 =====================

	 Patches can be submitted at the following url:
	   http://bugzilla.gnome.org/enter_bug.cgi?product=java-gnome


	   How can I contribute / join the team
	   ====================================

	   Submitting bugs and patches is a great help to the team.  If you wish
	   to have a greater involvement, we would welcome new members to the team.
	   Just send an email to jeffrey.morgan at bristolwest.com and I will help you get started.



--- NEW FILE: .cvsignore ---
bin
doc

--- NEW FILE: cairo-java.pc.in ---
prefix=@prefix@
exec_prefix=@exec_prefix@
libdir=@libdir@
includedir=@includedir@


Name: Cairo-Java
Description: Cairo Java bindings
Version: @VERSION@
api_version=@apiversion@
classpath=@INSTALLED_CLASSPATH@
Libs: -L at libdir@ -lcairojava

--- NEW FILE: NEWS ---