kyonshi/grenzland-mud
1
0
Fork 1
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Removing Makefiles for old architectures or build mechanisms.

Browse Source 
We're in 2024.

The VMS, Amiga, OS/2 and Arc have fallen by the wayside, along with the
Borland C compiler and Watcom...
This commit is contained in:
welcor
2024-06-21 00:08:40 +02:00
parent 11d4693776
commit 8f958359e9
21 changed files with 299 additions and 3684 deletions
Download Patch File Download Diff File Expand all files Collapse all files

81
doc/README.AMIGA
View File

@@ -1,81 +0,0 @@
Compiling CircleMUD on the Amiga
Written by Damian Jurzysta <boing@amigascne.org>
Compiling CircleMUD on the Amiga is basically the same as compiling it using
UNIX. What you need is:
* AmiTCP, INet225R2 or any other TCP/IP stack working with ixnet.library.
You can get the limited unregistered version of Miami from
http://www.nordicglobal.com. An old demoversion of AmiTCP 4.0 can be found on
AmiNet (ftp://ftp.aminet.org/pub/aminet/comm/tcp/AmiTCP-demo-40.lha).
* An installed and fully functional Geek Gadgets programming environment with
Autoconf installed. I've managed to compile and run CircleMUD using the
971125, 980523 and 990529 snapshots using GCC 2.7.2 and EGCS 1.1b-1.2.
The latest EGCS is always the optimal choice.
This can be found at ftp://ftp.ninemoons.com/pub/geekgadgets.
Installing this is a bit tricky at first, I recommend reading the manual
first. It is located at http://www.ninemoons.com/GG/docs/GG_7.html. That
way you'll know what archives to download and install.
* 6 MB's of RAM, it might work with less but has not been tested.
You can find it at the local computer store. :)
* A 68020 CPU or better is required, I've not been able to compile it without
specifying the -m68020 flag, therefore it won't run on a 68000 or 68010 CPU.
A1500, A2500, A3000, A4000 and A1200 all come with factory-installed 68020-040
CPU's. If you own an unexpanded Amiga not listed above you'll need to expand
it.
Here is how you compile this baby:
1) Open up a shell.
2) CD to the circle30bplXX directory. (where 'XX' is the current patchlevel)
3) Type "sh configure".
4) CD to the src directory.
5) Edit the Makefile file and add -m68020 to MYFLAGS.
6) Edit the config.c file and replace "const char *LOGNAME = NULL;" with
"const char *LOGNAME = "log/syslog";". If you don't do this, logging
won't be working properly.
7) CD to the util directory and repeat step 5.
8) Due to a buggy/non-functional/missing implementation of HAS_RLIMIT in
ixemul.library/Geek Gadgets you need to edit sysdep.h and remove or comment
the definition of HAS_RLIMIT on line 324 saying "#define HAS_RLIMIT".
9) CD back to the src directory.
10) Type "make all".
If you want to optimize the binary executable, change MYFLAGS to correspond
with your current processor (-m68020, -m68030, -m68040 or -m68060) and FPU
(-m68881). The -m68060 option is not included in GCC 2.7.2, only in EGCS 1.1+.
Also add -O3 to MYFLAGS to activate maximum optimization and inlining. I'm not
sure -O3 is working with GCC 2.7.2, if you get compiler errors replace it with
-O2. Finally, remove -g and -O2 from CFLAGS to remove debugging information and
to avoid the above -O3 (or -O2 if you're using GCC 2.7.2) to collide with this
flag.
To run the server all you need to do is follow these five simple steps:
1) Make sure you have a TCP/IP stack running. You don't need to be connected to
the net, just leave it running.
2) Open up a shell.
3) Since the UNIX autorun kept crashing on my machine, I wrote my own autorun
script. If "sh autorun" isn't working for you, type "autorun.amiga".
4) If it says "file is not executable" when you try to run autorun.amiga, type
"protect autorun.amiga +es" and run it again.
5) To connect to it, use a telnet or MUD client and connect to localhost, port
4000. If you don't have one, use the one supplied with Geek Gadgets:
'telnet localhost 4000'. The first person to log in will be made an
implementor (level 34) with all powers.
You may want to read the README.UNIX file since most what is written in it also
complies to the Amiga Geek Gadgets environment.
If someone manages to compile it on a PowerPC processor, please contact me.
I don't own a PowerUP/G3/G4-board myself so I've not been able to test this.
If you have any questions or can't get it working, feel free to email me at
boing@amigascne.org.

87
doc/README.ARC
View File

@@ -1,87 +0,0 @@
Compiling CircleMUD under RiscOS
by Gareth Duncan (garethduncan@argonet.co.uk)
You will need:
The CircleMUD source code.
!GCC, !UnixLib, drlink and make available from Hensa.
Acorns sockets library available form the Acorn ftp site.
A copy of !FreeNet and !FreeTerm.
1) Firstly obtain a copy of !GCC, !UnixLib, drlink, make and Acorns
sockets library.
2) Place the directory Sockets from the sockets library inside
!UnixLib37.src.clib
3) Unpack the CircleMUD binary and start setting up the directory
structures in the src directory.
4) src
|
----------------------------------
| | | | | |
util act c h o conf
|
---------------
| | |
c h o
5) Place all the files in the correct directories according to their
name remembering to remove the directory information from the
filename.
e.g. ban/c goes in the directory c and is renamed to ban.
act/item/c goes in the directory act then c and is renamed to
item.
6) Set the type of any data files in the src directories to text.
7) Copy the acorn configure file (should be conf/h/arc) into the h
directory and rename it conf.
8) Create an obey file called !Compile in the src containing the
following lines
-- begin (don't include this line)
WimpSlot -min 10000K -max 10000K
dir <Obey$Dir>
make -r
-- end (don't include this line)
and set the wimpslot to as much memory as you can afford.
9) Place the make program in the src directory and rename the file
Makefile/arc to Makefile removing the old file already called
Makefile.
10) Unpack GCC and Unixlib placing them where you want and then
double click on them. Then run the !Compile file. Everything
should run okay. Make sure that drlink is placed inside GCC in the
bin directory. If you get any error messages check that the code
changes at the bottom of this file are present. If not alter the
code as instructed.
11) Place the module CallASWI from !UnixLib37.src.CallASWI in the bin
directory.
12) Now get a copy of the FreeNet internet stack or a recent version
of Acorns stack and FreeTerm. Make sure the FreeUser start up
script has the line
ifconfig lo0 inet 127.0.0.1 up
Then run the startup script, run FreeTerm and then open a task
window. Run the !Run file (which should be placed in the directory
above src) from the task window by typing in its file name and
then press return, the Mud should load (you should be able to just
shift drag the !Run file onto the window if you are using !Zap).
13) To log onto the mud type localhost and set the port to 4000 in
FreeTerm and then press connect
Please excuse the poor spelling and grammar in this and if you have
any trouble contact garethduncan@argonet.co.uk.
Bye.
-Gareth

66
doc/README.BORLAND
View File

@@ -1,66 +0,0 @@
Compiling CircleMUD
under Microsoft Windows 95 or Windows NT
using Borland C++
Written by Mundi King <kingmundi@yahoo.com>
Here are some instructions on compiling circlemud using Borland C++ 5.01.
These instructions will not work using Turbo C++, or the 4.0 versions of
Borland C++ as those two products were geared twoards DOS and Windows 3.xx.
It will most likely work with versions 5.00, 5.02, and 5.5 of the Borland
C++ compilers.
Boot up your Windows 95 machine.
Unzip your CircleMUD package.
Goto a DOS prompt, and change to the circle \src directory.
(Type) rename conf.h.win conf.h (Enter)
** BORLAND 5.5 **
If you are using Borland C++ 5.5, a couple of extra changes need to be
made at this time. First you have to make sure the bin directory of the
tools is in your path. You can add the following line to your autoexec.bat
to have it automatically added to your path or you can type it at a DOS
prompt:
path = %path%;c:\borland\bcc55\bin
(Type) make -fmakefile.bcc55 (Enter)
** BORLAND 5.1 **
(Type) make -fmakefile.bcc (Enter)
** End Version Specifics **
Something to note here is that these makefile
assume that you have installed Borland C++ 5.x
to the C: drive. If you have installed it to
another drive you will have to open up the correct
Makefile in a text editor and find and replace
all C:\ references to the drive letter it has
been installed to.
(Type) move circle.exe ..\ (Enter)
(Type) cd .. (Enter)
(Type) circle (Enter)
The game should start loading the zones and database. You will no longer be
able to type in this DOS box.
Click on START and then on RUN.
(Type) telnet localhost 4000 (Enter)
The first one to logon becomes the Implementor.
Also remember that you are using Windows95's
built-in telnet program which is very basic.
Pat yourself on the back.
---
Mundi King 1998-07-03
Updated for 5.5: 2000-06-28

70
doc/README.OS2
View File

@@ -1,70 +0,0 @@
Compiling CircleMUD
under OS/2 Warp Connect v3.0 or 2.1
by David Carver
To compile CircleMUD under OS/2, you must have the following:
All needed files can be found at the hobbes.nmsu.edu FTP site.
* OS/2 Warp Connect Version 3.0, or OS/2 Version 2.1 with TCP/IP installed.
You should have at least 8 megs of memory. (Circle runs quite well on an
8 meg machine).
* An HPFS formatted drive. CircleMUD needs to be uncompressed on an HPFS
drive because it uses long filenames.
* The EMX09b runtime and compilation systems. These are free and
can be downloaded by anonymous FTP at hobbes.nmsu.edu in os2/unix/emx09b
* The OS/2 port of GNU's GCC compiler. This can also be found at
hobbes.nmsu.edu in os2/unix/emx09b. Please make sure you have the most
recent version of the GCC compiler for OS/2, as files needed by CircleMUD
were not included in earlier versions of GCC for OS/2. The current version
is 2.7.0
* GNU's TAR and GZIP programs to decompress the necessary files. Again
these can be found at hobbes.nmsu.edu in os2/unix.
**** You only need this if you plan on getting some of the various
**** addons for Circle that others have coded.
* A MAKE program. Either the GNU Make, or IBM's NMAKE should work. You
can obtain the NMAKE from either IBM's Developers kit or from
hobbes.nmsu.edu in os2/16dev.
Installation:
*** IMPORTANT
***
*** You must have EMX and GCC installed and the directories in your
*** PATH and LIBPATH statements in your CONFIG.SYS. Please read the
*** EMX installation instructions included with that package for more
*** information on how to install both EMX and GCC.
Download the ZIP archive of Circle and use your favorite UNZip utility
to extract it.
After you have uncompressed the files, switch to the directory that has
the CircleMUD files in it, and then to the SRC subdirectory. Rename
the following files:
Rename 'conf.h.os2' to 'conf.h'.
Delete the old 'makefile', and rename 'makefile.os2' to 'makefile'.
To compile the MUD type the following at an OS/2 command line:
NMAKE /i
CircleMUD will be compiled and the executable will be put in your current
directory. Copy the CIRCLE.EXE file to the circle30\bin directory. Then
follow the CircleMUD instructions in README on how to start up the MUD.
NOTE: General questions about CircleMUD can be addressed to the author,
Jeremy Elson, at jelson@circlemud.org. However, all questions which
specifically deal with the OS/2 port of Circle should go to my address,
listed below.
David Carver
dcarver@cougar.colstate.cc.oh.us
dcarver@iwaynet.net

81
doc/README.VMS
View File

@@ -1,81 +0,0 @@
This is directions for compiling & linking CircleMUD for OpenVMS.
Additional documentation can be found at.
http://www.ourservers.net/openvms_ports/
I have personally tested this port on both VAX and Alpha with OpenVMS v7.0
and DEC C v7.0 and Multinet TCP/IP using UCX emulation.
To build this, you need the following:
.1) DEC C compiler. I have tested with DEC C v7.0 and can help out
with problems with earlier versions of DEC C. If you don't have
the DEC C compiler I suggest you get a copy through the OpenVMS
Hobbyist program at http://www.montagar.com/hobbyist.
.2) A TCP/IP stack for OpenVMS that supports UCX emulation. I have
personally only tested out Multinet v4.1B and Multinet v4.2.
If you are using a TCP/IP stack that doesn't support UCX
emulation I would suggest getting a copy of Multinet though the
OpenVMS hobbyist program at http://www.montagar.com/hobbyist.
.3) A copy of the CircleMUD distribution file.
This can be found at ftp://ftp.circlemud.org/3.x/
Now, you have everything, do the following...
.1) Unpack the CircleMUD file you got from "www.circlemud.org"
.2) Go to the SRC directory and locate the BUILD_CIRCLEMUD.COM file.
The BUILD_CIRCLEMUD.COM file accepts the following parameters.
P1 ALL Just Build "Everything".
CIRCLE Just Build [.BIN]CIRCLE.EXE.
UTILS Just Build The CircleMUD Utilities.
P2 DEBUG Build CircleMUD With Debugging Information.
NODEBUG Build CircleMUD Without Debugging Information.
The default is "ALL" and "NODEBUG".
The "BUILD_CIRCLEMUD.COM" script checks some filenames to make
sure that they are correct as some of them are unpacked different
between the TAR file distribution and the ZIP file distribution.
It also checks for "CONF.H" and if not found copies "CONF.H_VMS"
to "CONF.H" for you.
So if you just want to build "everything" without debugging
information you could use...
$ @BUILD_CIRCLEMUD ALL NODEBUG
OR
$ @BUILD_CIRCLEMUD
The EXE's will be placed in the CircleMUD BIN directory.
Now, define the logical CIRCLEMUD_BIN to point to the "BIN" directory of
the CircleMUD directory like this...
$ DEFINE/SYSTEM/EXEC CIRCLEMUD_BIN DISK$WORK:[CIRCLE30BPL16.BIN]
To run CircleMUD, just execute the "VMS_AUTORUN.COM" file in the CircleMUD
root directory.
To customize how CircleMUD runs, edit the "VMS_CIRCLEMUD.COM" file in the
BIN directory.
To customize CircleMUD features (like player killing etc) edit the "CONFIG.C"
file in the SRC directory.
To edit the CircleMUD login message, edit the GREETINGS.; file found in the
TEXT directory under the LIB directory.
For the CircleMUD utilities, execute the file VMS_MUD_UTILS.COM in the
BIN directory and it will create the VMS symbols for the utilities.
If you have any problems, questions, comments, feel free to e-mail me at
byer@mail.ourservers.net and I'll try my best to answer them all.

23
doc/README.WATCOM
View File

@@ -1,23 +0,0 @@
Compiling CircleMUD
under Microsoft Windows 95 or Windows NT
using Watcom v.11
The following information is from Joe Osburn <joeos19@idt.net>.
Circle apparently compiles under 95/NT using Watcom's compiler with
the following changes:
1- Copy conf.h.win to conf.h
2- Rename all the act.* files to other names; the IDE in Watcom apparently
doesn't like files that start with act.*
3- In Watcom make a new project that is a Windows 95 character mode
executable; add all of Circle's .c files to it.
4- Remove the line that says "#define chdir _chdir" from sysdep.h
If you have any further information, patches, or more detailed instructions,
please mail them to us at bugs@circlemud.org.