Hi, On Sáb, 2015-09-12 at 18:31 -0400, W. Michael Petullo wrote: > I am interested in doing some kernel development on Fedora. I am familiar > with kernel internals, but I am looking for some tips to help manage the > build, compile, and install cycle. Unfortunately, I am developing against > the Linux Security Module interface, so my work cannot take the form of > a kernel module. > > I would like to build RPMs because they are convenient to install, > and they manage the kernel configuration for me. Put another way, I > would like for practical reasons to track the Fedora kernel source RPMs > as opposed to the upstream kernel tree. (This will eventually change, > but not yet.) However, building RPMs results in a full build each time, > slowing down the development cycle. > > I thought that I could speed this up using rpmbuild's --short-circuit. > My idea was to perform an "rpmbuild -bp" once, apply my own changes to > the build tree, and then on each compile run "rpmbuild -bc", "-bi", and > "-bb". The problem is that the RPM build runs "make mrproper" as part > of the %build target. > > Does anyone know of a good work flow for developing custom kernel code > on Fedora in a convenient way? The next best thing I could come up with > is to recreate much of the kernel RPM's %build target without the "make > mrproper" and other troublesome parts. But this sort of duplicates things > that I would rather dynamically track by making use of each kernel RPM. Google for "fedora custom kernel" https://fedoraproject.org/wiki/Building_a_custom_kernel And here is my own notes: How to patch and building a kernel for Fedora http://www.serjux.com/build_kernel/build_kernel.txt > Thank you, > > -- > Mike > > :wq -- Sérgio M. B. -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
