Fixed incorrect permissions in root directory.
This commit is contained in:
Gerald Schmidt
parent
4484bc0f40
commit
33e0577f40
2
AUTHORS
2
AUTHORS
|
|
@ -1 +1 @@
|
||||||
Gerald Schmidt <gnschmidt@users.sourceforge.net>
|
Gerald Schmidt <gnschmidt@users.sourceforge.net>
|
||||||
|
|
|
||||||
6
COPYING
6
COPYING
|
|
@ -1,3 +1,3 @@
|
||||||
See src/copying for acknowledgements and licenses.
|
See src/copying for acknowledgements and licenses.
|
||||||
Acknowledgement files are copied to /usr/local/share/xmlcopyeditor/copying on install.
|
Acknowledgement files are copied to /usr/local/share/xmlcopyeditor/copying on install.
|
||||||
|
|
||||||
|
|
|
||||||
424
INSTALL
424
INSTALL
|
|
@ -1,212 +1,212 @@
|
||||||
How to build wxWidgets
|
How to build wxWidgets
|
||||||
==========================================
|
==========================================
|
||||||
|
|
||||||
Download wxGTK-2.8.0 (or higher) from
|
Download wxGTK-2.8.0 (or higher) from
|
||||||
<http://sourceforge.net/project/showfiles.php?group_id=9863&package_id=14076> and unpack.
|
<http://sourceforge.net/project/showfiles.php?group_id=9863&package_id=14076> and unpack.
|
||||||
|
|
||||||
$ cd wxGTK-2.8.0
|
$ cd wxGTK-2.8.0
|
||||||
$ mkdir buildstatic
|
$ mkdir buildstatic
|
||||||
$ cd buildstatic
|
$ cd buildstatic
|
||||||
$ ../configure --enable-unicode
|
$ ../configure --enable-unicode
|
||||||
$ make
|
$ make
|
||||||
$ [as root] make install
|
$ [as root] make install
|
||||||
$ cd contrib/src/stc
|
$ cd contrib/src/stc
|
||||||
$ make
|
$ make
|
||||||
$ [as root] make install
|
$ [as root] make install
|
||||||
|
|
||||||
NB If you wish to distribute the program in binary form, you may wish to add the flag --disable-shared to the call to configure.
|
NB If you wish to distribute the program in binary form, you may wish to add the flag --disable-shared to the call to configure.
|
||||||
|
|
||||||
Installing XML Copy Editor
|
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.
|
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.
|
If you have any questions, please do not hesitate to contact gnschmidt@users.sourceforge.net.
|
||||||
|
|
||||||
Fedora Core 5/6 installation
|
Fedora Core 5/6 installation
|
||||||
==========================
|
==========================
|
||||||
|
|
||||||
A binary rpm is available for fc5 users (which also works on fc6), but the build should run without errors using the Makefiles provided. A copy of xmlcopyeditor.spec can be found in the src directory. All suggestions welcome. If you are using Fedora Core 4, you can follow a link from the home page to a separately produced binary rpm.
|
A binary rpm is available for fc5 users (which also works on fc6), but the build should run without errors using the Makefiles provided. A copy of xmlcopyeditor.spec can be found in the src directory. All suggestions welcome. If you are using Fedora Core 4, you can follow a link from the home page to a separately produced binary rpm.
|
||||||
|
|
||||||
Arch Linux installation
|
Arch Linux installation
|
||||||
=======================
|
=======================
|
||||||
|
|
||||||
David Scholl has kindly prepared a build script for Arch Linux. See http://aur.archlinux.org/packages.php?do_Details=1&ID=6283 for details.
|
David Scholl has kindly prepared a build script for Arch Linux. See http://aur.archlinux.org/packages.php?do_Details=1&ID=6283 for details.
|
||||||
|
|
||||||
Ubuntu and Slackware
|
Ubuntu and Slackware
|
||||||
====================
|
====================
|
||||||
|
|
||||||
There are binary packages for both Ubuntu and Slackware Linux. Please follow the links on the home page.
|
There are binary packages for both Ubuntu and Slackware Linux. Please follow the links on the home page.
|
||||||
|
|
||||||
Other distributions
|
Other distributions
|
||||||
===================
|
===================
|
||||||
|
|
||||||
If you find that you need to tweak the Makefiles, please consider getting in touch so others can benefit from your effort.
|
If you find that you need to tweak the Makefiles, please consider getting in touch so others can benefit from your effort.
|
||||||
|
|
||||||
Basic Installation
|
Basic Installation
|
||||||
==================
|
==================
|
||||||
|
|
||||||
These are generic installation instructions.
|
These are generic installation instructions.
|
||||||
|
|
||||||
The `configure' shell script attempts to guess correct values for
|
The `configure' shell script attempts to guess correct values for
|
||||||
various system-dependent variables used during compilation. It uses
|
various system-dependent variables used during compilation. It uses
|
||||||
those values to create a `Makefile' in each directory of the package.
|
those values to create a `Makefile' in each directory of the package.
|
||||||
It may also create one or more `.h' files containing system-dependent
|
It may also create one or more `.h' files containing system-dependent
|
||||||
definitions. Finally, it creates a shell script `config.status' that
|
definitions. Finally, it creates a shell script `config.status' that
|
||||||
you can run in the future to recreate the current configuration, a file
|
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
|
`config.cache' that saves the results of its tests to speed up
|
||||||
reconfiguring, and a file `config.log' containing compiler output
|
reconfiguring, and a file `config.log' containing compiler output
|
||||||
(useful mainly for debugging `configure').
|
(useful mainly for debugging `configure').
|
||||||
|
|
||||||
If you need to do unusual things to compile the package, please try
|
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
|
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
|
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'
|
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.
|
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
|
The file `configure.in' is used to create `configure' by a program
|
||||||
called `autoconf'. You only need `configure.in' if you want to change
|
called `autoconf'. You only need `configure.in' if you want to change
|
||||||
it or regenerate `configure' using a newer version of `autoconf'.
|
it or regenerate `configure' using a newer version of `autoconf'.
|
||||||
|
|
||||||
The simplest way to compile this package is:
|
The simplest way to compile this package is:
|
||||||
|
|
||||||
1. `cd' to the directory containing the package's source code and type
|
1. `cd' to the directory containing the package's source code and type
|
||||||
`./configure' to configure the package for your system. If you're
|
`./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
|
using `csh' on an old version of System V, you might need to type
|
||||||
`sh ./configure' instead to prevent `csh' from trying to execute
|
`sh ./configure' instead to prevent `csh' from trying to execute
|
||||||
`configure' itself.
|
`configure' itself.
|
||||||
|
|
||||||
Running `configure' takes a while. While running, it prints some
|
Running `configure' takes a while. While running, it prints some
|
||||||
messages telling which features it is checking for.
|
messages telling which features it is checking for.
|
||||||
|
|
||||||
2. Type `make' to compile the package.
|
2. Type `make' to compile the package.
|
||||||
|
|
||||||
3. Type `make install' to install the programs and any data files and
|
3. Type `make install' to install the programs and any data files and
|
||||||
documentation.
|
documentation.
|
||||||
|
|
||||||
4. You can remove the program binaries and object files from the
|
4. You can remove the program binaries and object files from the
|
||||||
source code directory by typing `make clean'.
|
source code directory by typing `make clean'.
|
||||||
|
|
||||||
Compilers and Options
|
Compilers and Options
|
||||||
=====================
|
=====================
|
||||||
|
|
||||||
Some systems require unusual options for compilation or linking that
|
Some systems require unusual options for compilation or linking that
|
||||||
the `configure' script does not know about. You can give `configure'
|
the `configure' script does not know about. You can give `configure'
|
||||||
initial values for variables by setting them in the environment. Using
|
initial values for variables by setting them in the environment. Using
|
||||||
a Bourne-compatible shell, you can do that on the command line like
|
a Bourne-compatible shell, you can do that on the command line like
|
||||||
this:
|
this:
|
||||||
CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
|
CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
|
||||||
|
|
||||||
Or on systems that have the `env' program, you can do it like this:
|
Or on systems that have the `env' program, you can do it like this:
|
||||||
env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
|
env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
|
||||||
|
|
||||||
Compiling For Multiple Architectures
|
Compiling For Multiple Architectures
|
||||||
====================================
|
====================================
|
||||||
|
|
||||||
You can compile the package for more than one kind of computer at the
|
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
|
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
|
own directory. To do this, you must use a version of `make' that
|
||||||
supports the `VPATH' variable, such as GNU `make'. `cd' to the
|
supports the `VPATH' variable, such as GNU `make'. `cd' to the
|
||||||
directory where you want the object files and executables to go and run
|
directory where you want the object files and executables to go and run
|
||||||
the `configure' script. `configure' automatically checks for the
|
the `configure' script. `configure' automatically checks for the
|
||||||
source code in the directory that `configure' is in and in `..'.
|
source code in the directory that `configure' is in and in `..'.
|
||||||
|
|
||||||
If you have to use a `make' that does not supports the `VPATH'
|
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
|
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
|
in the source code directory. After you have installed the package for
|
||||||
one architecture, use `make distclean' before reconfiguring for another
|
one architecture, use `make distclean' before reconfiguring for another
|
||||||
architecture.
|
architecture.
|
||||||
|
|
||||||
Installation Names
|
Installation Names
|
||||||
==================
|
==================
|
||||||
|
|
||||||
By default, `make install' will install the package's files in
|
By default, `make install' will install the package's files in
|
||||||
`/usr/local/bin', `/usr/local/man', etc. You can specify an
|
`/usr/local/bin', `/usr/local/man', etc. You can specify an
|
||||||
installation prefix other than `/usr/local' by giving `configure' the
|
installation prefix other than `/usr/local' by giving `configure' the
|
||||||
option `--prefix=PATH'.
|
option `--prefix=PATH'.
|
||||||
|
|
||||||
You can specify separate installation prefixes for
|
You can specify separate installation prefixes for
|
||||||
architecture-specific files and architecture-independent files. If you
|
architecture-specific files and architecture-independent files. If you
|
||||||
give `configure' the option `--exec-prefix=PATH', the package will use
|
give `configure' the option `--exec-prefix=PATH', the package will use
|
||||||
PATH as the prefix for installing programs and libraries.
|
PATH as the prefix for installing programs and libraries.
|
||||||
Documentation and other data files will still use the regular prefix.
|
Documentation and other data files will still use the regular prefix.
|
||||||
|
|
||||||
If the package supports it, you can cause programs to be installed
|
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
|
with an extra prefix or suffix on their names by giving `configure' the
|
||||||
option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
|
option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
|
||||||
|
|
||||||
Optional Features
|
Optional Features
|
||||||
=================
|
=================
|
||||||
|
|
||||||
Some packages pay attention to `--enable-FEATURE' options to
|
Some packages pay attention to `--enable-FEATURE' options to
|
||||||
`configure', where FEATURE indicates an optional part of the package.
|
`configure', where FEATURE indicates an optional part of the package.
|
||||||
They may also pay attention to `--with-PACKAGE' options, where 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
|
is something like `gnu-as' or `x' (for the X Window System). The
|
||||||
`README' should mention any `--enable-' and `--with-' options that the
|
`README' should mention any `--enable-' and `--with-' options that the
|
||||||
package recognizes.
|
package recognizes.
|
||||||
|
|
||||||
For packages that use the X Window System, `configure' can usually
|
For packages that use the X Window System, `configure' can usually
|
||||||
find the X include and library files automatically, but if it doesn't,
|
find the X include and library files automatically, but if it doesn't,
|
||||||
you can use the `configure' options `--x-includes=DIR' and
|
you can use the `configure' options `--x-includes=DIR' and
|
||||||
`--x-libraries=DIR' to specify their locations.
|
`--x-libraries=DIR' to specify their locations.
|
||||||
|
|
||||||
Specifying the System Type
|
Specifying the System Type
|
||||||
==========================
|
==========================
|
||||||
|
|
||||||
There may be some features `configure' can not figure out
|
There may be some features `configure' can not figure out
|
||||||
automatically, but needs to determine by the type of host the package
|
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
|
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
|
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
|
`--host=TYPE' option. TYPE can either be a short name for the system
|
||||||
type, such as `sun4', or a canonical name with three fields:
|
type, such as `sun4', or a canonical name with three fields:
|
||||||
CPU-COMPANY-SYSTEM
|
CPU-COMPANY-SYSTEM
|
||||||
|
|
||||||
See the file `config.sub' for the possible values of each field. If
|
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
|
`config.sub' isn't included in this package, then this package doesn't
|
||||||
need to know the host type.
|
need to know the host type.
|
||||||
|
|
||||||
If you are building compiler tools for cross-compiling, you can also
|
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
|
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
|
produce code for and the `--build=TYPE' option to select the type of
|
||||||
system on which you are compiling the package.
|
system on which you are compiling the package.
|
||||||
|
|
||||||
Sharing Defaults
|
Sharing Defaults
|
||||||
================
|
================
|
||||||
|
|
||||||
If you want to set default values for `configure' scripts to share,
|
If you want to set default values for `configure' scripts to share,
|
||||||
you can create a site shell script called `config.site' that gives
|
you can create a site shell script called `config.site' that gives
|
||||||
default values for variables like `CC', `cache_file', and `prefix'.
|
default values for variables like `CC', `cache_file', and `prefix'.
|
||||||
`configure' looks for `PREFIX/share/config.site' if it exists, then
|
`configure' looks for `PREFIX/share/config.site' if it exists, then
|
||||||
`PREFIX/etc/config.site' if it exists. Or, you can set the
|
`PREFIX/etc/config.site' if it exists. Or, you can set the
|
||||||
`CONFIG_SITE' environment variable to the location of the site script.
|
`CONFIG_SITE' environment variable to the location of the site script.
|
||||||
A warning: not all `configure' scripts look for a site script.
|
A warning: not all `configure' scripts look for a site script.
|
||||||
|
|
||||||
Operation Controls
|
Operation Controls
|
||||||
==================
|
==================
|
||||||
|
|
||||||
`configure' recognizes the following options to control how it
|
`configure' recognizes the following options to control how it
|
||||||
operates.
|
operates.
|
||||||
|
|
||||||
`--cache-file=FILE'
|
`--cache-file=FILE'
|
||||||
Use and save the results of the tests in FILE instead of
|
Use and save the results of the tests in FILE instead of
|
||||||
`./config.cache'. Set FILE to `/dev/null' to disable caching, for
|
`./config.cache'. Set FILE to `/dev/null' to disable caching, for
|
||||||
debugging `configure'.
|
debugging `configure'.
|
||||||
|
|
||||||
`--help'
|
`--help'
|
||||||
Print a summary of the options to `configure', and exit.
|
Print a summary of the options to `configure', and exit.
|
||||||
|
|
||||||
`--quiet'
|
`--quiet'
|
||||||
`--silent'
|
`--silent'
|
||||||
`-q'
|
`-q'
|
||||||
Do not print messages saying which checks are being made.
|
Do not print messages saying which checks are being made.
|
||||||
|
|
||||||
`--srcdir=DIR'
|
`--srcdir=DIR'
|
||||||
Look for the package's source code in directory DIR. Usually
|
Look for the package's source code in directory DIR. Usually
|
||||||
`configure' can determine that directory automatically.
|
`configure' can determine that directory automatically.
|
||||||
|
|
||||||
`--version'
|
`--version'
|
||||||
Print the version of Autoconf used to generate the `configure'
|
Print the version of Autoconf used to generate the `configure'
|
||||||
script, and exit.
|
script, and exit.
|
||||||
|
|
||||||
`configure' also accepts some other, not widely useful, options.
|
`configure' also accepts some other, not widely useful, options.
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -1,3 +1,3 @@
|
||||||
SUBDIRS = src
|
SUBDIRS = src
|
||||||
|
|
||||||
INCLUDES = -I$(top_srcdir)/. -I$(top_srcdir)/src
|
INCLUDES = -I$(top_srcdir)/. -I$(top_srcdir)/src
|
||||||
|
|
|
||||||
|
|
@ -588,3 +588,4 @@ uninstall-info: uninstall-info-recursive
|
||||||
# Tell versions [3.59,3.63) of GNU make to not export all variables.
|
# Tell versions [3.59,3.63) of GNU make to not export all variables.
|
||||||
# Otherwise a system limit (for SysV at least) may be exceeded.
|
# Otherwise a system limit (for SysV at least) may be exceeded.
|
||||||
.NOEXPORT:
|
.NOEXPORT:
|
||||||
|
|
||||||
|
|
|
||||||
3
NEWS
3
NEWS
|
|
@ -1 +1,2 @@
|
||||||
This file is always out of date. See https://sourceforge.net/projects/xml-copy-editor/ for project news.
|
This file is always out of date. See https://sourceforge.net/projects/xml-copy-editor/ for project news.
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -7242,3 +7242,4 @@ AC_SUBST([am__tar])
|
||||||
AC_SUBST([am__untar])
|
AC_SUBST([am__untar])
|
||||||
]) # _AM_PROG_TAR
|
]) # _AM_PROG_TAR
|
||||||
|
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -1409,3 +1409,4 @@ exit 1
|
||||||
# time-stamp-format: "%:y-%02m-%02d"
|
# time-stamp-format: "%:y-%02m-%02d"
|
||||||
# time-stamp-end: "'"
|
# time-stamp-end: "'"
|
||||||
# End:
|
# End:
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -1498,3 +1498,4 @@ exit 0
|
||||||
# time-stamp-format: "%:y-%02m-%02d"
|
# time-stamp-format: "%:y-%02m-%02d"
|
||||||
# time-stamp-end: "'"
|
# time-stamp-end: "'"
|
||||||
# End:
|
# End:
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue