[CDG5] Linked Patches

[Elliot Nunn]

They're very complicated -- and one of the last things between us and a
byte-perfect System 7.1. I am going to write some code to de-link lpch
resources in order to tell which files need to be built into them.
Otherwise I am at the mercy of the debug output from LinkPatch, for
which I do not have the source. (It seems to have been written in C++,
leading me to suspect that Vectorize also C++. They may even have shared
code.)

But other projects will have to take priority for a week or so, so if
somebody wants to beat me to this, I won't complain.

;)

> On 24 Dec 2018, at 1:03 pm, Elliot Nunn <elliotnunn at fastmail.com> wrote:
> 
> That's going a bit over my head. But it turns out that the source tree
> has an object file and small assembly stub (all in LinkedPatches:) that
> when linked together produce a working LinkPatch.
> 
> https://github.com/elliotnunn/LinkPatch
> 
> And now to figure out what to do next. I assume that it postprocesses
> the System file, and maybe it leaves some hints around for the
> Installer. Time to read the error messages...
> 
>> On 23 Dec 2018, at 10:27 pm, daniel B-J <danielbj314 at verizon.net> wrote:
>> 
>>> Anyone got a clue how the LinkPatch tool works? I am having trouble
>>> correlating the contents of System 7.1.2 with the Cube-E Sys.r file.
>>> (The idea is, like with the NewWorld ROM, to build something bootable.)
>> 
>> I think that the linked patch files include a whole ton of macros from LinkedPatchMacros.a. The macros set up all kinds of stuff. At boot time, LinkedPatchLoader constructs jump tables for all the linked patch resources. I think. It was very confusing when I read it. I’m not even sure we’re talking about the same thing. Does my description make sense with what comments and source you are looking at?
>> _______________________________________________
>> cdg5 mailing list
>> cdg5 at ucc.asn.au
>> https://lists.ucc.gu.uwa.edu.au/mailman/listinfo/cdg5
>