|
From: | Stuart Hughes |
Subject: | Re: [Ltib] Handling PKG_KERNEL_LEAVESRC? |
Date: | Wed, 15 Feb 2012 10:01:54 +0000 |
User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.26) Gecko/20120131 Lightning/1.0b2 Thunderbird/3.1.18 |
Hi Mike, The philosophy is that unpacked source is never clobbered.To do what you want, you would be better to have your kernel source code outside ltib (under git control etc).
To do this, run ./ltib -m config and under "choose your kernel", select "Local Linux directory build", you can then point ltib to use your SCM control kernel tree. When you're done, you can roll it up (as a patch against the original or whatever makes senses).
Regards, Stuart On 15/02/12 00:00, Mike Goins wrote:
Wondering if anyone else has this particular type of situation. I setup a continuous integration system involving ltib. ltib also builds kernel modules outside the source tree, so I have PKG_KERNEL_LEAVESRC=y so the modules can build. But when the kernel spec is updated, ltib refuses to colbber the existing kernel build directory and apply the updated spec (usually new patches). I guess what I would like is if the the spec file is updated and ltib detects a "directory build", is to go ahead and automatically clobber. Now sure where I can make this modification to ltib. Or is there some other way to accomplish this?
[Prev in Thread] | Current Thread | [Next in Thread] |