GitLab

Changes in Env 1.40-1.41 require GNU.gawk and amu within the same application
slot at the same time, which exceeds the default 640K WimpSlot. There isn't
actually any need for the awk script to run within a Makefile (it's not
testing the Makefile's behaviour directly) so by moving the lines up to
!Common, the memory usage is reduced.

Version 1.42. Tagged as 'Env-1_42'

These relied on calling the GNU.gawk binary, but did so *before* the run path
was guaranteed to point at it. Move that block of lines lower down.

Also remove unused (and commented) Src$Dir definition within the lines that
we move it past.

Version 1.41. Tagged as 'Env-1_41'

Extract the version number from AMU's help message and set `AMU$Version`
accordingly. Also set `AMU$HasWorkingWildcard` depending upon whether the
installed version of AMU has a fully functional `$(wildcard)` function.

Version 1.40. Tagged as 'Env-1_40'

Version 1.39. Tagged as 'Env-1_39'

In cases where mk's environment didn't define these, the null definition from
ModuleDB was overriding any default definitions in the Makefile, which is very
unhelpful!

Detail:
  In tentative efforts to support cross-compilation to date, a few
  components have had mk.sh scripts inserted. These are functionally
  equivalent to the !Mk* TaskObey files, in that they are a convenience for
  developers working on that component in isolation. However, unlike their
  RISC OS equivalents, the nature of shell scripts means that they are
  relatively complex, and are therefore relatively burdensome to create and
  maintain. This commit replaces this mechanism with a shell function which
  is defined when you source the Env file. This enables a build phase to be
  applied to the component at the working directory to be built with a
  simple "mk export", "mk install", "mk rom", "mk clean" and so on.
  Previously, the build variables COMPONENT, TARGET and INSTDIR were encoded
  in the mk.sh script, and where a component had multiple targets, the mk.sh
  script would run the phase on all such components; now the mk function
  scans the ModuleDB to locate this information instead. You can even target
  a component in another directory using the -C switch (chosen to match
  make's equivalent switch). Some efforts have also been made to support
  Posix shells other than bash. The only feature dropped is the ability to
  build the component using a different environment within a subshell.
  However it's relatively simple to construct this at the command line if
  desired.

Version 1.38. Tagged as 'Env-1_38'

Detail:
Admin:


Version 1.37. Tagged as 'Env-1_37'

Detail:
Admin:


Version 1.36. Tagged as 'Env-1_36'

Detail:
  ROOL/PlingSystem,feb - Instead of using the Archimedes machine type, use "26". This allows for e.g. recognition of the StrongARM MSR bug in Hdr:Machine.Machine, and allows CLib to build multiple variants of some routines to target the different CPU architectures (e.g. long multiplies)
Admin:
  Tested with PlingSystem build
  Requires HdrSrc-2_63, Library-1_87, BuildSys-6_90


Version 1.35. Tagged as 'Env-1_35'

Detail:
  Use CortexA7 for code generation options for Titanium, as a synonym for A15.
Admin:
  Submission from Elesar.
  Requires HdrSrc-2_55.

Version 1.34. Tagged as 'Env-1_34'

Admin:
  Submission from Willi Theiss

Detail:
  OMAP5: Since code wise and arch wise A7=A15=A17, the machines in HdrSrc have been made common on A7.
Admin:
  Bash script similarly changed, but untested.
  Retagged as Env-1_33.

Detail:
  OMAP5 and Titanium environments defined.
  !Common.sh CPU switch changed to ARMv7 as appropriate.
Admin:
  Submission from Willi Theiss (OMAP5) and Elesar (Titanium).

Version 1.33. Tagged as 'Env-1_33'

Version 1.32. Tagged as 'Env-1_32'

Detail:
  The Raspberry Pi ROM now joins the IOMD ROM in supporting multiple
  architectures, in this case ARMv6 and ARMv7. This has been achieved by
  creating a new machine type specific for Raspberry Pi. The old ARM11ZF
  machine type remains for builds that are ARM11-only.

Version 1.31. Tagged as 'Env-1_31'

Also add a couple more cross-compile Env files.

Version 1.30. Tagged as 'Env-1_30'

The !Common script will now define a macro variable for Install$Path
which contains <Install$Dir>. which means install targets can now be
specified in the form "Install:foo" rather than "<Install$Dir>.foo".

This is especially handy because any path that has a / in it can end
up being munged from UNIX to RISC OS form, even if it was a RISC OS
path in the first place. But one thing that prevents the munging is
if the path has a : in it.

Long story short, you can now do stuff like this:

    INSTDIR=Install:DDE.AcornC/C++.Library

which was hopelessly broken prior to this change.

Admin:
  Requires mkdir 1.04 for the full goodness. Will be put into the
  main Library component at some point soon.

Version 1.29. Tagged as 'Env-1_29'

Version 1.28. Tagged as 'Env-1_28'

Detail:
  ROOL/OMAP4,feb - OMAP4 ROM size increased from 4MB to 5MB, to cope with some incoming changes
Admin:
  Builds, but untested


Version 1.27. Tagged as 'Env-1_27'

Detail:
  For those components that support cross-compilation, the mk.sh scripts are
  being changed to assume that the castle/bsd/mixed etc directories are no
  longer merged together. This is in line with the change to recommended
  practice for native builds (see the Prepare component in the root of CVS).
  This has no impact on Env, except for the comments in the Env files about
  what they expect the PWD to be on entry.

Version 1.26. Tagged as 'Env-1_26'

Detail:
  !Common,feb - Ensure SharedULib 1.12 is loaded. Boot !GCC (i.e. GCC 4) and !SharedLibs if present
Admin:
  Required for GCC4 based tools to function
  Requires Modules-0_26 for SharedULib 1.12


Version 1.25. Tagged as 'Env-1_25'

Detail:
  ROOL/BCM2835,feb - Reduced ROM size from 6MB to 5MB. We haven't needed 6MB for ages!
Admin:
  Tested on Raspberry Pi


Version 1.24. Tagged as 'Env-1_24'

Version 1.23. Tagged as 'Env-1_23'

Version 1.22. Tagged as 'Env-1_22'

Version 1.21. Tagged as 'Env-1_21'

Version 1.20. Tagged as 'Env-1_20'

Request from Willi Theiss for OMAP4, not tested here.
OMAP3Live brought in line with OMAP3, not tested here.

Version 1.19. Tagged as 'Env-1_19'

Detail:
  New Env file
Admin:
  Changes received from Adrian Lees

Version 1.18. Tagged as 'Env-1_18'

Detail:
  ROOL/Tungsten,feb - Now that we're using compressed ROMs, we can increase ImageSize to 5120K and give ourselves some much-needed room for expansion
Admin:
  Tested in Tungsten ROM build & softload


Version 1.17. Tagged as 'Env-1_17'

Change UserIF for OMAP3.
Add missing title blocks to others.

Version 1.16. Tagged as 'Env-1_16'

Version 1.15. Tagged as 'Env-1_15'

Admin:
  Submission from Willi Theiß

Version 1.14. Tagged as 'Env-1_14'

Detail:
  These use Machine=32 and Machine=ARM11ZF respectively
Admin:
  Based on a code submission from Tom Walker

Version 1.13. Tagged as 'Env-1_13'

Detail:
  HALSize is a new environment variable supported by the OMAP3 HAL & Cortex kernel. As you'd expect, it's used to indicate the size of the HAL.
  The variable is actually used to select from one of several HALSize files in HdrSrc, much like the ImageSize variable.
  The OMAP3 env file is set to use a 96K HAL, the other builds are set to 64K.
  Apart from changing the HALSize setting, currently you also have to remember to change the Kernel offset in the corresponding components file.
Admin:
  Needed for my next batch of checkins to work.


Version 1.12. Tagged as 'Env-1_12'

If these apps were already booted in a different build then the filer boot
in a new build does nothing (e.g. you'll still be using the apps in the
original build in your new build). This is a particular problem if the old
build has been deleted in the mean time...

Version 1.11. Tagged as 'Env-1_11'

Version 1.10. Tagged as 'Env-1_10'

Detail:
  Added shell-script equivalents of !Common and two Env files.
Admin:
  Tested by building the DDE tools on Linux.

Version 1.09. Tagged as 'Env-1_09'