-
Type './configure' from the
eggdrop directory. That script will determine how your system is
set up, and figure out how to compile eggdrop. It will also try to
find Tcl, which is required to compile.
-
Type 'make' from the eggdrop
directory. Or to force a statically linked module bot type 'make
static'. Otherwise the Makefile will determin which type of bot your
system will support. Dynamic isalways the better way to go if possible.
There're also the options debug and sdebug (static-debug) which will give
more detailed output on (a highly unlikely :) crash. This might help the
devteam to track down the crash and fix the bug. Debug and sdebug will
take a little longer to compile and will enlarge the binary a bit, but
it's worth if you want to support eggdrop development.
-
Eggdrop must be installed in
a directory somewhere. This is accomplished by entering the unix
command:
make install DEST=<directory>
example make install DEST=/home/egguser/eggdrop
(note you must use full
path for every file to be correctly installed)
[The following is performed
from the directory installed above]
-
Copy the file 'eggdrop.conf.dist'
to a new file, usually the same name as the bot that will use it, e.g.
"LamestBot".
-
Edit your config file LamestBot
completely.
-
Start the bot with the "-m"
option to create a user file, ie 'eggdrop -m LamestBot'.
-
When starting the bot in the
future, drop the "-m". If you have edited your bot script correctly,
you can type:
chmod u+x <my-bot-script-name>
e.g.
chmod u+x LamestBot
and from then on, you will
be able to run your bot directly from the script. So you can just
type "LamestBot" from your shell prompt to start up your bot. For
this to work, the top line of your script MUST contain the correct path
to eggdrop.
-
It's advisable to run your
bot via crontab so that it will automatically restart if the machine goes
down or (heaven forbid) the bot should crash. Look at the file 'scripts/botchk'
and 'scripts/autobotchk' for a great start with crontabbing the bot.
-
Smile, and if you haven't already
read the README file in its entirety, go take a long walk off a short pier.