So, mk.conf(5) used to give some interesting ideas about what a
$(BUILDID), i.e. as set by "build.sh -B BUILDID" could be used for:
... can be consulted in the make(1) configuration file in order
to set additional build parameters, such as compiler flags.
This made me think it would be useful for creating variant releases,
such as one with (or without) INET6 enabled, for example.
However as implemented it doesn't go nearly far enough -- it only
affects $(OBJDIR) but to be useful for variant releases it would have to
also be appended to $(DESTDIR) and either to $(RELEASEDIR), or to some
other similar place where resulting release sets could be identified by
variant.
Now obviously these could be changed easily with a build.sh wrapper, but
it would seem to me that the "-B BUILDID" as an option to build.sh
should make this more useful without needing extra logic outside
build.sh.
I note that the change to remove the text above was done by lukem@ on
2023/07/22 with only the comment:
Clarify BUILDID behaviour with OBJMACHINE, and remove unnecessary sentence.
So, I agree the sentence was "unnecessary" given the current
implementation, but maybe it would be nice if it could be more
completely implemented and added back?
What, if anything, is anyone currently using $(BUILDID) for?
--
Greg A. Woods <gwoods%acm.org@localhost>
Kelowna, BC +1 250 762-7675 RoboHack <woods%robohack.ca@localhost>
Planix, Inc. <woods%planix.com@localhost> Avoncote Farms <woods%avoncote.ca@localhost>
Attachment:
pgpt46dnl65J_.pgp
Description: OpenPGP Digital Signature