--TOmSpbqtysumMR8M
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi all.

Our current Makefile infrastructure supports the following
"common" object file suffices:

	.o	"standard" objects
	.po	profiled objects; "cc -pg ..."
	.so	PIC objects; "cc -fPIC -DPIC ..."
	.lo	host objects (for tools, etc)
	.ro	relocatable objects for crunchgen (?); "ld -r -dc ..."
	.so	shared libraries; "ld -x- shared ..."

There's been a suggestion from Nick Hudson to rework this slightly:

    *	Use .ho instead of .lo for host objects.

    *	Use .lo instead of .so for PIC objects,
    	thus reserving .so for shared libraries.
	I would have considered .po ("PIC objects") or
	.ro ("relocatable objects"), except that they're already taken.=20
	I don't like .Po.

This would result in:

	.o	"standard" objects
	.po	profiled objects; "cc -pg ..."
	.lo	PIC objects; "cc -fPIC -DPIC ..."
	.ho	host objects (for tools, etc)
	.ro	relocatable objects for crunchgen (?); "ld -r -dc ..."
	.so	shared libraries; "ld -x- shared ..."

If we're considering changing this, is there prior art in other
systems (e.g, the GNU toolchain, libtool, ...) for purpose specific
object suffices ?

Thoughts / other comments?

Cheers,
Luke.

--TOmSpbqtysumMR8M
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFBdxXZpBhtmn8zJHIRAlibAJ4kL30T98n3e9zuN39WmtXYqeObqQCglqXQ
NX/Wlt7Lptfs+D0eiA/MlFE=
=4SFM
-----END PGP SIGNATURE-----

--TOmSpbqtysumMR8M--