CydandClaude Fable 5
63312e07f9
- BORLAND/: Borland C++ 4.52 (chosen over 4.5 by byte-match: CODE/RP/CW32.LIB
is identical to 4.52's install lib). BCC32/TLINK32/TLIB/MAKE run natively on
Win11; CODE/BT/OPT.MAK is the shipped BTL4OPT.EXE's exact flag recipe
(extender = Borland PowerPack DPMI32, not Phar Lap TNT).
- restoration/source410/: the literal 1995-form reconstruction of the missing
BT game source (never mixed into CODE/). Round 1-3 state:
* 6 of 10 surviving original TUs COMPILE CLEAN under the period toolchain
(BTMSSN, BTCNSL, BTSCNRL, BTTEAM, BTL4MODE, BTL4ARND) - first builds
since 1996.
* BT_L4/BTL4APP.CPP pilot reconstruction: 12/12 functions, Fail() lands on
its binary-recorded line 400 exactly.
* BT/BTCNSL.HPP: console wire IDs recovered from the binary's ctors
(Killed=9, Damaged=10, ScoreUpdate=13, DeathWithoutHonor=15 [T1];
TeamScore=12 flagged [T4]).
* MUNGA/: 8 engine-header backfills back-dated from the BT412 WinTesla tree
(VDATA numbering decomp-verified; AUDREND's OpenAL-era virtual removed -
the period compiler is the drift detector).
* Tooling: backdate.py (WinTesla->1995 header transform), compile410.sh
(per-TU verification sweep under authentic OPT.MAK flags).
* README: corrected roadmap - MECH.HPP is the capstone grown with the mech
TU reconstructions; BTREG.CPP green = the header-family milestone.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
47 lines
1.7 KiB
Plaintext
47 lines
1.7 KiB
Plaintext
Instructions for the ide example MULTITRG.IDE.
|
|
//
|
|
// Instructions for MultiTrg.ide
|
|
// Copyright Borland International, 1993
|
|
//
|
|
|
|
|
|
This project is an example of multi-targeting in the new project manager.
|
|
|
|
The two multitrg.exe targets in the project are mostly similar with two major
|
|
differences: The local options for the first target specifies output
|
|
directories to point to .\out16 and is tagged as Win3.x (16 bit)
|
|
applictation in TargetExpert. The second target has local options specifying
|
|
output directories to point to .\out32 and is tagged as a Win32 appliction
|
|
in TargetExpert.
|
|
|
|
The targets were created by
|
|
1) selecting Project|New Target,
|
|
2) typing "multitrg" in the 'Target Name' field,
|
|
3) selecting 'Standard' from the 'Target Type' list,
|
|
4) selecting 'Ok'
|
|
|
|
This leads to TargetExpert where:
|
|
5) selecting "Windows 3.x (16 bit)" from the 'Platforms' list
|
|
6) selecting 'Ok'
|
|
|
|
Repeating steps 1-6 for the second target with the exception of step (5)
|
|
where "Win32" was selected from the 'Platforms' list.
|
|
|
|
To redirect output on the first target to the 'out16' directory
|
|
6) Right click on the first target
|
|
7) Select 'Local Options' with brings up the Multi-Page-Dialog
|
|
8) In the 'Directories' section entering 'out16' in the 'Intermediate'
|
|
and 'Final output' fields.
|
|
9) Select 'Ok'
|
|
|
|
Repeating steps 6-9 for the second target replacing 'out16' with 'out32'
|
|
completes the process.
|
|
|
|
You should note that the source nodes under both executables are copied
|
|
under each target. If you wanted to add a source module you would have to
|
|
do so (in this project) in two places to keep you 16bit and 32bit targets
|
|
in synch. To get relief see the example in the SrcPool directory.
|
|
|
|
|
|
|