On Tue, 27 Jan 2015 12:38:12 -0800 (PST), Efudd <someone>
wrote:
This last 0014 references a new build system. Any progress there?
I have it building lib and main, but not pplc. It makes testing and
debugging easier, that's why I use it. When I'm done, I backport the
fixes to the old CDC build system, and release that.
I don't have any plans to do away with the old build system. Using both
old and new is a good cross check to make sure I didn't miss anything or break anything with the new build system.
I'm too lazy to package it up right now. And it won't help much unless
you're into serious debugging and testing of lib and/or main.
One problem I'm interested in, is making the fossil code more efficient,
and less of a CPU hog. But I've not worked on it lately, and there's no popular demand ...
On Thursday, January 29, 2015 at 2:39:34 AM UTC-5, Trifle Menot wrote:
On Tue, 27 Jan 2015 12:38:12 -0800 (PST), Efudd <someone>
wrote:
This last 0014 references a new build system. Any progress there?
I have it building lib and main, but not pplc. It makes testing and debugging easier, that's why I use it. When I'm done, I backport the
fixes to the old CDC build system, and release that.
I don't have any plans to do away with the old build system. Using both
old and new is a good cross check to make sure I didn't miss anything or break anything with the new build system.
I'm too lazy to package it up right now. And it won't help much unless you're into serious debugging and testing of lib and/or main.
One problem I'm interested in, is making the fossil code more efficient, and less of a CPU hog. But I've not worked on it lately, and there's no popular demand ...
I'm assuming this died at this point? I'd like to get the most current work you have, if possible....
On Thursday, January 21, 2016 at 3:40:17 PM UTC-8, Efudd wrote:
On Thursday, January 29, 2015 at 2:39:34 AM UTC-5, Trifle Menot wrote:
On Tue, 27 Jan 2015 12:38:12 -0800 (PST), Efudd <someone>
wrote:
This last 0014 references a new build system. Any progress there?
I have it building lib and main, but not pplc. It makes testing and debugging easier, that's why I use it. When I'm done, I backport the fixes to the old CDC build system, and release that.
I don't have any plans to do away with the old build system. Using both old and new is a good cross check to make sure I didn't miss anything or break anything with the new build system.
I'm too lazy to package it up right now. And it won't help much unless you're into serious debugging and testing of lib and/or main.
One problem I'm interested in, is making the fossil code more efficient, and less of a CPU hog. But I've not worked on it lately, and there's no popular demand ...
I'm assuming this died at this point? I'd like to get the most current work you have, if possible....
not really dead.
they just wanted to fix some of the pcboard problems.
and is working on it as they can.
Indeed. I helped some (tried, Trifle and I work a little differently)
I just don't want to duplicate work if he's made further progress with a
new build system.
Compiles and works. Archive includes compiler and library for building.
v0.014:
Fix giveup.c to release timeslices on WINXP, and remove its code
segment self modification mess, replacing that sorry code with a
function pointer that allows a debugger to work.
Added ppl directory to main\obj, needed for building pplc.
As previously mentioned in change 009, I expected to abandon the
CDC build system in favor of my new modular build system. Since
then, however, I wrote batch files that backport patches from my
new build system to the CDC build system. Using the two systems
in parallel is good for testing, I can verify that the new build
system does not create problems. And it's still possible to use
the CDC build system for releasing fixes, providing users with a
format already familiar to them.
http://www.4shared.com/zip/uy-VvYWyce/PCBoard_153_source_code_v0014.html
ed2k://|file|PCBoard%2015.3%20source%20code%20v0.014.zip|27066143|2C8A300076A3E9377AE0FC49F00F4B85|h=WFJN5IBGWL3UR3HY5EWUYG6U7LOHPC6B|/
I am interested in it.
VinylDoctor - was there anything in the original archives that matched "vmdata.lib" or "vmdata.h"? That library is used to build the setup utilities, uucp utilities and pcbfiler utilities.
Incidentally, the company that made that library still exists although
VMData went out of support in 1999. Still, one of their devs graciously responded to my email and provided me a current version....
1) I couldn't get pcboardM.exe to run because it was too large.
1a) This led me down the path of going back in time and bought old borland/tasm/etc. manuals I could find on the internet to try to bring
back old memories and get it to live again.>2) I started working on
getting it to build under a more current borland environment with
limited success.
3) I branched and started recoding some of the ASM back into C with the ultimate goal of a potential port for the purposes of "just because".
Compiles and works. Archive includes compiler and library for building.
v0.014:
Fix giveup.c to release timeslices on WINXP, and remove its code
segment self modification mess, replacing that sorry code with a
function pointer that allows a debugger to work.
Added ppl directory to main\obj, needed for building pplc.
As previously mentioned in change 009, I expected to abandon the
CDC build system in favor of my new modular build system. Since
then, however, I wrote batch files that backport patches from my
new build system to the CDC build system. Using the two systems
in parallel is good for testing, I can verify that the new build
system does not create problems. And it's still possible to use
the CDC build system for releasing fixes, providing users with a
format already familiar to them.
http://www.4shared.com/zip/uy-VvYWyce/PCBoard_153_source_code_v0014.html
ed2k://|file|PCBoard%2015.3%20source%20code%20v0.014.zip|27066143|2C8A300076A3E9377AE0FC49F00F4B85|h=WFJN5IBGWL3UR3HY5EWUYG6U7LOHPC6B|/
On Thursday, January 29, 2015 at 2:39:34 AM UTC-5, Trifle Menot wrote:
I've not worked on it lately, and there's no popular demand ...
I'm assuming this died at this point? I'd like to get the most
current work you have, if possible....
On Tue, 26 Jan 2016 17:05:25 -0800 (PST), Efudd <>
wrote:
Indeed. I helped some (tried, Trifle and I work a little differently)
I added your work to the pot. But I did revise it, to fit my framework
and style. That's what editors do to authors. They mash the potato.
I am the first one who got the PCBoard source compiling, so I consider
myself the de facto editor of this "project." If you can call it that.
With only three people known to be interested, it's not much of a
project. For me it's more about programming and code than any desire to actually run a BBS.
I just don't want to duplicate work if he's made further progress with a >new build system.
My new build system works. The reason I wanted it was to have a better environment for debugging. You can't build the whole PCBoard executable
with debugging symbols on every module, it's too big and won't run.
In my new build system, I use a single command that builds the whole
thing, lib and main, and spits out the final executable.
When I want debugging symbols on a few modules, I go back into the
source\obj tree and delete the objects for the modules in question. Then rebuild just those objects and relink to produce a new executable, which
is small enough to actually run. It's been so long since I've done that,
I don't remember the exact steps. But it's not hard. Much easier than
trying to use the CDC build system.
It's all kind of pointless unless you use it for debugging with Turbo Debugger. But if you're really into that, I can package it up for you.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 185 |
Nodes: | 16 (2 / 14) |
Uptime: | 11:04:34 |
Calls: | 3,718 |
Calls today: | 1 |
Files: | 11,157 |
Messages: | 3,451,865 |