Bump version from 2.13 to 2.14.0.0 across the codebase

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Stephen Dennis 2026-03-07 22:10:38 -07:00
parent 5909c4744b
commit ebe374d8cc
40 changed files with 130 additions and 130 deletions

4
.gitignore vendored
View file

@ -39,8 +39,8 @@ mux/game/*.pem
mux/game/*.pfx
# Release/patch archives and reference directories
mux2.13/
mux2.13_*/
mux2.14/
mux2.14_*/
patches_src/
patches_bin/

View file

@ -28,9 +28,9 @@ This file provides guidance to Claude Code (claude.ai/code) when working with co
- Patch files for upgrading from previous version (.patch.gz)
- SHA256 checksums for all distribution files
- Generated files:
- `mux-2.13.0.x.unix.tar.gz` - Complete distribution
- `mux-2.13.0.x.unix.tar.bz2` - Same, in bzip2 format
- `mux-2.13.0.[x-1]-2.13.0.x.unix.patch.gz` - Patch from previous version
- `mux-2.14.0.x.unix.tar.gz` - Complete distribution
- `mux-2.14.0.x.unix.tar.bz2` - Same, in bzip2 format
- `mux-2.14.0.[x-1]-2.14.0.x.unix.patch.gz` - Patch from previous version
- Each file has a corresponding .sha256 checksum file
## Code Style Guidelines

View file

@ -9,16 +9,16 @@ set -e # Exit on error
set -o pipefail
# Version information
OLD_BUILD=8
OLD_VERSION="2.13.0.$OLD_BUILD"
NEW_BUILD=9
NEW_VERSION="2.13.0.$NEW_BUILD"
OLD_BUILD=0
OLD_VERSION="2.14.0.$OLD_BUILD"
NEW_BUILD=0
NEW_VERSION="2.14.0.$NEW_BUILD"
# Directory structure
CHANGES_DIR=mux
REFERENCE_DIR=mux2.13_$OLD_BUILD
DISTRO_DIR=mux2.13
NEW_DIR=mux2.13_$NEW_BUILD
REFERENCE_DIR=mux2.14_$OLD_BUILD
DISTRO_DIR=mux2.14
NEW_DIR=mux2.14_$NEW_BUILD
# Load file lists
patchable_files=$(cat unix/TOC.patchable)

View file

@ -9,16 +9,16 @@ set -e # Exit on error
set -o pipefail
# Version information
OLD_BUILD=8
OLD_VERSION="2.13.0.$OLD_BUILD"
NEW_BUILD=9
NEW_VERSION="2.13.0.$NEW_BUILD"
OLD_BUILD=0
OLD_VERSION="2.14.0.$OLD_BUILD"
NEW_BUILD=0
NEW_VERSION="2.14.0.$NEW_BUILD"
# Directory structure
CHANGES_DIR=mux
REFERENCE_DIR=mux2.13_$OLD_BUILD
DISTRO_DIR=mux2.13
NEW_DIR=mux2.13_$NEW_BUILD
REFERENCE_DIR=mux2.14_$OLD_BUILD
DISTRO_DIR=mux2.14
NEW_DIR=mux2.14_$NEW_BUILD
echo "Checking for required tools..."
if ! command -v xdelta3 &> /dev/null; then

View file

@ -1,9 +1,9 @@
---
title: TinyMUX 2.13 ALPHA
title: TinyMUX 2.14 ALPHA
date: March 2026
author:
- Brazil
---
The alpha period for TinyMUX 2.13 has concluded. All known issues from
The alpha period for TinyMUX 2.14 has concluded. All known issues from
that period have been resolved, including non-blocking SSL support.

View file

@ -1,11 +1,11 @@
---
title: TinyMUX 2.13 BETA
title: TinyMUX 2.14 BETA
date: March 2026
author:
- Brazil
---
The beta period for TinyMUX 2.13 has concluded.
The beta period for TinyMUX 2.14 has concluded.
- Make backups. Frequent and complete. It is important.
- Store your backups off site. This was always prudent anyway.

View file

@ -1,5 +1,5 @@
---
title: TinyMUX 2.13 CHANGES
title: TinyMUX 2.14 CHANGES
date: March 2026
author:
- Brazil

View file

@ -71,7 +71,7 @@ library or tool is missing.
- cd to the game directory. `cd ../game`
- Make your configuration file, as described in `docs/CONFIGURATION.md`
- Type `./Startmux`. TinyMUX 2.13 automatically creates a minimal DB
- Type `./Startmux`. TinyMUX 2.14 automatically creates a minimal DB
if one does not exist in the `game/data` directory.
- Log into the game as player wizard `connect wizard potrzebie` and
shut it down again.
@ -79,7 +79,7 @@ library or tool is missing.
5. Edit the .txt files in `game/text` to your liking. In particular,
`connect.txt` and `motd.txt`.
6. Start TinyMUX 2.13 by running `./Startmux` again.
6. Start TinyMUX 2.14 by running `./Startmux` again.
7. `@ccreate` a channel named `Public`, and a channel named `Guests`
from within the TinyMUX. Created players will automatically be
@ -146,5 +146,5 @@ upgrade.
accordingly, BEFORE you restart the game, or else ALL `@mail` older
than the default value of 14 days will be deleted.
5. Start TinyMUX 2.13 by running `./Startmux`.
5. Start TinyMUX 2.14 by running `./Startmux`.

View file

@ -71,7 +71,7 @@ to export a flatfile and `db_load` to import it on the other end.
# On Making Backups:
TinyMUX 2.13 includes a `Backup` script in the `game` directory. It uses
TinyMUX 2.14 includes a `Backup` script in the `game` directory. It uses
the SQLite `.backup` command to create a timestamped, compressed copy of
the database:

View file

@ -4,7 +4,7 @@ date: March 2026
title: README (Unix)
---
Congratulations and welcome to the `README.md` file for TinyMUX 2.13. That
Congratulations and welcome to the `README.md` file for TinyMUX 2.14. That
you have chosen to actually read the file is a sign of bravery equal to
that of Beowulf facing Grendel or anyone who has ever faced the garden
variety lumbering behemoth.
@ -21,7 +21,7 @@ because we want you to succeed, we are happy to provide a file that
will, in our sincerest hopes, provide you with enough information to
make that possible. If not, it should be at least an entertaining read.
The TinyMUX 2.13 `README` and supplemental documentation has been divided
The TinyMUX 2.14 `README` and supplemental documentation has been divided
into multiple files. For discussion and instructions on how to do
various things associated with the care and feeding of your TinyMUX,
please refer to the following files:
@ -30,9 +30,9 @@ please refer to the following files:
`README.md` General information on the distribution, platforms it has been shown to run under out of the box, and how to report bugs.
`CHANGES.md` New features, commands, and bug fixes.
`INSTALL.md` How to compile your game, step-by-step.
`NOTES.md` All kinds of tidbits made much easier to find. Known compiling issues and known fixes are found here. Known OSes that TinyMUX 2.13 will run on and compiling issues. Has basic conversion information.
`NOTES.md` All kinds of tidbits made much easier to find. Known compiling issues and known fixes are found here. Known OSes that TinyMUX 2.14 will run on and compiling issues. Has basic conversion information.
`UPGRADING.md` Step-by-step guide for upgrading from earlier TinyMUX versions, including the flatfile-to-SQLite migration.
`docs/BACKUPS.md` A file about the TinyMUX 2.13 Backup script.
`docs/BACKUPS.md` A file about the TinyMUX 2.14 Backup script.
`docs/CONFIGURATION.md` How to set up your TinyMUX, including an explanation of the common configuration items and how to customize your `GAMENAME`.
`docs/CREDITS.md` The people who helped make this server possible.
`docs/GUESTS.md` How the current guest implementation works and how to set it up.
@ -41,7 +41,7 @@ please refer to the following files:
# General Information:
TinyMUX 2.13 is written in a mix of C and C++ and is currently being
TinyMUX 2.14 is written in a mix of C and C++ and is currently being
developed on Windows, Debian, and FreeBSD. It is a continuation of the
TinyMUX 1.x flavor of MUSH servers.
@ -92,7 +92,7 @@ formalized. Sometimes, due to lack of available time, it is ad-hoc.
# Environment:
TinyMUX 2.13 should run on most Unixes with BSD-style sockets and a C++
TinyMUX 2.14 should run on most Unixes with BSD-style sockets and a C++
compiler that groks function prototypes. It is 64-bit clean code
supporting both IPv4 and IPv6.

View file

@ -1,5 +1,5 @@
---
title: TinyMUX 2.13 SGP Minimal DB
title: TinyMUX 2.14 SGP Minimal DB
date: March 2026
author:
- Brazil

View file

@ -4,7 +4,7 @@ date: March 2026
title: SQL
---
TinyMUX 2.13 supports both asynchronous and synchronous SQL. The
TinyMUX 2.14 supports both asynchronous and synchronous SQL. The
synchronous/in-line support is similar to that of PennMUSH and TinyMUSH,
namely the `sql()` function. The asynchronous support is unique to TinyMUX
at this time and is the recommended method for SQL access.

View file

@ -4,7 +4,7 @@ date: March 2026
title: SSL
---
SSL is always enabled in TinyMUX 2.13. OpenSSL is a required dependency.
SSL is always enabled in TinyMUX 2.14. OpenSSL is a required dependency.
1. Once the game has been compiled you will need to create an SSL
certificate. You can create a self-signed certificate using the
@ -50,7 +50,7 @@ SSL is always enabled in TinyMUX 2.13. OpenSSL is a required dependency.
If you do not see this line, look for SSL error messages in the log.
A likely cause is an improper certificate passphrase.
If TinyMUX 2.13 cannot initialize the SSL engine, the game will still
If TinyMUX 2.14 cannot initialize the SSL engine, the game will still
run but the SSL ports will not be opened and the TLS option will be
disabled.

View file

@ -4,15 +4,15 @@ date: March 2026
title: UPGRADING
---
# Upgrading to TinyMUX 2.13
# Upgrading to TinyMUX 2.14
TinyMUX 2.13 replaces the flatfile and CHashFile (`.dir`/`.pag`) storage
TinyMUX 2.14 replaces the flatfile and CHashFile (`.dir`/`.pag`) storage
with a single SQLite database. This guide walks through upgrading from
earlier TinyMUX versions.
## Compatible Flatfile Formats
TinyMUX 2.13 can read flatfiles from:
TinyMUX 2.14 can read flatfiles from:
> TinyMUX 2.0, 2.1, 2.2, 2.3, 2.4, 2.6, 2.7, 2.9, 2.10, 2.12
@ -89,20 +89,20 @@ you have a structure file and need to re-export with `db_unload` (or
Keep `comsys.db` and `mail.db` from the old `game/data` directory as-is.
## Step 3 -- Build TinyMUX 2.13
## Step 3 -- Build TinyMUX 2.14
TinyMUX 2.13 untars into its own directory, so your old installation is
TinyMUX 2.14 untars into its own directory, so your old installation is
not disturbed.
```
tar xzf mux-2.13.0.x.unix.tar.gz
tar xzf mux-2.14.0.x.unix.tar.gz
cd mux/src
./configure
make
make install
```
The `make install` step is new in 2.13 -- it creates symlinks in `game/bin/`
The `make install` step is new in 2.14 -- it creates symlinks in `game/bin/`
that the startup scripts expect.
Optional `configure` flags:
@ -231,7 +231,7 @@ Connect as `Wizard` and verify:
## Ongoing Differences
Once running on 2.13, the day-to-day experience is mostly the same with
Once running on 2.14, the day-to-day experience is mostly the same with
a few changes:
- **`@dump`** performs a WAL checkpoint (fast, no fork). It does not write

View file

@ -64,7 +64,7 @@ Sometimes, the differences are minor, sometimes these differences are major.
Omega can upgrade PennMUSH from 'old' to 'new' style flatfiles.
Omega can upgrade or downgrade between TinyMUX flatfiles from TinyMUX 2.0
through TinyMUX 2.13. It may also be able to accept TinyMUX 1.6, but
through TinyMUX 2.14. It may also be able to accept TinyMUX 1.6, but
flatfiles from that era were more varied in the flatfile options. Your 1.6
flatfile may use options which Omega doesn't expect. It is best to run it
through TinyMUX 2.0 first.

View file

@ -14,7 +14,7 @@ occur and entire games have disappeared forever because of it.
# Making a Backup
TinyMUX 2.13 stores all game data (objects, attributes, comsys, and mail)
TinyMUX 2.14 stores all game data (objects, attributes, comsys, and mail)
in a single SQLite database file. The included `Backup` script, located in
the `game/` directory, uses the SQLite `.backup` command to create a
timestamped, compressed copy of the database.

View file

@ -4,7 +4,7 @@ date: March 2026
title: CONFIGURATION
---
TinyMUX 2.13 gets the information it needs to operate the game (aside from
TinyMUX 2.14 gets the information it needs to operate the game (aside from
the database itself) from a configuration file that is read in at startup.
The configuration file contains various parameters, such as what port to
listen for connects, and many other things.
@ -143,7 +143,7 @@ forbid_site 194.205.0.0 255.255.0.0
# Existing users may connect, newbies cannot.
register_site 137.120.19.0 255.255.255.0
register_site 152.0.0.0 255.0.0.0
register_site 62.136.0.0 255.255.0.0
register_site 62.146.0.0 255.255.0.0
register_site 195.92.0.0 255.255.0.0
register_site 195.166.0.0 255.255.0.0
```

View file

@ -4,7 +4,7 @@ date: March 2026
title: CREDITS
---
TinyMUX 2.13 is maintained by Stephen Dennis (Brazil@BrazilMUX) and would not
TinyMUX 2.14 is maintained by Stephen Dennis (Brazil@BrazilMUX) and would not
exist without the generous contributions of many individuals. Ideas for
features, occasionally code, documentation, project support, bug hunting,
came from many places, including TinyMUSH, ChaoticMUX, RhostMUSH, and

View file

@ -4,9 +4,9 @@ date: March 2026
title: DISTRIBUTIONS
---
# Where You Can Get TinyMUX 2.13
# Where You Can Get TinyMUX 2.14
TinyMUX 2.13 is developed by Stephen Dennis (brazilofmux@gmail.com) and a
TinyMUX 2.14 is developed by Stephen Dennis (brazilofmux@gmail.com) and a
small group of enthusiastic volunteers. The server is simultaneously
developed on Windows and Unix platforms. For the latest version, updates,
and news, please look at any of the project websites:
@ -41,7 +41,7 @@ Release cycle history:
| 2008--2009 | 2.9 |
| 2010--2011 | 2.10 |
| 2012--2019 | 2.12 |
| 2020-- | 2.13 |
| 2020-- | 2.14 |
Typically, development for each release cycle begins in January. After twelve
months, it will usually enter a beta period and stay there for three or four

View file

@ -29,7 +29,7 @@ The number of unique attribute names is limited to the maximum value of an
# Attributes per Object
TinyMUX 2.13 stores attributes in SQLite. The number of attributes per
TinyMUX 2.14 stores attributes in SQLite. The number of attributes per
object is not subject to the legacy 8000-byte A_LIST encoding limit.
The practical limit is determined by available disk space and memory.

View file

@ -4,7 +4,7 @@ date: March 2026
title: PATCHES
---
# A Word About Patches for TinyMUX 2.13
# A Word About Patches for TinyMUX 2.14
Changes are distributed in the form of patches, and these occur
most-frequently during the Alpha and Beta periods of the server's
@ -46,28 +46,28 @@ but if something goes wrong and you didn't, you won't be real happy.
1. Download the patch file to your local shell account somewhere. The
location is not critical.
The patch file `mux-2.13.0.1-2.13.0.2.unix.patch.gz` will patch from
version 2.13.0.1 to version 2.13.0.2. This patch file is compressed
The patch file `mux-2.14.0.1-2.14.0.2.unix.patch.gz` will patch from
version 2.14.0.1 to version 2.14.0.2. This patch file is compressed
using gzip.
2. Optionally, you can decompress the patch files with `gzip -d` like so:
gzip -d mux-2.13.0.1-2.13.0.2.unix.patch.gz
gzip -d mux-2.14.0.1-2.14.0.2.unix.patch.gz
This will change the filename to `mux-2.13.0.1-2.13.0.2.unix.patch`.
This will change the filename to `mux-2.14.0.1-2.14.0.2.unix.patch`.
3. Change to your game's top-most directory. For example:
cd mux2.13
cd mux2.14
4. Apply the patch as follows:
zcat < ../mux-2.13.0.1-2.13.0.2.unix.patch.gz | patch -p0
zcat < ../mux-2.14.0.1-2.14.0.2.unix.patch.gz | patch -p0
Or, if you optionally decompressed the patch as described in step 2,
apply the patch as follows:
patch -p0 < ../mux-2.13.0.1-2.13.0.2.unix.patch
patch -p0 < ../mux-2.14.0.1-2.14.0.2.unix.patch
From here, you will usually get to watch a lot of output fly by as the
`patch` utility modifies the files to be updated. You might occasionally
@ -83,6 +83,6 @@ server as usual.
# If You Have Problems
If the patch fails and you were applying it to a standard beta or release
version of TinyMUX 2.13, then collect the error messages and report it to
version of TinyMUX 2.14, then collect the error messages and report it to
`brazilofmux@gmail.com` following the bug reporting procedures in
`README.md`.

View file

@ -6373,7 +6373,7 @@ CLONE()
Topic: CREDITS
TinyMUX 2.13 is based on TinyMUX 2.12. It is currently maintained by
TinyMUX 2.14 is based on TinyMUX 2.12. It is currently maintained by
Stephen Dennis (AKA Brazil). There is a more complete list of credits
in the README files for the server itself.

View file

@ -1,4 +1,4 @@
TinyMUX 2.13: README (Win32/64-based)
TinyMUX 2.14: README (Win32/64-based)
Last Update: July 2012
~~~~~~~~~~~~~~~~~~~~~~
@ -35,7 +35,7 @@ named incorrectly. Use version 2.50 of PKZip or use WinZip.
Regarding tar/gzip on Win32, I'm using the Cygwin version of these tools.
You can use Cygwin tools to unpack the Win32 distribution. However, as
mentioned above, you should not be using the Win32 distribution if you want
to use Cygwin to compile TinyMUX 2.13.
to use Cygwin to compile TinyMUX 2.14.
Regarding JAR from ARJ Software, this archiving tool produces the smallest
files. It's available via http://www.arjsoftware.com/jar.htm.
@ -49,21 +49,21 @@ To use a binary distribution:
following lines (depending on which archiving program you have chosen to
use).
jar32 x mux-2.13.0.1.win32.bin.j
tar xzf mux-2.13.0.1.win32.bin.tar.gz
pkzip -extract -directories mux-2.13.0.1.win32.bin.zip
jar32 x mux-2.14.0.1.win32.bin.j
tar xzf mux-2.14.0.1.win32.bin.tar.gz
pkzip -extract -directories mux-2.14.0.1.win32.bin.zip
-or-
Unpack the mux-2.13.0.1.win32.bin.zip using WinZip.
Unpack the mux-2.14.0.1.win32.bin.zip using WinZip.
2. The pre-built binaries for 32-bit are already placed in mux2.13/game/bin and
ready to go. 64-bit binaries are provided in mux2.13/game/bin/win64, but to
2. The pre-built binaries for 32-bit are already placed in mux2.14/game/bin and
ready to go. 64-bit binaries are provided in mux2.14/game/bin/win64, but to
use those, you need to be using a 64-bit version of Windows, and you need
to copy them up one directory level into mux2.13/game/bin. 64-bit versions
to copy them up one directory level into mux2.14/game/bin. 64-bit versions
of Windows can use either.
3. cd mux2.13/game
3. cd mux2.14/game
4. Possibly edit netmux.conf and mux.config to tweak the configuration.
@ -83,25 +83,25 @@ To use a source distribution:
following lines (depending on which archiving program you have chosen to
use).
jar32 x mux-2.13.0.1.win32.src.j
tar xzf mux-2.13.0.1.win32.src.tar.gz
pkzip -extract -directories mux-2.13.0.1.win32.src.zip
jar32 x mux-2.14.0.1.win32.src.j
tar xzf mux-2.14.0.1.win32.src.tar.gz
pkzip -extract -directories mux-2.14.0.1.win32.src.zip
-or-
Unpack the mux-2.13.0.1.win32.src.zip using WinZip.
Unpack the mux-2.14.0.1.win32.src.zip using WinZip.
2. Start Visual C++ and open the workspace file (mux2.13/src/netmux.dsw). Your
2. Start Visual C++ and open the workspace file (mux2.14/src/netmux.dsw). Your
version of Visual Studio may want to convert this workspace file into a
'solution' file and also convert all the project files. Let it do this,
and then remember to work with the solution file thereafter.
3. Within Visual C++, do a batch build in order to produce netmux.exe. The
non-debug version will be placed in mux2.13/src/bin_release and must be
copied over to mux2.13/game/bin. It will also build a libmux.dll file which
must also be copied over to mux2.13/game/bin. It will also build several
modules under mux2.13/src/modules/bin_release. If you intend to use
these, they must also be copied into the mux2.13/game/bin directory.
non-debug version will be placed in mux2.14/src/bin_release and must be
copied over to mux2.14/game/bin. It will also build a libmux.dll file which
must also be copied over to mux2.14/game/bin. It will also build several
modules under mux2.14/src/modules/bin_release. If you intend to use
these, they must also be copied into the mux2.14/game/bin directory.
4. Start the server with the following:

View file

@ -1,4 +1,4 @@
# Makefile.am for TinyMUX 2.13
# Makefile.am for TinyMUX 2.14
SUBDIRS = tools ganl . modules

View file

@ -14,7 +14,7 @@
@SET_MAKE@
# Makefile.am for TinyMUX 2.13
# Makefile.am for TinyMUX 2.14
VPATH = @srcdir@

View file

@ -16,7 +16,7 @@ extern char szBuildDate[];
#define MUX_BUILD_DATE szBuildDate
#endif
#define MUX_VERSION "2.13.0.9" // Version number
#define MUX_VERSION "2.14.0.0" // Version number
#define MUX_RELEASE_DATE "2026-MAR-06" // Source release date
// Define if this release is qualified as ALPHA or BETA.

View file

@ -378,7 +378,7 @@
#define PACKAGE_NAME "TinyMUX"
/* Define to the full name and version of this package. */
#define PACKAGE_STRING "TinyMUX 2.13"
#define PACKAGE_STRING "TinyMUX 2.14"
/* Define to the one symbol short name of this package. */
#define PACKAGE_TARNAME "tinymux"
@ -387,7 +387,7 @@
#define PACKAGE_URL ""
/* Define to the version of this package. */
#define PACKAGE_VERSION "2.13"
#define PACKAGE_VERSION "2.14"
/* Define if calling signal with SIGCHLD when handling SIGCHLD blows chow. */
/* #undef SIGNAL_SIGCHLD_BRAINDAMAGE */

22
mux/src/configure vendored
View file

@ -1,6 +1,6 @@
#! /bin/sh
# Guess values for system-dependent variables and create Makefiles.
# Generated by GNU Autoconf 2.71 for TinyMUX 2.13.
# Generated by GNU Autoconf 2.71 for TinyMUX 2.14.
#
# Report bugs to <tinymux@googlegroups.com>.
#
@ -611,8 +611,8 @@ MAKEFLAGS=
# Identity of this package.
PACKAGE_NAME='TinyMUX'
PACKAGE_TARNAME='tinymux'
PACKAGE_VERSION='2.13'
PACKAGE_STRING='TinyMUX 2.13'
PACKAGE_VERSION='2.14'
PACKAGE_STRING='TinyMUX 2.14'
PACKAGE_BUGREPORT='tinymux@googlegroups.com'
PACKAGE_URL=''
@ -1368,7 +1368,7 @@ if test "$ac_init_help" = "long"; then
# Omit some internal or obsolete options to make the list less imposing.
# This message is too long to be a string in the A/UX 3.1 sh.
cat <<_ACEOF
\`configure' configures TinyMUX 2.13 to adapt to many kinds of systems.
\`configure' configures TinyMUX 2.14 to adapt to many kinds of systems.
Usage: $0 [OPTION]... [VAR=VALUE]...
@ -1439,7 +1439,7 @@ fi
if test -n "$ac_init_help"; then
case $ac_init_help in
short | recursive ) echo "Configuration of TinyMUX 2.13:";;
short | recursive ) echo "Configuration of TinyMUX 2.14:";;
esac
cat <<\_ACEOF
@ -1556,7 +1556,7 @@ fi
test -n "$ac_init_help" && exit $ac_status
if $ac_init_version; then
cat <<\_ACEOF
TinyMUX configure 2.13
TinyMUX configure 2.14
generated by GNU Autoconf 2.71
Copyright (C) 2021 Free Software Foundation, Inc.
@ -2290,7 +2290,7 @@ cat >config.log <<_ACEOF
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
It was created by TinyMUX $as_me 2.13, which was
It was created by TinyMUX $as_me 2.14, which was
generated by GNU Autoconf 2.71. Invocation command line was
$ $0$ac_configure_args_raw
@ -3784,7 +3784,7 @@ fi
# Define the identity of the package.
PACKAGE='tinymux'
VERSION='2.13'
VERSION='2.14'
printf "%s\n" "#define PACKAGE \"$PACKAGE\"" >>confdefs.h
@ -4302,7 +4302,7 @@ printf "%s\n" "$ac_try_echo"; } >&5
printf "%s\n" "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
test $ac_status = 0; }
then :
# Autoconf-2.13 could set the ac_cv_exeext variable to `no'.
# Autoconf-2.14 could set the ac_cv_exeext variable to `no'.
# So ignore a value of `no', otherwise this would lead to `EXEEXT = no'
# in a Makefile. We should not override ac_cv_exeext if it was cached,
# so that the user can short-circuit this test for compilers unknown to
@ -11598,7 +11598,7 @@ cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1
# report actual input values of CONFIG_FILES etc. instead of their
# values after options handling.
ac_log="
This file was extended by TinyMUX $as_me 2.13, which was
This file was extended by TinyMUX $as_me 2.14, which was
generated by GNU Autoconf 2.71. Invocation command line was
CONFIG_FILES = $CONFIG_FILES
@ -11666,7 +11666,7 @@ ac_cs_config_escaped=`printf "%s\n" "$ac_cs_config" | sed "s/^ //; s/'/'\\\\\\\\
cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
ac_cs_config='$ac_cs_config_escaped'
ac_cs_version="\\
TinyMUX config.status 2.13
TinyMUX config.status 2.14
configured by $0, generated by GNU Autoconf 2.71,
with options \\"\$ac_cs_config\\"

View file

@ -1,7 +1,7 @@
dnl Process this file with autoconf to produce a configure script.
AC_PREREQ([2.71])
AC_INIT([TinyMUX],[2.13],[tinymux@googlegroups.com])
AC_INIT([TinyMUX],[2.14],[tinymux@googlegroups.com])
AC_CONFIG_SRCDIR([game.cpp])
AC_CONFIG_HEADERS([autoconf.h] [modules/autoconf.h] [tools/autoconf.h])
AM_INIT_AUTOMAKE([foreign subdir-objects])

View file

@ -5,7 +5,7 @@
/* -*-C-*- */
/*
* MUX Source Code (version 2.0 through 2.13).
* MUX Source Code (version 2.0 through 2.14).
* Copyright (C) 1999-2004 by Solid Vertical Domains, Ltd.
* Copyright (C) 2005-2020 Stephen Dennis
*
@ -50,7 +50,7 @@
* MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
*
*
* TinyMUX 2.13 Copyright: The Artistic License
* TinyMUX 2.14 Copyright: The Artistic License
*
* Preamble
*

View file

@ -1,4 +1,4 @@
# Makefile.am for TinyMUX 2.13 modules
# Makefile.am for TinyMUX 2.14 modules
# Shared build flags
AM_CPPFLAGS = -I$(top_srcdir)

View file

@ -14,7 +14,7 @@
@SET_MAKE@
# Makefile.am for TinyMUX 2.13 modules
# Makefile.am for TinyMUX 2.14 modules
VPATH = @srcdir@
am__is_gnu_make = { \
if test -z '$(MAKELEVEL)'; then \

View file

@ -62,7 +62,7 @@
#define PACKAGE_NAME "TinyMUX"
/* Define to the full name and version of this package. */
#define PACKAGE_STRING "TinyMUX 2.13"
#define PACKAGE_STRING "TinyMUX 2.14"
/* Define to the one symbol short name of this package. */
#define PACKAGE_TARNAME "tinymux"
@ -71,7 +71,7 @@
#define PACKAGE_URL ""
/* Define to the version of this package. */
#define PACKAGE_VERSION "2.13"
#define PACKAGE_VERSION "2.14"
/* Define to 1 if you have the ANSI C header files. */
#define STDC_HEADERS 1

View file

@ -100,7 +100,7 @@
<Link>
<AdditionalDependencies>ganl.lib;wsock32.lib;ws2_32.lib;secur32.lib;crypt32.lib;ncrypt.lib;pcre2-8.lib;%(AdditionalDependencies)</AdditionalDependencies>
<AdditionalLibraryDirectories>.\bin_release;%(AdditionalLibraryDirectories)</AdditionalLibraryDirectories>
<Version>2.13</Version>
<Version>2.14</Version>
<SubSystem>Console</SubSystem>
<RandomizedBaseAddress>true</RandomizedBaseAddress>
<DataExecutionPrevention />

View file

@ -1,4 +1,4 @@
# Makefile.am for TinyMUX 2.13 tools
# Makefile.am for TinyMUX 2.14 tools
# Build the announce utility
bin_PROGRAMS = announce

View file

@ -14,7 +14,7 @@
@SET_MAKE@
# Makefile.am for TinyMUX 2.13 tools
# Makefile.am for TinyMUX 2.14 tools
VPATH = @srcdir@
am__is_gnu_make = { \

View file

@ -44,10 +44,10 @@
#define PACKAGE_BUGREPORT ""
/* Define to the full name of this package. */
#define PACKAGE_NAME "Tinymux-UTF 2.13"
#define PACKAGE_NAME "Tinymux-UTF 2.14"
/* Define to the full name and version of this package. */
#define PACKAGE_STRING "Tinymux-UTF 2.13 tinymux@googlegroups.com"
#define PACKAGE_STRING "Tinymux-UTF 2.14 tinymux@googlegroups.com"
/* Define to the one symbol short name of this package. */
#define PACKAGE_TARNAME "tinymux-utf-2-13"

View file

@ -20,8 +20,8 @@
#define HAVE__BOOL 1
#define STDC_HEADERS 1
#define PACKAGE_NAME "Tinymux-UTF 2.13"
#define PACKAGE_STRING "Tinymux-UTF 2.13"
#define PACKAGE_TARNAME "tinymux-utf-2-13"
#define PACKAGE_NAME "Tinymux-UTF 2.14"
#define PACKAGE_STRING "Tinymux-UTF 2.14"
#define PACKAGE_TARNAME "tinymux-utf-2-14"
#define PACKAGE_URL ""
#define PACKAGE_VERSION "2.13"
#define PACKAGE_VERSION "2.14"

24
utf/configure vendored
View file

@ -1,6 +1,6 @@
#! /bin/sh
# Guess values for system-dependent variables and create Makefiles.
# Generated by GNU Autoconf 2.69 for Tinymux-UTF 2.13 tinymux@googlegroups.com.
# Generated by GNU Autoconf 2.69 for Tinymux-UTF 2.14 tinymux@googlegroups.com.
#
#
# Copyright (C) 1992-1996, 1998-2012 Free Software Foundation, Inc.
@ -575,10 +575,10 @@ MFLAGS=
MAKEFLAGS=
# Identity of this package.
PACKAGE_NAME='Tinymux-UTF 2.13'
PACKAGE_TARNAME='tinymux-utf-2-13'
PACKAGE_NAME='Tinymux-UTF 2.14'
PACKAGE_TARNAME='tinymux-utf-2-14'
PACKAGE_VERSION='tinymux@googlegroups.com'
PACKAGE_STRING='Tinymux-UTF 2.13 tinymux@googlegroups.com'
PACKAGE_STRING='Tinymux-UTF 2.14 tinymux@googlegroups.com'
PACKAGE_BUGREPORT=''
PACKAGE_URL=''
@ -1240,7 +1240,7 @@ if test "$ac_init_help" = "long"; then
# Omit some internal or obsolete options to make the list less imposing.
# This message is too long to be a string in the A/UX 3.1 sh.
cat <<_ACEOF
\`configure' configures Tinymux-UTF 2.13 tinymux@googlegroups.com to adapt to many kinds of systems.
\`configure' configures Tinymux-UTF 2.14 tinymux@googlegroups.com to adapt to many kinds of systems.
Usage: $0 [OPTION]... [VAR=VALUE]...
@ -1290,7 +1290,7 @@ Fine tuning of the installation directories:
--localedir=DIR locale-dependent data [DATAROOTDIR/locale]
--mandir=DIR man documentation [DATAROOTDIR/man]
--docdir=DIR documentation root
[DATAROOTDIR/doc/tinymux-utf-2-13]
[DATAROOTDIR/doc/tinymux-utf-2-14]
--htmldir=DIR html documentation [DOCDIR]
--dvidir=DIR dvi documentation [DOCDIR]
--pdfdir=DIR pdf documentation [DOCDIR]
@ -1303,7 +1303,7 @@ fi
if test -n "$ac_init_help"; then
case $ac_init_help in
short | recursive ) echo "Configuration of Tinymux-UTF 2.13 tinymux@googlegroups.com:";;
short | recursive ) echo "Configuration of Tinymux-UTF 2.14 tinymux@googlegroups.com:";;
esac
cat <<\_ACEOF
@ -1385,7 +1385,7 @@ fi
test -n "$ac_init_help" && exit $ac_status
if $ac_init_version; then
cat <<\_ACEOF
Tinymux-UTF 2.13 configure tinymux@googlegroups.com
Tinymux-UTF 2.14 configure tinymux@googlegroups.com
generated by GNU Autoconf 2.69
Copyright (C) 2012 Free Software Foundation, Inc.
@ -1842,7 +1842,7 @@ cat >config.log <<_ACEOF
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
It was created by Tinymux-UTF 2.13 $as_me tinymux@googlegroups.com, which was
It was created by Tinymux-UTF 2.14 $as_me tinymux@googlegroups.com, which was
generated by GNU Autoconf 2.69. Invocation command line was
$ $0 $@
@ -2375,7 +2375,7 @@ $as_echo "$ac_try_echo"; } >&5
ac_status=$?
$as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
test $ac_status = 0; }; then :
# Autoconf-2.13 could set the ac_cv_exeext variable to `no'.
# Autoconf-2.14 could set the ac_cv_exeext variable to `no'.
# So ignore a value of `no', otherwise this would lead to `EXEEXT = no'
# in a Makefile. We should not override ac_cv_exeext if it was cached,
# so that the user can short-circuit this test for compilers unknown to
@ -4363,7 +4363,7 @@ cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1
# report actual input values of CONFIG_FILES etc. instead of their
# values after options handling.
ac_log="
This file was extended by Tinymux-UTF 2.13 $as_me tinymux@googlegroups.com, which was
This file was extended by Tinymux-UTF 2.14 $as_me tinymux@googlegroups.com, which was
generated by GNU Autoconf 2.69. Invocation command line was
CONFIG_FILES = $CONFIG_FILES
@ -4425,7 +4425,7 @@ _ACEOF
cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
ac_cs_config="`$as_echo "$ac_configure_args" | sed 's/^ //; s/[\\""\`\$]/\\\\&/g'`"
ac_cs_version="\\
Tinymux-UTF 2.13 config.status tinymux@googlegroups.com
Tinymux-UTF 2.14 config.status tinymux@googlegroups.com
configured by $0, generated by GNU Autoconf 2.69,
with options \\"\$ac_cs_config\\"

View file

@ -1,7 +1,7 @@
dnl Process this file with autoconf to produce a configure script.
AC_PREREQ([2.69])
AC_INIT([Tinymux-UTF 2.13],[tinymux@googlegroups.com])
AC_INIT([Tinymux-UTF 2.14],[tinymux@googlegroups.com])
AC_CONFIG_SRCDIR([ConvertUTF.cpp])
AC_CONFIG_HEADERS([autoconf.h])