Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[bruceuncle]

I've started this topic as a place to post info on the AMOS Pro Architecture.

That is, anything that relates to the 'whole' picture.  Not for stuff on individual bits of code, etc.

I'll kick this off with a spreadsheet and PDF print of the dependencies between the *.s files.  And before anyone asks "What about the other *.s files?", this whole topic will relate only to those that are essential to completely generating AMOS Pro V2.0 from the sources.  Anything that's used purely for debugging and testing is excluded.  I have included the Debug.s, Debug0.s, Debug1.s and Debug2.s files but only because Debug.s is referenced and the other three are quick replacements when debugging.

Use the other *.s files for debugging purposes if you need to but beware that some are entirely unsuitable for AMOS Pro V2.0.  It's best to make your own if ever you need them.

The next publication will be the build flow, dependencies and sources for generating the rest of AMOS Pro V2.0.  That is anything this is not a *.s file.  It's fairly straightforward for most of them as they're *.AMOS, *.abk, etc., or plain text files - just a lot of them!

I haven't included the Installer at this stage as I haven't looked at it yet.

Just AMOS Pro V2.0 as it comes 'out of the box' (though I'm still tempted to sneak Sprite_600 from AMOS V1.3 into the Extras folder  ).

Zip file attached.

[SamuraiCrow]

Ummm... Library offsets from LibOffsets.i are calculated by multiplying running the LVO utility on an FD file for each library and copying those offsets to the new LibOffsets.i file.  The LVO utility is found on the Amiga Developers' CD in the AmigaOS version 2 includes and requires that the FD files be located in a directory with FD: assigned to it.

This should be useful for incorporating AmigaOS 3.1 features into future versions of AmosPro.

[bruceuncle]

This should be useful for incorporating AmigaOS 3.1 features into future versions of AmosPro.

Good point.  Though, having said that, I'm not at all sure what features are involved.  As I've mentioned a few times, I'm completely new to the Amiga architecture since AmigaOS 2.11 which was the last one I used.  And I have to admit that I didn't get too involved with that and previous versions as I was more heavily into AMOS 1.3 at the time and the OS scared me witless after I tried reading through the RKMs ...  You guys seem to have been steeped in Amiga architecture for many years.  So expect me to make some embarrassing boo-boos in the coming months.   

The only un-sourced file that really bothers me is +Dialog_Funcs.Bin.  It's obvious that it's using offsets into the code from my limited understanding of how the Interface DBL interpretation works.  But I'm too busy with what I call "CSI AMOS" (look for results in a new topic) to do a thorough job on investigating it yet.

I did make one small error in the build_flow_and_dependencies spreadsheet.  Both +ILib.s and +Lib.s are used by Make_Labels.AMOS to generate +LEqu.s.  So find build_flow_and_dependencies_Rev_2_0 attached (I really should get into the habit of putting revision numbers on these documents from the start  ).

The switch to using set in the macros defining the library instruction numbers does have its drawbacks.  See CSI AMOS for details.

[bruceuncle]

Oops 
Stuffed the pagination in those spreadsheets.  Find build_flow_and_dependencies_Rev_2_1 attached.