readme

本人长期积累的一些系统小工具.其中包含了一些微软工具程序集中的工具,有了这些工具,你将更有能力处理Windows的各种问题

next up previous contents
Next: 3. Basic Usage Up: GNU Aspell 0.50.3 Previous: 1. Introduction   
Contents

Subsections

  * 2.1 Requirements
  * 2.2 Obtaining
  * 2.3 Support
  * 2.4 Helping Out
  * 2.5 Compiling & Installing
      + 2.5.1 Generic Install Instructions
      + 2.5.2 General Problems
      + 2.5.3 Curses Notes
      + 2.5.4 Upgrading from Aspell .33/Pspell .12
      + 2.5.5 Upgrading from a pre-release snapshot
      + 2.5.6 Win32 Notes
          o 2.5.6.1 Getting
          o 2.5.6.2 Building
          o 2.5.6.3 (PD)Curses
          o 2.5.6.4 Directories
          o 2.5.6.5 Installer
          o 2.5.6.6 Win32 consoles
  * 2.6 Using aspell-import

--------------------------------------------------------------------------

2. Getting Started


2.1 Requirements

Aspell requires gcc 2.95 (or better) as the C++ compiler. Other C++
compilers should work with some effort. Other C++ compilers for mostly
POSIX compliant (Unix, Linux, BeOS, CygWin) systems should work with out
any major problems provided that the compile can handle all of the
advanced C++ features Aspell uses. C++ compilers for non-Unix systems
might work but it will take some work. Aspell at very least requires a
Unix-like environment (sh, grep, sed, tr, etc...) in order to build.
Aspell also uses a few POSIX functions when necessary.

2.2 Obtaining

The latest version can always be found at GNU Aspell's home page at http:/
/aspell.net.

2.3 Support

Support for Aspell can be found on the Aspell mailing lists. Instructions
for joining the various mailing lists (and an archive of them) can be
found off the Aspell home page at http://aspell.net.

2.4 Helping Out

I have very little time to work on Aspell so I desperately need other
people to help with the development of Aspell. There are a lot of things
that need to be done before I consider Aspell complete. See section B.1
for a list of them. I would really appreciate some help with doing them.
If you are interested in helping with one of them please let me know.

I am also looking for someone to eventually take over the maintenance and
development of Aspell. If you are interested please contact me directly.

2.5 Compiling & Installing

2.5.1 Generic Install Instructions

    ./configure && make

For additional configure options type ./configure --help. You can control
what C++ compiler is used by setting the environmental variable CXX before
running configure and you can control what flags are passed to the C++
compile via the environmental variable CXXFLAGS. Static libraries are
disabled by default since static libraries will not work right due to the
mixing of C and C++. When a C program links with the static libraries in
Aspell it is likely to crash because Aspell's C++ objects are not getting
initialized correctly. However, if for some reason you want them, you can
enable them via --enable-static.

Aspell should then compile with out any additional user intervention. If
you run into problems please first check the sections below as that might
solve your problem.

To install the program simply type

    make install

After Aspell is installed at least one dictionary needs to be installed.
You can find them at http://aspell.net/. The "aspell" program must be in
your path in order for the dictionaries to install correctly.

If you do not have Ispell or the traditional Unix "spell" utility
installed on your system than you should also copy the compatibly scripts
"ispell" and "spell" located in the scripts/ directory into your
binary directory which is usually /usr/local/bin so that programs that
expect ispell or spell command will work correctly.

2.5.2 General Problems

Aspell does not use a released version of GNU Libtool. If you have a need
to modify configure.ac or any of the Makefile.am's you should install the
CVS version of libtool.

2.5.3 Curses Notes

If you are having problems compiling termios.cc than the most likely
reason is due to incompatibilities with the curses implementation on your
system. If this is the case than you can explicitly disable the curses
library with --disable-curses. By doing this you will lose the nice full
screen interface but hopefully you will be able to at least get Aspell to
compile correctly.

If the curses library is installed in a non-standard location than you can
specify the library and include directory with --enable-curses=玪ib