GitLab

Missing `$` character before `{LOCALE}` would have caused UK resources to
be selected instead of non-UK ones, if anyone were to be doing an
internationalised cross-compiled build.

This allows RISC OS abstract data files with filetype ffd to be referenced
identically whether native or cross-compiling (it expands to an empty string
when used natively).

This only applies to cross-compilation builds. The `make links` rules don't
know a pre-determined list of subdirectories that need to be converted into
filename extensions. Instead, files that should have no filename extension
are usually simply identified by the absence of a `/` in their specification
in `SOURCES_TO_SYMLINK`. However, this is insufficient to handle some rarer
cases, such as a `Makefile` within a `Test` subdirectory.

To handle this, we introduce explicit support for specifying such files in
`SOURCES_TO_SYMLINK`, using a double slash where there would otherwise be a
filetype subdirectory name, such as `Test//Makefile`. (Conveniently, this is
also valid Posix filename syntax anyway.) The way this is achieved is to
tweak the regular expressions to require the directory and leafnames between
slashes to be at least one character long.

Version 7.58. Tagged as 'BuildSys-7_58'

With GNU `make` unlike with `amu`, it is considered an error to make a target
for which no rule is defined. Therefore we need an explicit no-op `export`
rule in the cross-compiling `CApp` makefile.

`AAsmModule`, `CApp`, `CLibrary` and `CModule` implicitly include various
other shared makefile fragments to permit simpler master makefiles. However,
when cross-compiling, they were only included when invoked from within the
`objs` subdirectory, which in particular meant you couldn't rely on any of
the definitions from `StdTools` when extending the `clean` rule unless you
explicitly included it from the master makefile, thereby defeating the
purpose of the implicit inclusion. Change them so that `StdTools` is included
for all rules.

This tells it to use gcc for preprocessing the CMHG file (if enabled) and
asasm for the backend (which means the object file is an ELF file, required
in order to link with GCC objects).

Occasionally, it is useful to be able to set C++FLAGS from the calling
environment, for example when building a 32-bit x86 target from a 64-bit
x86-64 host. This works fine for CFLAGS and LDFLAGS, but C++FLAGS is not a
valid Posix environment variable name. Import setting from CXXFLAGS instead
when cross-compiling.

When executing the makefile from within the `objs` directory, this now
includes an implicit `-C..` option. This makes it simpler to write agnostic
makefiles. For example,

	${MAKE} -f other${EXT}mk other_target

rather than

ifeq (,${MAKE_VERSION})
	${MAKE} -f other/mk other_target
else
	${MAKE} -f ../other.mk other_target
endif

Earlier versions couldn't cope with RES_OBJ being set to an empty string.

This allows makefiles to refer to the parent directory in an OS-neutral way.

`TOKHELPSRC`, `HELPSRC` and `TOKENS` have the same meaning as in `AAsmModule`.
Because `CModule`, unlike `AAsmModule`, can build a binary from multiple
linked object files, it is also necessary to specify which object file(s)
depend on the autogenerated source file. This is achieved with the new input
variable `TOKHELPDEPENDS`. This defaults to `OBJS` which in turn defaults to
`TARGET`, which should mean that any components converted from `AAsmModule`
will not require any such line to be specified in their master makefile.

Requires RiscOS/Sources/Programmer/Debugger!4

This allows Perl files with filetype 102 to be referenced identically whether
native or cross-compiling (it expands to an empty string when used natively).

This brings it into line with AAsmModule and CModule shared makefiles

There are at least 19 components that use this tool to autogenerate a source
file. Needs initial capitalisation on case-sensitive filesystems.

Use `${TBOXINC}` instead.

Use `${TCPIPINC}` instead. Although there is only a single directory
on TCPIPLibs$Path, all ported BSD sockets code assumes their headers are
already directly on the include path.

Typically useful for libraries where you have both types of target, and you
want the application build to contain function names (for meaningful
backtraces) but the module build not to (to save ROM space). This is
achieved as follows:

* CAPPFLAGS and CMODFLAGS contain additional flags to be passed to application
  and module builds, respectively

* C_FNAMES is initialised to a compiler-agnostic build switch to enable
  function names in the binary

Therefore a master makefile will often use the line
CAPPFLAGS = ${C_FNAMES}
although CAPPFLAGS and CMODFLAGS are not limited to this usage.

Occasionally, a library needs to export additional files that don't live in
either an h or hdr directory and (when cross compiling) shouldn't have a
.h suffix added to their exported version. A typical example would be where
the licence conditions of the library require a licence header to be attached
to all copies. To achieve this, CLibrary now uses EXPORTS in a similar manner
to how AAsmModule does, simply as a dependency of export_hdrs, which can
expand to any additional targets you need to define. By default, it overrides
the internal targets EXPORTING_HDRS and EXPORTING_ASMHDRS (derived from
HDRS and ASMHDRS supplied by the master makefile), but you can always include
them in your definition of EXPORTS if desired.

This de-duplicates some of the information from AppLibs and ModuleLibs,
which now include the new Makefile fragment in order to ensure compatibility.
It also means that the definitions can be used for building other library
components, which by definition do not perform a link step, without having
to choose either AppLibs or ModuleLibs when most of either one is unused for
a library build.

For iMx6, remove DDEUtils to match the other ROMs (it's in the HardDisc4 image).

Version 7.57. Tagged as 'BuildSys-7_57'

Requires Env-1_46

Version 7.56. Tagged as 'BuildSys-7_56'

Version 7.55. Tagged as 'BuildSys-7_55'

Detail:
  ModuleDB updated to make Obey and Shell as 'C' for ROM builds

Version 7.54. Tagged as 'BuildSys-7_54'

Help2-3_27 now uses the CApp shared makefile.

Version 7.53. Tagged as 'BuildSys-7_53'

Exercising the new library/symbols selector on a more complex case (Help2) showed that the selection never triggered, because where it is placed ${RLIB} is unset.
Move the test to after ModuleLibs/AppLibs are set, and invert the sense (it should have been ifneq).

Version 7.52. Tagged as 'BuildSys-7_52'

To CTools, for Installer, fixes build as for BuildSys-7_48.

Version 7.51. Tagged as 'BuildSys-7_51'