On Windows:
- Items starting with -l are ignored
- Everything else is treated as an ASCII library file

On other platforms:
- Items starting with -l are treated as shared libraries
- Items containing a dot are treated as normal files and linked
- Other items are ignored

This allows one to use for example:

	import code from library "mylib_library"
	import code from library "-lmylib"

(where Clean System Files\mylib_library refers to mylib.dll or so).
The first entry is used on Windows; the second on non-Windows.

Create separate stages for optimising ABC and generating bytecode, so that the timestamps of these files differ for large projects

Previously an imported object file:
```
implementation module test.test

import code from "obj.o"
```

Would only search in the roots of the project paths. Now it will als
search in the test/ folder in the root.

Add EnvironmentByteCodePrelink and PrelinkByteCode options to prelink bytecode for use with the WebAssembly interpreter

in project files for modules in a directory write the directory once, instead of per module (to reduce problems caused by version control systems)

saveEnvironments (now saveEnvironmentsStupArg),
to reduce the number of GetFullApplicationPath calls in BatchBuild
  

use same separator characters in project and application relative paths in project files on all platforms,
add list of other paths containing project modules