On Thu, Feb 23, 2006 at 12:24:09PM +0100, Marc Haber wrote:
> > The build process is something that is being worked on very heavily.
> > So yes there is ample room for improvement. And one area that is
> > particularly lacking is documenation. Contributions in that area
> > would be greatly welcomed.
>
> The build is a lot of make magic, something I am not very familiar
> with. And it is hard for me to fine a starting point for investigation.
It uses less make magic than cdbs.
> > One caveat, is that if you play with stuff before running
> > dpkg-buildpackage, which I guess you would else you won't be
> > here,
>
> That guess seems to be correct. In particular, I'd like only three
> flavors of the kernel to be built, all of them for i386, but with my
> own .config file.
Edit debian/arch/defines and remove anything from the arches
specification what you don't want. Also edit debian/arch/i386/defines to
only include what you want. You may also rename the flavours to
something other to avoid clashes with the official names.
> > > * How do I control generation of the
> > > kernel-image-2.x-<flavour>_2.x.y-z_<arch>.deb helper packages?
> > > They do not seem to be controlled by debian/arch/<arch>/defines
> > > as the real kernel debs do.
> >
> > What about them do you want to control?
>
> I would probably like to disable their generation.
Edit debian/templates/control.extra.
> > > * Are there hooks for building external modules?
> >
> > No
>
> Too bad.
Not yet.
> > > * Are there debian/rules parameters or environment variables to
> > > select only a certain kernel to be built (like for debugging
> > > problems)?
> >
> > No. If you are talking about linux-2.6, then edit
> > debian/arch/$ARCH/defines. Near the top is a list of flavours
> > that will be built. Remove the ones you don't want, and then run
> >
> > rm -f debian/control
> > ./debian/rules debian/control
>
> Thanks.
Call debian/rules.gen directly. If you want to build the k7 kernel, use
fakeroot make -f debian/rules.gen binary-arch-i386-none-k7.
> > > * I think it is necessary that a patch file contains information
> > > * what does the patch do?
> > > * why is it applied?
> > > * is it necessary only on certain archs?
> >
> > Yes, thats why it says amd64. Its applied to all arches, but
> > it only affects amd64.
>
> Would that be true for all patches with names starting with an arch
> name?
Should be.
Bastian
--
The more complex the mind, the greater the need for the simplicity of play.
-- Kirk, "Shore Leave", stardate 3025.8
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
