On Tue, Nov 11, 2008 at 08:44:08PM +0100, Jonas Smedegaard wrote: > Hi, > > On Tue, Nov 11, 2008 at 01:08:34PM -0600, Steve M. Robbins wrote: > >It would be nice if I could either set some variable like > >DEB_MAKE_PARALLEL=yes, or use something like > > include /usr/share/cdbs/1/rules/parallel.mk > >and be finished. > > Thanks for raising this topic. > > > Both these concrete proposals fail to support the (corner) case of a > package using 2 build systems simultaneously, only one of them > supporting parallel builds.
I'm having trouble understanding what you mean. Do you mean a package that uses cdbs to build both a make-based and a cmake-based component? Or 2 make-based components? Is this a common use case? Maybe the answer could be: "don't use the easy cdbs parallel build, but roll your own" ? > >Failing that, I need some way to pass a -jN flag to the initial make > >invocation. > > >The recommended practice is to supply -jN *only* to the initial > >invocation of make. > > I suggest adding the options DEB_MAKE_BUILD-OPTIONS, > DEB_MAKE_INSTALL_OPTIONS, DEB_MAKE_CHECK_OPTIONS and > DEB_MAKE_CLEAN_OPTIONS. > > all of those options would be blank by default (to ensure backwards > compatibility for packages not supporting parallel build). In a next > major version of cdbs we can enable parallelism by default. Did you really mean "by default"? The Policy Manual [1] suggests that parallel=n only be honoured if the package build system supports parallel builds. Or maybe you meant "by default" to mean "if the packager signals in some way" -- like by including "rules/parallel.mk" or something. Whatever you meant: how do you forsee solving the objection you raised to my first two suggestions (include parallel.mk, or set DEB_MAKE_PARALLEL=yes)? Cheers, -Steve [1] http://www.debian.org/doc/debian-policy/ch-source.html#s-debianrules-options
signature.asc
Description: Digital signature
