Permalink
Browse files

This commit was generated by cvs2svn to compensate for changes in r2,

which included commits to RCS files with non-trunk default branches.


git-svn-id: https://wxmaxima.svn.sourceforge.net/svnroot/wxmaxima/trunk@3 cef4cce0-9ccc-409e-9180-6d2a30c8385f
  • Loading branch information...
andrejv committed Jan 29, 2005
1 parent f474f28 commit a96b09c95a3d71db9d4632ef177c6e5a282bc67a
Showing with 36,780 additions and 0 deletions.
  1. 0 ABOUT-NLS
  2. +5 −0 AUTHORS
  3. +340 −0 COPYING
  4. 0 ChangeLog
  5. +229 −0 INSTALL
  6. +9 −0 Makefile.am
  7. +632 −0 Makefile.in
  8. 0 NEWS
  9. +113 −0 README
  10. +1,442 −0 aclocal.m4
  11. +5 −0 bootstrap
  12. +1,411 −0 config.guess
  13. +1,500 −0 config.sub
  14. +5,316 −0 configure
  15. +141 −0 configure.in
  16. +479 −0 depcomp
  17. +294 −0 install-sh
  18. +86 −0 locales/Makefile.am
  19. +388 −0 locales/Makefile.in
  20. +2,293 −0 locales/es.po
  21. +2,404 −0 locales/fr.po
  22. +2,293 −0 locales/it.po
  23. BIN locales/wxwin/es.mo
  24. BIN locales/wxwin/fr.mo
  25. BIN locales/wxwin/it.mo
  26. BIN maxima-new.png
  27. +336 −0 missing
  28. +111 −0 mkinstalldirs
  29. +121 −0 src/AbsCell.cpp
  30. +43 −0 src/AbsCell.h
  31. +146 −0 src/AtCell.cpp
  32. +46 −0 src/AtCell.h
  33. +124 −0 src/BC2Wiz.cpp
  34. +61 −0 src/BC2Wiz.h
  35. +105 −0 src/BTextCtrl.cpp
  36. +44 −0 src/BTextCtrl.h
  37. +169 −0 src/CellParser.cpp
  38. +52 −0 src/CellParser.h
  39. +261 −0 src/CommandLine.cpp
  40. +56 −0 src/CommandLine.h
  41. +659 −0 src/Config.cpp
  42. +104 −0 src/Config.h
  43. +133 −0 src/DiffCell.cpp
  44. +47 −0 src/DiffCell.h
  45. +61 −0 src/DragNDrop.cpp
  46. +45 −0 src/DragNDrop.h
  47. +152 −0 src/ExptCell.cpp
  48. +49 −0 src/ExptCell.h
  49. +174 −0 src/FracCell.cpp
  50. +55 −0 src/FracCell.h
  51. +131 −0 src/FunCell.cpp
  52. +46 −0 src/FunCell.h
  53. +94 −0 src/Gen1Wiz.cpp
  54. +55 −0 src/Gen1Wiz.h
  55. +92 −0 src/Gen2Wiz.cpp
  56. +60 −0 src/Gen2Wiz.h
  57. +88 −0 src/Gen3Wiz.cpp
  58. +61 −0 src/Gen3Wiz.h
  59. +92 −0 src/Gen4Wiz.cpp
  60. +64 −0 src/Gen4Wiz.h
  61. +110 −0 src/IC1Wiz.cpp
  62. +58 −0 src/IC1Wiz.h
  63. +114 −0 src/IC2Wiz.cpp
  64. +60 −0 src/IC2Wiz.h
  65. +263 −0 src/IntCell.cpp
  66. +60 −0 src/IntCell.h
  67. +169 −0 src/IntegrateWiz.cpp
  68. +68 −0 src/IntegrateWiz.h
  69. +169 −0 src/LimitCell.cpp
  70. +48 −0 src/LimitCell.h
  71. +148 −0 src/LimitWiz.cpp
  72. +65 −0 src/LimitWiz.h
  73. +66 −0 src/Makefile.am
  74. +574 −0 src/Makefile.in
  75. +232 −0 src/MatWiz.cpp
  76. +92 −0 src/MatWiz.h
  77. +363 −0 src/MathCell.cpp
  78. +113 −0 src/MathCell.h
  79. +800 −0 src/MathCtrl.cpp
  80. +83 −0 src/MathCtrl.h
  81. +501 −0 src/MathParser.cpp
  82. +55 −0 src/MathParser.h
  83. +332 −0 src/MathPrintout.cpp
  84. +62 −0 src/MathPrintout.h
  85. +197 −0 src/MatrCell.cpp
  86. +56 −0 src/MatrCell.h
  87. +149 −0 src/ParenCell.cpp
  88. +45 −0 src/ParenCell.h
  89. +497 −0 src/Plot2dWiz.cpp
  90. +114 −0 src/Plot2dWiz.h
  91. +422 −0 src/Plot3dWiz.cpp
  92. +84 −0 src/Plot3dWiz.h
  93. +3 −0 src/Resources.rc
  94. +141 −0 src/SeriesWiz.cpp
  95. +66 −0 src/SeriesWiz.h
  96. +138 −0 src/SqrtCell.cpp
  97. +43 −0 src/SqrtCell.h
  98. +140 −0 src/SubCell.cpp
  99. +46 −0 src/SubCell.h
  100. +115 −0 src/SubstituteWiz.cpp
  101. +59 −0 src/SubstituteWiz.h
  102. +272 −0 src/SumCell.cpp
  103. +58 −0 src/SumCell.h
  104. +124 −0 src/SumWiz.cpp
  105. +63 −0 src/SumWiz.h
  106. +101 −0 src/SystemWiz.cpp
  107. +56 −0 src/SystemWiz.h
  108. +227 −0 src/TextCell.cpp
  109. +49 −0 src/TextCell.h
  110. +125 −0 src/TextCtrl.cpp
  111. +44 −0 src/TextCtrl.h
  112. +95 −0 src/TextInput.cpp
  113. +50 −0 src/TextInput.h
  114. +42 −0 src/TextStyle.h
  115. +27 −0 src/Version.h
  116. BIN src/docs.zip
  117. BIN src/intro.zip
  118. +83 −0 src/main.cpp
  119. BIN src/maximaicon.ico
  120. +428 −0 src/maximaicon.xpm
  121. +19 −0 src/tips.txt
  122. +2,097 −0 src/wxMaxima.cpp
  123. +131 −0 src/wxMaxima.h
  124. +494 −0 src/wxMaximaFrame.cpp
  125. +215 −0 src/wxMaximaFrame.h
  126. +845 −0 src/wxmathml-cvs.lisp
  127. +833 −0 src/wxmathml.lisp
  128. +9 −0 wxmaxima.desktop
  129. +56 −0 wxmaxima.spec.in
View
No changes.
View
@@ -0,0 +1,5 @@
+Main developer:
+ Andrej Vodopivec <andrejv@users.sourceforge.net>
+
+Translators:
+ - French: Eric Delevaux <ericdel@libertysurf.fr>
View
340 COPYING

Large diffs are not rendered by default.

Oops, something went wrong.
View
No changes.
View
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.
+
View
@@ -0,0 +1,9 @@
+SUBDIRS = src locales
+
+EXTRA_DIST = bootstrap wxmaxima.spec.in wxmaxima.desktop maxima-new.png
+
+docdir = ${datadir}/wxMaxima
+doc_DATA = README COPYING
+
+issdir = ${prefix}
+iss_DATA = $(ISS_FILES)
Oops, something went wrong.

0 comments on commit a96b09c

Please sign in to comment.