GitLab

So long, and thanks for all the fish.

Version 5.40. Tagged as 'BuildSys-5_40'

Do actively report when the CMHG file is deleted in CModule.
Add PRISMLIB to the available module libraries.
Components files updated to pass USB driver switches via CDEFINES not
CFLAGS.
Tested with OMAP3 ROM build, other components files modified by eye but
not tested.

Version 5.39. Tagged as 'BuildSys-5_39'

Not tagged.

WIPE is now the same as XWIPE, rather than the annoying "-wipe".

Version 5.36. Tagged as 'BuildSys-5_36'

* Added components file to generate a !System
* Binaries/Browse/BuildEnv/Disc/IOMD32/OMAP4/Printers/Tungsten add heading blocks and line stuff up
* OMAP3 remove unused switch from FPEmulator
* SysMap add mapping from Sovereign to 'V'
* CTools extra qualifiers on some modules to get help right for modules in the 310 directory
* AAsmModule when CMDHELP=None is in force you can infer that no international help is desired, therefore pass this as a switch to the module to allow it to remove the tokens from its help table (based on how the 'standalone' switch is done)

Version 5.35. Tagged as 'BuildSys-5_35'

Version 5.34. Tagged as 'BuildSys-5_34'

Add CLEAN_DEPEND support to AAsmModule makefile fragment. Disable VFP/NEON assembler for Tungsten ROM versions of BASIC.

Detail:
  Makefiles/AAsmModule - Added ${CLEAN_DEPEND} as a dependency to the 'clean' rule, to allow components to extend the default rule. This is the same functionality that the CApp fragment offers.
  Components/ROOL/Tungsten - Disable VFP/NEON support in the BASIC assembler, due to lack of ROM space.
Admin:
  Required changes for BASIC 1.49


Version 5.33. Tagged as 'BuildSys-5_33'

Detail:
  The change which permitted top-level makefiles to include only CApp,
  CModule etc accidentally broke makefiles which included HostTools (StdTools
  got included instead and overwrote the HostTools settings). Amazingly, we
  seem to have got away with this so far - but fixed now. Also, brought the
  GNUmakefiles versions in line with updates to the amu Makefiles in this
  and other respects.
Admin:
  Tested in a RISC OS ROM build, and for building cross-compiling versions
  of the tools.

Version 5.21. Tagged as 'BuildSys-5_21'

Detail:
  ModuleLibs used the wrong (non-zM) version of RISC_OSLib. This meant that
  any module using the shared makefiles and RISC_OSLib ended up using the
  static initialisers instead of static data, meaning that it could not be
  reinitialised or multiply instantiated. This was rather critical for the
  FrontEnd module, which relies on being reinstantiated for each new tool.
Admin:
  Fixes the reported bug in FrontEnd 1.31 - verified it now works with more
  than one tool loaded.

Version 5.14. Tagged as 'BuildSys-5_14'

Detail:
  A line in this makefile evaluates CFLAGS so that the default static data
  relocation and stack checking options can be inserted before any overrides
  from the top-level makefile. But this was being done before StdTools was
  included, so C_STKCHK had not yet been defined, so if the top-level makefile
  tried to use it, it had no effect.
Admin:
  Tested using new FrontEnd makefile.

Version 5.13. Tagged as 'BuildSys-5_13'

Detail:
  * Some subtle bugs can be caused by including shared makefiles in the
    wrong order. To try to prevent further problems, and simplify main
    makefiles at the same time, CApp, CLibrary and CModule now include the
    makefiles they depend upon themselves, in the correct order: generally
    speaking, all macro (re)definitions should be before rule definitions.
  * Added sentry macro definitions to each makefile. These can be used to
    avoid repeated inclusion of makefiles - particularly important now that
    CApp, CLibrary and CModule do additional includes. This removes the
    majority of cases where amu produced warnings about multiple inclusion;
    a few components remain where this is still the case, but these
    warnings are harmless. If they bother you, simply remove the
    now-superfluous include statements from the relevant main makefile.
  * Created a CUtil shared makefile, for building transient utilities. The
    'C' in the name is more for c...

Detail:
  * Fixed dependencies for debug builds in GNUmakefiles/CApp
  * Added -f switch to rm in GNUmakefiles/StdTools to make it fail silently
    if the file doesn't exist, like the RISC OS version
  * Fix for amu complaining if INSTTYPE is undefined in Makefiles/CApp
  * Reflected makefile changes in resgen, squeeze and xpand in CTools
    component file
  * Added a8time to ModuleDB and CTools component file
Admin:
  Tested in  a C Tools build

Version 5.03. Tagged as 'BuildSys-5_03'

Detail:
 CApp:
  * New variable CLEAN_DEPEND is now the preferred way to specify additional
    clean actions because GNU make doesn't have an equivalent to amu's :: rules
  * Can now indicate preference to use C++ linker options using LINK_TYPE
  * Gains install phase support:
    + INSTALLAPPFILES lists the files to be copied, effectively specified
      relative to LocalRes$Path
    + Adopted INSTTYPE concept from DDE makefiles for cases where executable
      and support files need to be installed to different locations
    + Unusual cases can override this implementation using CUSTOMINSTALLAPP
      and/or CUSTOMINSTALLTOOL

  CLibrary:
  * New variable CLEAN_DEPEND is now the preferred way to specify additional
    clean actions because GNU make doesn't have an equivalent to amu's :: rules
  * -o is no longer a mandatory argument to libfile - now in ARFLAGS rather
    than used explicitly

  DbgRules / StdRules:
  * Macroised some Norcroft-specific features

  HostTools:
  * Clean phase support was incomplete

  StdTools:
  * A few additional tool definitions
  * Added macro definitions for common C options
  * C's enable-warnings and suppress-function-name-embedding options now on by
    default because they're usually (maybe even universally?) used - it won't
    hurt if they're specified again by existing makefiles
  * C++ now has equivalent INCLUDES and DEFINES variables, and the standard C++
    headers are on the default include path
  * SEP is defined as the directory separator character and can be used from
    top-level makefiles in a platform-independent way

  Functionally equivalent versions of the following makefile fragments
  have been developed so far for executing on a Posix build host:
    AppLibs, CApp, CLibrary, DbgRules, HostTools, StdRules, StdTools
  These suport native compilers (when APCS=Host) and cross-compilers,
  and GCC (when TOOLCHAIN=GNU) and Norcroft toolchains - typically these
  environment variables would be selected by running an Env file.

Admin:
  Tested by building as many as possible of the DDE components on RISC OS
  and on Linux, using native and cross compilers, and using Norcroft and
  GNU toolchains.

Version 5.01. Tagged as 'BuildSys-5_01'

Fixed to point at the (new) location of the zip tool and added some useful
parameters - this is safe because nothing in the build tree was using
this definition of ZIP anyway.

Version 4.81. Tagged as 'BuildSys-4_81'

Update CModule makefile fragment to use a default RESFSDIR if required. Add IIC module to OMAP3 components file.

Detail:
  Makefiles/CModule - makefile fragment now generates a default RESFSDIR value in an identical way to the AAsmModule fragment, easing migration of makefiles to the fragment system.
  Components/ROOL/OMAP3 - IIC module has been added to ROM image
Admin:
  Tested on rev C2 beagleboard


Version 4.80. Tagged as 'BuildSys-4_80'

Detail:
  * Updates to CModule makefile fragment to reduce the number of OS-specific
    rules in main Makefiles:
    + Added (RAM|ROM)(C|ASM)DEFINES variables. These allow the calling makefile
      to specify additional defines for RAM or ROM builds of C or assembler
      source files respectively. Traditionally this was done by having separate
      object files for RAM and ROM corresponding at least to whichever source
      file was responsible for interfacing with ResourceFS, but this requires
      messy additional rules. With this new approach, it is necessary to clean
      the component when switching between RAM and ROM builds, but I don't
      think this will affect many people's workflows.
    + Added CMHGDEPENDS. This should be used to specify which object files need
      a static dependency upon the h file autogenerated from the cmhg file.
      It should be specified in the usual form for object files passed to
      CModule - with neither an o. prefix nor a .o suffix.
  * Added TBOXINTLIB to ModuleLibs makefile fragment.
  * AsmUtils, HdrSrc, TCPIPheaders, ToolboxLib and UnicodeLib all upgraded in
    ModuleDB from EXP to ASM or C components, to permit them to be built in the
    install phase. As a result, those other Components files that didn't
    already do so now need to override this back to -type EXP.
  * BuildHost Components file edited to reflect the fact that binaof, binasm,
    modgen and ResGen now have separate install phases for executables and
    Docs files.
Admin:
  The new Components file uses various components that are not publicly
  released, so it can only sensibly be used internally by ROOL. However, it's
  more convenient for us to keep it alongside the other Components files - and
  it also serves as an illustration of how to do a disc build.

Version 4.77. Tagged as 'BuildSys-4_77'

Detail:
  This is useful for building tools during the course of a main build where
  the build host is of an incompatible architecture to the target - for example
  building an Iyonix ROM on a Risc PC or an architecture-tuned Beagleboard ROM
  on an Iyonix.  For now it relies on re-using the target architecture versions
  of CApp and other makefile fragments so it's not suitable for cross-
  compilation yet (in other words, the host system is still assumed to be a
  RISC OS machine).
Admin:
  Tested by building an APCS-R target on an Iyonix (with a few tweaks - we
  can't link with the APCS-R stubs on an Iyonix, but the stubs should be
  architecture-invariant within the same calling standard so this isn't a
  real problem).

Version 4.75. Tagged as 'BuildSys-4_75'

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 4.73. Tagged as 'BuildSys-4_73'

Detail:
  * Added new components file
  * Added entry for new HAL in the ModuleDB
  * Minor tweak to Makefiles:CModule so HALs can use shared Makefiles:
    no longer assumes that all callers wil have a non-null CMHGFILE
Admin:
  Used in a test build

Version 4.68. Tagged as 'BuildSys-4_68'

Version 4.63. Tagged as 'BuildSys-4_63'

This represents the version released in the Batch 4 "bbe" tarfiles.
Tagged as 'Batch4'