That's it! The program should install to /usr/local.
Installing XML Copy Editor
==========================
At first startup, the application tries to locate its data files in /usr/local/share/xmlcopyeditor or, failing that, /usr/share/xmlcopyeditor. If icons, the About page, and so on are not available at runtime, it is likely that the application was unable to find the application directory. You can correct it in the General Pane of the Options dialog under Tools or simply change the applicationDir entry in .xmlcopyeditor, which you can find in your home directory after running the application for the first time.
If you have any questions, please do not hesitate to contact gnschmidt@users.sourceforge.net.
How to build wxWidgets (if your distribution doesn't package wxGTK-2.8.x)
<http://sourceforge.net/project/showfiles.php?group_id=9863&package_id=14076> and unpack.
$ cd wxGTK-2.8.*
$ mkdir build
$ cd build
$ ../configure --enable-unicode
$ make
$ [as root] make install
$ cd contrib/src/stc
$ make
$ [as root] make install
Q: Will wxGTK-2.6.x work?
A: Unfortunately not. The program relies on a number of features (notably the docking library wxAUI) that were not available in a stable build of wxGTK until version 2.8.0.
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, a file
`config.cache' that saves the results of its tests to speed up
reconfiguring, 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. If at some point `config.cache'
contains results you don't want to keep, you may remove or edit it.
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 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 a while. While running, it prints some
messages telling which features it is checking for.
2. Type `make' to compile the package.
3. Type `make install' to install the programs and any data files and
documentation.
4. You can remove the program binaries and object files from the
source code directory by typing `make clean'.
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:
