[Build-common-hackers] Proposals for multi-build
27 Jul 2003 16:53:57 -0400
On Wed, 2003-07-23 at 17:10, Jeff Bailey wrote:
> My initial proposal is that all of our variable access switch to using
> this syntax where it's reasonable that the caller might either user foo
> or foo_$(cdbs_curpkg).
This seems reasonable to me.
> I'm assuming here that all builds define DEB_BUILD_MULTI. If the user
> doesn't specify it, then we just fille it with the name of the first
> package and proceed.
Hm. Will this cause any problems for source packages which build
multiple .debs but don't need multi-build?
> DEB_BUILD_makefile = $(DEB_BUILD_MULTI)
> $(call cdbs_localval,DEB_MAKE_INVOKE) $(call cdbs_localval,DEB_MAKE_BUILD_TARGET)
Ok...that could work. BTW, we don't need to do the $(call ...) stuff.
It should work to just put this inside the variable, and let recursive
variable referencing do the work.
> I think that doing it this way means that the multi-build stuff will
> work without any changes to the buildcore.mk file. We're *already*
> calling these targets. The only issue then is that we don't run a make
> clean between runs, so they need to do VPATH builds. This is probably
> solvable somehow, too, but I haven't thought about it.
That is a hard part.
> Any comments? If this looks good, I can dig in on it.
I'm cool with trying it, definitely. If it really doesn't work we can
back it out, and we'll have learned something from it anyways.