--=-=-=
Content-Transfer-Encoding: quoted-printable


Gary Thorpe <gathorpe79@yahoo.com> writes:

> Is it possible to share the build directories for different
> architectures such that some common parts (e.g. manual pages) do not
> have to be built more than once? Would this be a major space-saver or
> at least a major time-saver?

I don't think it's possible.

> Would setting the object directory with -O (for build.sh) to a common
> place for different architectures work or just overwrite the objects
> each time a different architecture is built (I don't see any prefix or
> postfix on the objects as in the TOOLDIR)?

I don't think this will work; make rules then won't know that the
non-sharable objects need rebuilding for the next architecture.

It might be possible to have OBJDIR and SHAREOBJDIR, where SHAREOBJDIR
is used for things that are the same for all archs.  This would
require introducing the concept, defaulting SHAREOBJDIR to OBJDIR, and
adjusting makefilesto use it when appropriate.

Another optimization (that might be easier) would be to make the
OBJDIR for tools not be duplicated; currently one seems to get
multiple tools obj files, even though they are all for the host.

It's not clear to me how much of the build time is from running nroff.
It would be cool to write a script to run the output of build.sh into
to timestamp and analyze such things, if you're in the mood.

=2D-=20
    Greg Troxel <gdt@ir.bbn.com>

--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (NetBSD)

iD8DBQFE/reU+vesoDJhHiURAtQqAJ9wdVo70k1Tg0P5KDWEYpqc/JdJmgCfVUMH
MrcvFNNC9IZr9FzxvpgUMRQ=
=r2/C
-----END PGP SIGNATURE-----
--=-=-=--