Permalink
Browse files

Restructured package and added polar plotting

  • Loading branch information...
1 parent 31d1dfc commit ed26955153aa0156f37350917ee62b30a5645266 @pchilds committed Feb 21, 2011
Showing with 38,875 additions and 253 deletions.
  1. +2 −0 AUTHORS
  2. 0 LICENSE → COPYING
  3. +161 −0 INSTALL
  4. +2 −0 NEWS
  5. +5 −0 PlotLinear/Makefile.am
  6. +9 −0 PlotLinear/configure.ac
  7. +9 −0 PlotLinear/src/Makefile.am
  8. +185 −113 { → PlotLinear/src}/plotlinear0-1-0.c
  9. 0 { → PlotLinear/src}/plotlinear0-1-0.h
  10. +88 −48 { → PlotLinear/src}/plotlinearboth0-1-0.c
  11. 0 { → PlotLinear/src}/plotlinearboth0-1-0.h
  12. +88 −48 { → PlotLinear/src}/plotlinearlines0-1-0.c
  13. 0 { → PlotLinear/src}/plotlinearlines0-1-0.h
  14. 0 { → PlotLinear/src}/plotlinearpoints0-1-0.c
  15. 0 { → PlotLinear/src}/plotlinearpoints0-1-0.h
  16. 0 { → PlotLinear/src}/testplotlinear0-1-0.c
  17. 0 { → PlotLinear/src}/testplotlinear0-1-0.h
  18. BIN PlotLinear/testplotlinear
  19. +5 −0 PlotLog/Makefile.am
  20. +9 −0 PlotLog/configure.ac
  21. +13 −0 PlotLog/src/Makefile.am
  22. 0 { → PlotLog/src}/plotlinearlog0-1-0.h
  23. 0 { → PlotLog/src}/plotlinearlogboth0-1-0.h
  24. 0 { → PlotLog/src}/plotlinearloglines0-1-0.h
  25. 0 { → PlotLog/src}/plotlinearlogpoints0-1-0.h
  26. 0 { → PlotLog/src}/plotloglinear0-1-0.h
  27. 0 { → PlotLog/src}/plotloglinearboth0-1-0.h
  28. 0 { → PlotLog/src}/plotloglinearlines0-1-0.h
  29. 0 { → PlotLog/src}/plotloglinearpoints0-1-0.h
  30. 0 { → PlotLog/src}/plotloglog0-1-0.h
  31. 0 { → PlotLog/src}/plotloglogboth0-1-0.h
  32. 0 { → PlotLog/src}/plotlogloglines0-1-0.h
  33. 0 { → PlotLog/src}/plotloglogpoints0-1-0.h
  34. +677 −0 PlotPolar/Makefile
  35. +5 −0 PlotPolar/Makefile.am
  36. +677 −0 PlotPolar/Makefile.in
  37. +1,109 −0 PlotPolar/aclocal.m4
  38. +4,690 −0 PlotPolar/autom4te.cache/output.0
  39. +4,690 −0 PlotPolar/autom4te.cache/output.1
  40. +141 −0 PlotPolar/autom4te.cache/requests
  41. +840 −0 PlotPolar/autom4te.cache/traces.0
  42. +337 −0 PlotPolar/autom4te.cache/traces.1
  43. +26 −0 PlotPolar/config.h
  44. +25 −0 PlotPolar/config.h.in
  45. +291 −0 PlotPolar/config.log
  46. +1,172 −0 PlotPolar/config.status
  47. +4,690 −0 PlotPolar/configure
  48. +9 −0 PlotPolar/configure.ac
  49. +630 −0 PlotPolar/depcomp
  50. +520 −0 PlotPolar/install-sh
  51. +376 −0 PlotPolar/missing
  52. +1,448 −0 PlotPolar/src/.deps/plotpolar0-1-0.Po
  53. +1,446 −0 PlotPolar/src/.deps/testplotpolar0-1-0.Po
  54. +459 −0 PlotPolar/src/Makefile
  55. +9 −0 PlotPolar/src/Makefile.am
  56. +459 −0 PlotPolar/src/Makefile.in
  57. BIN PlotPolar/src/TestPolarPlot
  58. +3,891 −0 PlotPolar/src/plotpolar0-0-8.c
  59. +4,378 −0 PlotPolar/src/plotpolar0-1-0.c
  60. +4,378 −0 PlotPolar/src/plotpolar0-1-0.c~
  61. +70 −0 PlotPolar/src/plotpolar0-1-0.h
  62. +6 −12 plotpolar0-1-0.h → PlotPolar/src/plotpolar0-1-0.h~
  63. BIN PlotPolar/src/plotpolar0-1-0.o
  64. +6 −12 { → PlotPolar/src}/plotpolarboth0-1-0.h
  65. +6 −10 { → PlotPolar/src}/plotpolarlines0-1-0.h
  66. +6 −10 { → PlotPolar/src}/plotpolarpoints0-1-0.h
  67. +247 −0 PlotPolar/src/testplotpolar0-1-0.c
  68. +247 −0 PlotPolar/src/testplotpolar0-1-0.c~
  69. +26 −0 PlotPolar/src/testplotpolar0-1-0.h
  70. +26 −0 PlotPolar/src/testplotpolar0-1-0.h~
  71. BIN PlotPolar/src/testplotpolar0-1-0.o
  72. +1 −0 PlotPolar/stamp-h1
  73. BIN PlotPolar/testplotpolar
  74. +243 −0 PlotPolar/testplotpolar0-1-0.c~
  75. +26 −0 PlotPolar/testplotpolar0-1-0.h~
  76. +16 −0 TODO
  77. BIN testplotlinear
View
@@ -0,0 +1,2 @@
+Paul Childs <p.childs@physics.org>
+
View
File renamed without changes.
View
@@ -0,0 +1,161 @@
+Basic Installation
+==================
+
+ These are more or less 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').
+
+ 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.
+
+ The file `configure.in' is used to create `configure' by a program
+called `autoconf'. You only need `configure.in' 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 named according to the desired plotting
+ function (e.g. /PlotPolar) 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. While
+ running, configure 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. 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.
+
+Alternately the following should work with gcc:
+
+ cd src
+ gcc -o testplotpolar testplotpolar0-1-0.c \
+ `pkg-config --cflags --libs gtk+-2.0` \
+ plotpolar0-1-0.h plotpolar0-1-0.c
+
+Compilers and Options
+=====================
+
+ Some systems require unusual options for compilation or linking that
+the `configure' script does not know about. You can give `configure'
+initial values for variables by setting them in the environment. Using
+a Bourne-compatible shell, you can do that on the command line like
+this:
+ CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
+
+Or on systems that have the `env' program, you can do it like this:
+ env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
+
+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 supports 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.
+
+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' can not figure out
+automatically, but needs to determine by the type of host the package
+will run on. Usually `configure' can figure that out, but if it prints
+a message saying it can not guess the host type, give it the
+`--host=TYPE' option. TYPE can either be a short name for the system
+type, such as `sun4', or a canonical name with three fields:
+ CPU-COMPANY-SYSTEM
+
+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 host type.
+
+ If you are building compiler tools for cross-compiling, you can also
+use the `--target=TYPE' option to select the type of system they will
+produce code for and the `--build=TYPE' option to select the type of
+system on which you are compiling the package.
+
+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.
+
+Operation Controls
+==================
+
+ `configure' recognizes the following options to control how it
+operates.
+
+`--cache-file=FILE'
+ Use and save the results of the tests in FILE instead of
+ `./config.cache'. Set FILE to `/dev/null' to disable caching, for
+ debugging `configure'.
+
+`--help'
+ Print a summary of the options to `configure', and exit.
+
+`--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.
+
+`--version'
+ Print the version of Autoconf used to generate the `configure'
+ script, and exit.
+
+`configure' also accepts some other, not widely useful, options.
+
View
@@ -0,0 +1,2 @@
+
+
@@ -0,0 +1,5 @@
+## Process this file with automake to produce Makefile.in
+SUBDIRS=src
+EXTRA_DIST= \
+ autogen.sh
+
@@ -0,0 +1,9 @@
+AC_PREREQ([2.65])
+AC_INIT([GtkPlot],[0.1.0],[pchilds@physics.org],[gtk-plot],[https://github.com/pchilds/GtkPlot])
+AC_CONFIG_SRCDIR([src/testplotlinear0-1-0.h])
+AM_INIT_AUTOMAKE([-Wall -Werror foreign])
+AC_PROG_CC([gcc cc])
+AC_CONFIG_HEADERS([config.h])
+PKG_CHECK_MODULES([LIN], [gtk+-2.0 >= 2.14])
+AC_CONFIG_FILES([Makefile src/Makefile])
+AC_OUTPUT()
@@ -0,0 +1,9 @@
+## Process this file with automake to produce Makefile.in
+AM_CFLAGS=$(LIN_CFLAGS)
+bin_PROGRAMS=TestLinearPlot
+TestLinearPlot_SOURCES= \
+ testplotlinear0-1-0.c \
+ plotlinear0-1-0.c \
+ testplotlinear0-1-0.h \
+ plotlinear0-1-0.h
+TestLinearPlot_LDADD=$(LIN_LIBS)
Oops, something went wrong.

0 comments on commit ed26955

Please sign in to comment.