prepare.sh:
Don't pass --remote to the 'git submodule update'.
We want the boehm_gc submodule to be checked out at the commit
recorded in the mercury repository, not automatically update to the
latest commit on the branch listed in .gitmodules. Similarly for
libatomic_ops within the boehm_gc submodule.
Fix help message.
Feedback of the upgrade of Boehm GC indicated that including the
libatomic_ops submodule in the top-level was inconvenient, and I agree.
This change, along with a corresponding change to the boehm_gc repository,
will instead included it as a nested submodule of boehm_gc.
.gitmodules:
libatomic_ops:
Remove libatomic_ops submodule.
boehm_gc
Update to the most recent revision that adds a libatomic_ops submodule.
prepare.sh:
Update submodules recursively.
Mmakefile:
scripts/prepare_install_dir.in:
tools/bootcheck:
Remove code in build tools that links or copies the libatomic_ops
directory from Mercury's top-level,
This change adds the boehm_gc and libatomic_ops code as git submodules.
This is analgous to a symbolic link: it's a referece to these external
repositories.
To make things easier, the libatomic_ops submodule is included directly in
Mercury rather than via the boehm_gc submodule. This makes configuration of
the submodules centralised and a little simpler.
.gitmodules:
boehm_gc:
libatomic_ops:
As atove.
prepare.sh:
Add a script that will initialize and checkout the submodules, create a
symbolic link from boehm_gc/libatomic_ops to libatomic_ops and
prepare the configure script.
