Changes between Version 4 and Version 5 of Linux/Ubuntu/Kernel/BuildDebianDKMSPackages


Ignore:
Timestamp:
22/07/08 23:00:00 (9 years ago)
Author:
tj
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Linux/Ubuntu/Kernel/BuildDebianDKMSPackages

    v4 v5  
    4040The primary issue is the Makefile detection of an in-tree or out-of-tree build. It is often done by checking for an empty/undefined variable that is always set by Kbuild (the kernel build system). 
    4141 
    42   E.g. 
    43   {{{ 
     42 E.g. 
     43{{{ 
    4444ifneq ($(KERNELRELEASE),) 
    4545include $(src)/Kbuild 
     
    4747 
    4848all:: 
    49   }}} 
     49}}} 
    5050As I discovered after several hours of frustration when DKMS failed to build the package, detecting '''KERNELRELEASE''' ''causes the DKMS build to fail''. I'll spare the explanation but I found that detecting an alternative variable, '''PATCHLEVEL''', solved this issue. 
    5151 
     
    163163As a further enhancement I usually suffix the ~ppaX version with a single letter that represents the release the package is for. This solves an annoying issue when building the same package for multiple releases (e.g. gutsy, hardy, intrepid) where the packages would otherwise have to have different version-numbers in order for the PPA to accept them. So: 
    164164 
    165  * '''h''' = The release this package is for (g = Gutsyt, h = Hardy, i = Intrepid, etc.) 
     165 * '''h''' = The release this package is for (g = Gutsy, h = Hardy, i = Intrepid, etc.) 
    166166 
    167167I wrote the [wiki:PPAPublish ppa_publish shell script] to automatically build and publish source packages to the PPA for multiple releases.