GitLab

Don't assume !Help puts its resources in 'Resources', depending on where it is in the ROM listing it might be in one of the numerically suffixed ones. Without this, the makefile for Help2 has to have a corresponding assumption hardwired into it.

Version 1.12. Not tagged

Looks like a typo, since there's no point checking search!=NULL then checking again 2 lines later, the intent was probably to check search->msg!=NULL.
Binary rebuilt with cc 5.71 in Disc environment.

Version 1.12. Tagged as 'Messages-1_12'

Pass the location of <resdata> in as a predefine, otherwise we end up with a dependency on <resdata> that the makefile undefines one line later, which upsets AMU.
Retagged as Messages-1_11.

Useful for small/headless modules whose only error message is the one where they kill themselves having not found a hardware dependency.

Version 1.11. Tagged as 'Messages-1_11'

Detail:
  Utils/c/MsgTok2 - MessageTrans won't find messages which don't end in a newline, so revert the assert to its previous state and output an error message whenever we encounter a file which doesn't end in a newline
  Utils/MsgTok2,ff8 - Rebuilt
Admin:
  Tested in OMAP3 ROM build


Version 1.10. Tagged as 'Messages-1_10'

Detail:
  Utils/c/MskTok2 - Fix spurious assert when tokenising a message that runs up to end of buffer and isn't newline terminated
  Utils/Makefile - Tweaked to use CApp makefile fragment
  Utils/MkClean,fd7, Utils/MkCVSClean,fd7 - New scripts for cleaning everything, or for cleaning just the bits we don't want in CVS
  Utils/o - Removed folder, shouldn't be in CVS
  Utils/c/Old - Removed folder, we rely on CVS to store old versions of files
  Utils/c/MsgExt, Utils/c/ScanRes, Utils/c/TokGen, Utils/c/TokGen2 - Fixed dangerous-sounding warnings (potential use of uninitialised variables, wrong fscanf arg type for "%s")
  Utils/*,ff8 - Rebuilt all binaries with Norcroft 5.69
Admin:
  Tested with building/running Iyonix & OMAP3 ROMs


Version 1.09. Tagged as 'Messages-1_09'

Version 1.08. Tagged as 'Messages-1_08'

Previous changes were untagged, but incrementing the version number gives
us a tag we can associate with the official RISC OS 5.16 release.

Version 1.07. Tagged as 'Messages-1_07'

Detail:
  Uses suffixed file extensions for compatiblity with both objasm and asasm.
Admin:
  Supplied by Peter Naulls, tested at ROOL

Version 1.06. Not tagged

Detail:
  Some users reported problems building the sources if they had other
  installations of perl on their build machine. The build system was using a
  mixture of "perl" and "<Perl$Dir>.perl" to invoke the interpreter, and
  sometimes but not always using "do" to expand system variables on the
  command line. This has now been standardised to use "do <Perl$Dir>.perl in
  all cases, and where possible, to use the makefile macro ${PERL}.
Admin:
  Checked that a Tungsten build still works on a build machine with no other
  perl installation. "perl" was aliased to an error to ensure it wasn't used.

Version 1.06. Not tagged

Detail:
  * Switched to build the module using objasm instead of aasm
  * Rebuilt all the utils APCS-32, involved making them C99 compliant
  * Fixed a bug in MsgTok whereby single character tokens would screw up
    the output (because the tokenised version is longer than the original).
    Not really sure how we got away with this in the past, and not sure why
    the token generator produces single-character tokens to begin with.
Admin:
  Tested in a Tungsten build.

Version 1.06. Tagged as 'Messages-1_06'

Detail:
  The included header files are included only in a standard build.  In the
    BBE, the definitions for the 3 SWIs it uses are provided explicitly.
    This means that nearly all of the assembler headers can be removed
    from the BBE.  This is useful because those headers contain many
    details about different customers' hardware and software which other
    customers (of the BBE) should not see.  Hdr:Machine.Machine is the
    only file that may need to be modified in this respect.
  During BBE export, BBEDefs is copied as Defs so that s/Common remains
    unaltered in the BBE.
Admin:
  Tested in manual build.
  Required by RiscOS/Export 0.01 or later (Export-0_01)

Version 1.05. Tagged as 'Messages-1_05'

Detail:
  The messages module needs to export itself very carefully to the BBE
    so that it can still be rebuilt from scratch when required.
Admin:
  Tested in BBE.
  Does not affect other builds.
  Requires BuildSys 2.76 or later.
  Requires Library 0.62 or later.

Version 1.04. Tagged as 'Messages-1_04'

Detail:
  The Messages module has peculiar requirements in that it needs to be
    a fully functional source export to the BBE installation.
Admin:
  Not tested; changes grafted on from earlier version which was tested.
  Should not affect other builds.

Version 1.03. Tagged as 'Messages-1_03'

Detail:
    If there was only one territory then the file scanning in ResCommon was
occuring, increasing build time. ResCommon now detects if there is only one
territory and then copies it straight over to the processed directory.
    This was not needed for the Bethany project and so was left out. Inserted
now to save build time on other projects.

Admin:
    Some testing performed in a 32-bit Lazarus build.
    All Utils binaries have been recompiled with the latest toolset.

Version 1.02. Tagged as 'Messages-1_02'

Detail:
  s.Common
    The loop where it checks to see whether the territory exists and selects
    a default one if not has been optimised a bit.
  Utils.c.LocaleChk
    Changed Territory_NameToNumber to use OS_ServiceCall to prevent problems
    with some territory names not being known (namely Austraila in this case).

Version 1.01. Tagged as 'Messages-1_01'

  Instead the selected territory is selected from the list of territories
  present in the build, guaranteeing that a working territory will be selected.
Admin:
  It will work, but has been tested on a Risc PC just in case...

Version 1.00. Tagged as 'Messages-1_00'

If the configured territory does not exist, the resources from an already defined default territory are taken.

Detail:
  Needed for Bethany as the UK territory is not hard-coded in the kernel as
  one set of ROMs does not contain UK.  If an unknown territory (say 99 for
  example) was selected, the unit would data abort on start up as it could
  not find the correct resources.
  At build time, the application 'LocaleChk' is run that defines a locale
  table which is built into the Messages module.
Admin:
  The new Messages module has been tested in both the Bethany builds (one with
  and one without UK) and the correct behaviour is seen.

Version 0.99. Tagged as 'Messages-0_99'

Detail:
	On a delete-poweron, the default territory is set to UK (01). On
startup the messages module looks at all the registered ResourceFS blocks and
uses the ones containing the currently territory.
	Unfortunately if the territories in the build do not include the UK
resource set, this means that no resources are allocated, and hence the
machine does not boot up in varies weird and wonderful ways (usually by the
WIMP failing to initialise).
	To overcome this limitation, if the territory list in the ROM does
not include UK, then the UK territory code is added to the first territory's
resource blocks. This means that the country code 01 is present in the ROM,
but it does not point to the UK territory. This allows the ROM to boot up.
	The code in ResCommon and ScanRes have been tidied.
	Added a file explaining how the resource differencing within
ResCommon works into a Docs directory.

Admin:
	Tested in Bethany and Lazarus builds. Builds containing UK resource
blocks still work, and ones without it work, and default to the first
territory in the territory list after a delete-poweron.

Version 0.98. Tagged as 'Messages-0_98'

Detail:
	ScanRes now uses Service_International rather than the
Territory_NameToNumber swi. Also added the caseless strcmp() routine to allow
certain string comparisons to work.
	ResCommon now places resources that are common between all the
resource sets into a 'Common' directory, rather than in a numeric form. This
allows ScanRes to place them in the '00' directory that the messages module
expects on start-up.

Admin:
	Tested in Bethany and Lazarus builds.

Version 0.97. Tagged as 'Messages-0_97'

Detail:
	We now need to fit five resource sets into the first Bethany ROM
image. The previous simple scheme that I implemented did not allow this, so
the ResCommon utility has been extensively overhauled to detect more
commonality between resource sets and hence reduce the ROM requirements for
the resources.
	For instance if there are three files, each containing a byte as
follows:
	File:	1	2	3
	Data:	A	B	A
	Then files 1 and 3 will be common, whilst 2 would have it's own,
individual, version of the file.
	This process is undertaken for all files in the resource sets. For a
Bethany build with five territories (and hence resource sets) this parsing
takes about seven minutes to calculate all commonality and copy the files
into the correct processed directories on a RiscPC with RapIde interface.

Admin:
	Tested in Bethany builds with 3 and 5 different resource sets, and in
Lazarus builds with 1 resource set. This all appears to work correctly, with
please use with caution; the first time you do a build with this version,
check the resources in the build to ensure that they at least look correct
with nothing missing.
	There are some limitations of the current system; for more detais of
these please see the 'ToDo' comments at the end of the ResCommon sources.

Version 0.96. Tagged as 'Messages-0_96'

Detail:
	Added more comments to ResCommon and added a few more run-time checks
for incorect parameters. Corrected a comment in ScanRes.
Amin:
	Tested in a Bethany build.

Version 0.95. Tagged as 'Messages-0_95'

Detail:
	Some redundant code had been left in ResCommon, which caused the
resource sets to be incomplete. This code as been removed.
	ResCommon has had many comments added explaining what is going on,
along with associated code tidying.

Admin:
	Tested in Lazarus and Bethany builds. Requires srcbuild 0.21 or
later. Appears to be stable, but use with caution.

Version 0.94. Tagged as 'Messages-0_94'

Detail:
	* ResCommon no longer called with Verbose flag set.
	* A new Perl script, RemoveEmpt, added, that strips out any emtpy
directories in the processed directory.
	* ResCommon now deals correctly with squashed filed - it reads in the
header of the file and ignores the exec address.
	* get_filetype() now works correctly.
	* ResCommon has been generally tidied up.
Admin:
	Still under development. Should work more reliably than the previous
version.

Version 0.93. Not tagged

	This version of the module deals with multiple territory blocks being
held in ResourceFS.

Detail:
	* Fixed a bug in TokGen2. MAX_TOKEN_LEN2 was set to 256, when it
actually should be 254 (to allow for 2 byte to hold length and status). This
was causing an overflow which meant that large messages were not being
correctly tokenised. Also added a check for tokens that are too long, to at
least make sure that the buildmaster is informed that something has gone
screwy with the token generation instead of continuing on regardless.
	* Created a simple Perl script, HelpApend, that appends common help
data onto the end of each of the individual territory blocks.
	* Bug fixed in s.Common: Pointer in list was not being advanced.
	* ScanRes altered to allow nested resorce blocks.
	* Bug fixed in ResCommon - the -simulate flag now works in the
correct manner, and not the inverse (ooops!)
	* MsgTok2 now gives a warning if the input file is not present.
	* The main MakeFile has been altered to go through the extra stages
needed by the multiple-resource system.
	* Added the ResCommon binary.

To be done:
	* Make ScanRes use Service_Territory 0 instead of
Territory_NameToNumber to work out territory number to name mappings.
	* Make ResCommon cope with Squash files.
	* Make ResCommon remove all empty directories from the resource
directories.
	* Tidy up the code.
	* Add documentation.
	* Thoroughly test on different builds.

Admin:
	Must be used with srcbuild 20 or later.
	Important notice: From this version onwards, the TerritoryManager
*must* be placed ahead of Messages in the ROM, but after ResourceFS.
	This module has not yet been tested without the LocaleList system
variable being set.
	Work in progress. Do not use for anything release-critical.

Version 0.93. Not tagged

Build work for this not done yet, but ScanRes modified to output new form
of data block.

Untested.

Version 0.93. Not tagged

Detail:
	This utility can be used to generate a set of common resources from a
series of different locale resource sets. This can then be used by a future
version of the Messages module to create ROM builds with more than one
resource set included. The Common files help save space in the ROM.
Admin:
	Tested on Lazarus build resources. This is very much work in
progress, although it should be essentially feature-complete.

Version 0.93. Tagged as 'Messages-0_93'

Detail:

  * Line 44 of both "s.Messages" and "s.MessagesHI" was missing
    "- Module_BaseAddr", meaning that the offset was incorrect.
    This is now fixed.

Admin:

  * Untested at time of check-in; to be tested in Lazarus development
    build.

Version 0.92. Tagged as 'Messages-0_92'

Version 0.91. Tagged as 'Messages-0_91'

Version 0.90. Tagged as 'Messages-0_90'

Changed to assume resources are immediately after the end of the ROM module chain. Requires Kernel 4.79.

Version 0.89. Tagged as 'Messages-0_89'

Version 0.88. Tagged as 'Messages-0_88'

ScanRes utility modified to include trailing zero word in output file - necessary for MessData export.

MessagesHI now expects to find resources at &04000000 - latest Kernel maps
top 8Mb of ROM there.

Version 0.87. Tagged as 'Messages-0_87'

Version 0.86. Tagged as 'Messages-0_86'

Added extra targets for placing resources beyond the first 8Mb of ROM.

Version 0.85. Tagged as 'Messages-0_85'