Permalink
Browse files

Imported version 0.0.3

  • Loading branch information...
korczis committed Jun 13, 2011
0 parents commit 4bdc0d5c3434b4cbc4d10ab8191bfc1075d0b71e
Showing with 58,743 additions and 0 deletions.
  1. 0 AUTHORS
  2. +512 −0 COPYING
  3. +824 −0 ChangeLog
  4. +229 −0 INSTALL
  5. +128 −0 Makefile.am
  6. +1,330 −0 Makefile.in
  7. 0 NEWS
  8. 0 README
  9. +7,630 −0 aclocal.m4
  10. +142 −0 compile
  11. +1,500 −0 config.guess
  12. +1,616 −0 config.sub
  13. +21,988 −0 configure
  14. +208 −0 configure.ac
  15. +530 −0 depcomp
  16. +323 −0 install-sh
  17. +10 −0 libtwin.pc.in
  18. +1,272 −0 libtwin/twin.h
  19. +266 −0 libtwin/twin_box.c
  20. +131 −0 libtwin/twin_button.c
  21. +297 −0 libtwin/twin_convolve.c
  22. +258 −0 libtwin/twin_cursor.c
  23. +33 −0 libtwin/twin_dispatch.c
  24. +734 −0 libtwin/twin_draw.c
  25. +589 −0 libtwin/twin_fbdev.c
  26. +96 −0 libtwin/twin_fbdev.h
  27. +72 −0 libtwin/twin_feature.c
  28. +121 −0 libtwin/twin_file.c
  29. +142 −0 libtwin/twin_fixed.c
  30. +613 −0 libtwin/twin_font.c
  31. +1,065 −0 libtwin/twin_font_default.c
  32. +64 −0 libtwin/twin_geom.c
  33. +262 −0 libtwin/twin_hull.c
  34. +181 −0 libtwin/twin_icon.c
  35. +217 −0 libtwin/twin_jpeg.c
  36. +46 −0 libtwin/twin_jpeg.h
  37. +158 −0 libtwin/twin_label.c
  38. +144 −0 libtwin/twin_linux_js.c
  39. +37 −0 libtwin/twin_linux_js.h
  40. +193 −0 libtwin/twin_linux_mouse.c
  41. +67 −0 libtwin/twin_linux_mouse.h
  42. +222 −0 libtwin/twin_matrix.c
  43. +606 −0 libtwin/twin_path.c
  44. +41 −0 libtwin/twin_pattern.c
  45. +346 −0 libtwin/twin_pixmap.c
  46. +188 −0 libtwin/twin_png.c
  47. +28 −0 libtwin/twin_png.h
  48. +385 −0 libtwin/twin_poly.c
  49. +402 −0 libtwin/twin_primitive.c
  50. +108 −0 libtwin/twin_queue.c
  51. +432 −0 libtwin/twin_screen.c
  52. +136 −0 libtwin/twin_spline.c
  53. +123 −0 libtwin/twin_timeout.c
  54. +190 −0 libtwin/twin_toplevel.c
  55. +224 −0 libtwin/twin_trig.c
  56. +275 −0 libtwin/twin_widget.c
  57. +503 −0 libtwin/twin_window.c
  58. +79 −0 libtwin/twin_work.c
  59. +228 −0 libtwin/twin_x11.c
  60. +61 −0 libtwin/twin_x11.h
  61. +556 −0 libtwin/twinint.h
  62. +6,871 −0 ltmain.sh
  63. +360 −0 missing
  64. +62 −0 twin_def.h
  65. +61 −0 twin_def.h.in
  66. +107 −0 twin_demos/ftwin.c
  67. +239 −0 twin_demos/twin_calc.c
  68. +32 −0 twin_demos/twin_calc.h
  69. +270 −0 twin_demos/twin_clock.c
  70. +49 −0 twin_demos/twin_clock.h
  71. +453 −0 twin_demos/twin_demo.c
  72. +30 −0 twin_demos/twin_demo.h
  73. +154 −0 twin_demos/twin_demoline.c
  74. +52 −0 twin_demos/twin_demoline.h
  75. +166 −0 twin_demos/twin_demospline.c
  76. +54 −0 twin_demos/twin_demospline.h
  77. +72 −0 twin_demos/twin_hello.c
  78. +30 −0 twin_demos/twin_hello.h
  79. +83 −0 twin_demos/twin_text.c
  80. +30 −0 twin_demos/twin_text.h
  81. +74 −0 twin_demos/xtwin.c
  82. +292 −0 twin_ttf/twin_ttf.c
  83. +41 −0 twin_ttf/twin_ttf.h
No changes.
512 COPYING

Large diffs are not rendered by default.

Oops, something went wrong.
824 ChangeLog

Large diffs are not rendered by default.

Oops, something went wrong.
229 INSTALL
@@ -0,0 +1,229 @@
+Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002 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=PATH'.
+
+ You can specify separate installation prefixes for
+architecture-specific files and architecture-independent files. If you
+give `configure' the option `--exec-prefix=PATH', the package will use
+PATH 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=PATH' 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.
+
@@ -0,0 +1,128 @@
+AM_CFLAGS = @WARN_CFLAGS@ @ALTIVEC_CFLAGS@
+
+EXTRA_PROGRAMS =
+
+bin_PROGRAMS =
+lib_LTLIBRARIES = libtwin/libtwin.la
+pkginclude_HEADERS = libtwin/twin.h
+
+libtwin_libtwin_la_LDFLAGS = -version-info @LIB_VERSION@
+libtwin_libtwin_la_SOURCES = \
+ libtwin/twin_box.c \
+ libtwin/twin_button.c \
+ libtwin/twin_convolve.c \
+ libtwin/twin_cursor.c \
+ libtwin/twin_dispatch.c \
+ libtwin/twin_draw.c \
+ libtwin/twin_feature.c \
+ libtwin/twin_hull.c \
+ libtwin/twin_icon.c \
+ libtwin/twin_file.c \
+ libtwin/twin_fixed.c \
+ libtwin/twin_font.c \
+ libtwin/twin_font_default.c \
+ libtwin/twin_geom.c \
+ libtwin/twin_label.c \
+ libtwin/twin_matrix.c \
+ libtwin/twin_path.c \
+ libtwin/twin_pattern.c \
+ libtwin/twin_pixmap.c \
+ libtwin/twin_poly.c \
+ libtwin/twin_primitive.c \
+ libtwin/twin_queue.c \
+ libtwin/twin_screen.c \
+ libtwin/twin_spline.c \
+ libtwin/twin_timeout.c \
+ libtwin/twin_toplevel.c \
+ libtwin/twin_trig.c \
+ libtwin/twin_widget.c \
+ libtwin/twin_window.c \
+ libtwin/twin_work.c \
+ libtwin/twinint.h \
+ twin_def.h
+
+if TWIN_X11
+pkginclude_HEADERS += libtwin/twin_x11.h
+libtwin_libtwin_la_SOURCES += libtwin/twin_x11.c
+endif
+
+if TWIN_FB
+pkginclude_HEADERS += libtwin/twin_fbdev.h
+libtwin_libtwin_la_SOURCES += libtwin/twin_fbdev.c
+endif
+
+if TWIN_MOUSE
+pkginclude_HEADERS += libtwin/twin_linux_mouse.h
+libtwin_libtwin_la_SOURCES += libtwin/twin_linux_mouse.c
+endif
+
+if TWIN_JOYSTICK
+pkginclude_HEADERS += libtwin/twin_linux_js.h
+libtwin_libtwin_la_SOURCES += libtwin/twin_linux_js.c
+endif
+
+if TWIN_PNG
+pkginclude_HEADERS += libtwin/twin_png.h
+libtwin_libtwin_la_SOURCES += libtwin/twin_png.c
+endif
+
+if TWIN_JPEG
+pkginclude_HEADERS += libtwin/twin_jpeg.h
+libtwin_libtwin_la_SOURCES += libtwin/twin_jpeg.c
+endif
+
+pkgconfigdir = $(libdir)/pkgconfig
+pkgconfig_DATA = libtwin.pc
+
+# demo twin applications
+EXTRA_PROGRAMS += twin_demos/xtwin twin_demos/ftwin
+noinst_PROGRAMS =
+noinst_LIBRARIES = twin_demos/libtwin_demos.a
+
+if TWIN_X11
+noinst_PROGRAMS += twin_demos/xtwin
+endif
+
+if TWIN_FB
+noinst_PROGRAMS += twin_demos/ftwin
+endif
+
+twin_demos_xtwin_SOURCES = twin_demos/xtwin.c
+twin_demos_xtwin_CFLAGS = @TWIN_DEP_CFLAGS@ -I$(top_srcdir)/twin_demos
+twin_demos_xtwin_LDADD = twin_demos/libtwin_demos.a libtwin/libtwin.la \
+ @TWIN_DEP_LDFLAGS@
+
+twin_demos_ftwin_SOURCES = twin_demos/ftwin.c
+twin_demos_ftwin_CFLAGS = @TWIN_DEP_CFLAGS@ -I$(top_srcdir)/twin_demos
+twin_demos_ftwin_LDADD = twin_demos/libtwin_demos.a libtwin/libtwin.la \
+ @TWIN_DEP_LDFLAGS@
+
+twin_demos_libtwin_demos_a_CFLAGS = @WARN_CFLAGS@ -I$(top_srcdir)/twin_demos
+twin_demos_libtwin_demos_a_SOURCES = \
+ twin_demos/twin_calc.c twin_demos/twin_calc.h \
+ twin_demos/twin_clock.c twin_demos/twin_clock.h \
+ twin_demos/twin_demo.c twin_demos/twin_demo.h \
+ twin_demos/twin_demoline.c twin_demos/twin_demoline.h \
+ twin_demos/twin_demospline.c twin_demos/twin_demospline.h \
+ twin_demos/twin_hello.c twin_demos/twin_hello.h \
+ twin_demos/twin_text.c twin_demos/twin_text.h
+
+# at the moment, the twin demos require twinint.h :(
+twin_demos_xtwin_CFLAGS += -I$(top_srcdir)/libtwin
+twin_demos_ftwin_CFLAGS += -I$(top_srcdir)/libtwin
+twin_demos_libtwin_demos_a_CFLAGS += -I$(top_srcdir)/libtwin
+
+# twin_ttf
+EXTRA_PROGRAMS += twin_ttf/twin_ttf
+
+if TWIN_TTF
+bin_PROGRAMS += twin_ttf/twin_ttf
+endif
+
+twin_ttf_twin_ttf_SOURCES = \
+ twin_ttf/twin_ttf.h \
+ twin_ttf/twin_ttf.c
+
+twin_ttf_twin_ttf_LDADD = @FREETYPE_LIBS@ -lm
+twin_ttf_twin_ttf_CFLAGS = -g @WARN_CFLAGS@
+twin_ttf_twin_ttf_CPPFLAGS = @FREETYPE_CFLAGS@ -I$(top_srcdir)/twin_ttf
Oops, something went wrong.

0 comments on commit 4bdc0d5

Please sign in to comment.