Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Applies to: v10

v10 reader's guide. This guide is the Worldgroup 3.x guide (chapters 1-28, Marc Fountain's text, unchanged) with v10 notes added after the passages they concern, plus chapter 29 (the v10 layer). Three things to know first: (1) Client/Server mode and Active HTML are not in v10 and are marked as such wherever they occur; (2) v10 is built with Visual Studio, not Borland, so the Borland/Phar Lap/MAKEBBS instructions are history (chapter 29, section 29.3); (3) string literals passed to char * parameters crash v10 modules, and most examples in this guide do exactly that (chapter 29, section 29.4, read it before copying any example).

...

Applies to: WG2+

Editor’s note: the server-side topics of the addendum are merged into the chapters below (3, 4, 5, 6, 11). The client-side topics are collected in 20-client-side-addendum.md.

Requirements

Applies to: v10

The requirements and installation steps of this chapter (Borland C++ 4.50, the Phar Lap DOS-Extender SDK, SET BORLAND/PHARLAP/MBBS, MAKEBBS.BAT, the 386/486 and DOS 5 requirements) do not apply to v10. A v10 module is built with Visual Studio from a .vcxproj (Win32 and x64) against inc\ and wgserver_lib.lib; see chapter 29, section 29.3. Source written for WG1/WG2/WG3.x must be ported first: chapters 28 and 29.

Applies to: WG3.x

Editor's note: the requirements and installation steps in this chapter (Borland C++ 4.50, the Phar Lap 286|DOS-Extender SDK, SET BORLAND/PHARLAP/MBBS, MAKEBBS.BAT) are the WG1 development environment. Worldgroup 3.12 requires a 32-bit Windows host and supports Borland C++ 5.00 (DOS and NT/95 servers), Microsoft Visual C++ 4.2 (offline NT/95 programs) and Visual Basic 3.00 (client programs). See chapter 21, "Development Tools" and "Worldgroup Development Environment Requirements".

Header check: the 3.2 kit's \WGDEV\SRC also holds bc551-32.mak, bc50-32.mak, bc45.mak and bc31.mak; the addendum names only Borland 5.00. bc551-32.mak (ilink32) still reads the BC50 environment variable (bc551-32.mak:4-13).

...

Applies to: WG3.x

Editor's note: steps 2 through 14 below are the WG1 procedure. In WG3.x the build tree is \WGDEV (INC, BIN, LIB, HELP, SRC, VCPROJ), controlled by the environment variables BC50, DOSEXT, WGDEV, WGDOS, WGNT, BUDOS, MVC42 and VB3; projects are built with MKNT, MKDOSL, MKDOSP or MAKEWGS and .MAK files that include $(WGDEV)\src\GCRULES.MAK; there is no %MBBS%\SRC\MAKEBBS.BAT with one cd/MAKE pair per project. The PATH entry is \WGDEV\BIN (chapter 21, "Environment Variables", "PATH Statement", "Compilation Batch Files"). Existing WG1/WG2 source must be ported first: see chapter 28.

The following procedure has been designed to apply to everyone who purchases C source code from Galacticomm. It assumes you already have a way to edit text files like .BAT files.

...

For example, you could have something like this in your AUTOEXEC.BAT file:

Code Block
:
SET BORLAND=C:\BC45
SET PHARLAP=C:\RUN286
SET MBBS=C:\WGSERV
:
PATH=C:\DOS;%BORLAND%\BIN;%PHARLAP%\BIN;%MBBS%\SRC
:

Because you’ve changed AUTOEXEC.BAT, reboot your PC before continuing.

...

Notice that you cannot use the environment variables here, but must use the literal path names instead, all the more reason to install software in the default locations.

TLINK.CFG

Code Block
-L\BC45\LIB;\RUN286\BC4\LIB;\WGSERV\DLIB

TURBOC.CFG

Code Block
-I\BC45\INCLUDE;\RUN286\INC;\WGSERV\SRC
-L\BC45\LIB;\RUN286\BC4\LIB;\WGSERV\DLIB
  1. Get and install Borland C++ 4.50 Huge Model Support. Dial (617) 661-1009 and log onto Phar Lap’s BBS. Go into File Libraries, select library GALACT, and download the file named PLPAT4.ZIP into your \RUN286\BC4\LIB directory, then unzip it and install it:

...

For every %MBBS%\SRC\.MAK file that comes with the Extended C Source Developer’s Kit, you need to insert another instruction pair in MAKEBBS.BAT ahead of the last two lines of each file:

Code Block
cd %MBBS%\src           <-- add verbatim for each additional *.MAK file
MAKE -fwgsxyz.mak               <-- add for each additional *.MAK file, e.g. WGSXYZ.MAK
cd %MBBS%                       <-- leave as next-to-the-last line of each batch file
:DONE                   <-- leave as last line of each batch file

For every %MBBS%\SRC\.MAK file that comes with the Extended C Source Developer’s Kit, you need to insert a debugging version of this same instruction pair in MAKEBBSD.BAT ahead of the last two lines of each file:

Code Block
cd %MBBS%\src            <-- add verbatim for each additional *.MAK file
MAKE -DDEBUG -fwgsxyz.mak <-- add for each additional *.MAK file, e.g. WGSXYZ.MAK
cd %MBBS%                        <-- leave as next-to-the-last line of each batch file
:DONE                    <-- leave as last line of each batch file

Only if you purchased Btrieve to create your own databases, do step 9:

...

Insert another instruction pair in %MBBS%\SRC\MAKEBBS.BAT ahead of the last two lines of each file:

Code Block
cd %MBBS%\src           <-- add verbatim for each additional *.MAK file
MAKE -fgalxyz.mak               <-- add for each additional *.MAK file, e.g. GALXYZ.MAK
cd %MBBS%                       <-- leave as next-to-the-last line of each batch file
:DONE                   <-- leave as last line of each batch file

Insert a debugging version of this same instruction pair in %MBBS%\SRC\MAKEBBSD.BAT ahead of the last two lines of each file:

Code Block
cd %MBBS%\src            <-- add verbatim for each additional *.MAK file
MAKE -DDEBUG -fgalxyz.mak <-- add for each additional *.MAK file, e.g. GALXYZ.MAK
cd %MBBS%                        <-- leave as next-to-the-last line of each batch file
:DONE                    <-- leave as last line of each batch file

Instead of GALXYZ.MAK use the name of whatever .MAK file comes with the C source code of the Add-on Option. This step allows you to use MAKEBBS and MAKEBBSD to properly follow up on any and all changes you may make to the source files in the Add-on Options.

...

13a. Put the C source code you write in %MBBS%\SRC alongside the source code we wrote. For every .MAK file you create, insert another instruction pair in MAKEBBS.BAT ahead of the last two lines of each file:

Code Block
cd %MBBS%\SRC           <-- add verbatim for each additional *.MAK file
MAKE -fdddxyz.mak               <-- add for each *.MAK file you create, e.g. DDDXYZ.MAK
cd %MBBS%                       <-- leave as next-to-the-last line of each batch file
:DONE                   <-- leave as last line of each batch file

Insert a debugging version of the same instruction pair in MAKEBBSD.BAT ahead of the last two lines of each file:

Code Block
cd %MBBS%\SRC            <-- add verbatim for each additional *.MAK file
MAKE -DDEBUG -fdddxyz.mak <-- add for each *.MAK file you create, e.g. DDDXYZ.MAK
cd %MBBS%                        <-- leave as next-to-the-last line of each batch file
:DONE                    <-- leave as last line of each batch file

or:

13b. Put the C source code you write in %MBBS%\DDD (substituting your own Developer-ID for DDD). For every .MAK file you create, insert another instruction pair in MAKEBBS.BAT ahead of the last two lines of each file:

Code Block
cd %MBBS%\DDD           <-- add verbatim for each additional *.MAK file
MAKE -fdddxyz.mak               <-- add for each *.MAK file you create, e.g. DDDXYZ.MAK
cd %MBBS%                       <-- leave as next-to-the-last line of each batch file
:DONE                   <-- leave as last line of each batch file

Insert a debugging version of the same instruction pair in MAKEBBSD.BAT ahead of the last two lines of each file:

Code Block
cd %MBBS%\DDD            <-- add verbatim for each additional *.MAK file
MAKE -DDEBUG -fdddxyz.mak <-- add for each *.MAK file you create, e.g. DDDXYZ.MAK
cd %MBBS%                        <-- leave as next-to-the-last line of each batch file
:DONE                    <-- leave as last line of each batch file

Now, test your development environment:

...

Most of the files you distribute will be combined into .ZIP compressed files on your release floppy diskette(s). The first floppy will contain INSTALL.EXE, of course, and also the file DISK1.DID. This file indicates to the installation program that it is the first in a sequence of at least one disk. The contents of DISK1.DID also convey information. For example:

Code Block
2  150  7000000  NOBBS

Here is what these sample entries represent:

...

An alternate form of the .DID files on each of your release diskettes adds a language name at the end. For example, DISK1.DID might contain:

Code Block
2  150  7000000  English/RIP

This is used in certain special situations. When a language name appears as the fourth parameter in a .DID file, it tells the INSTALL program to be sure to force all text in that language onto the receiving Major BBS, and not to mix it with any text the Sysop may already have in that language.

...

You can use this feature with any user language, such as Spanish/RIP or German/RIP. If you use this feature in your Add-on Option, the Sysop will be given the option (called UPDATE NEW) of mixing his text in the specified user language with yours, but he’ll be strongly encouraged to allow all of your text to take precedence (that option being called UPDATE ALL).

...

Contents  |  Next: Major BBS v10: 02 The Major BBS’s Environment