1. 28 7月, 2005 1 次提交
    • S
      kbuild: fix building external modules · db8c1a7b
      Sam Ravnborg 提交于
      kbuild failed to locate Makefile for external modules.
      This brought to my attention how the variables for directories
      have different values in different usage scenarios.
      
      Different kbuild usage scenarios:
      make       - plain make in same directory where kernel source lives
      make O=    - kbuild is told to store output files in another directory
      make M=    - building an external module
      make O= M= - building an external module with kernel output seperate from src
      
      Value assigned to the different variables:
      
                 |$(src)          |$(obj) |$(srctree)        |$(objtree)
      make       |reldir to k src |as src |abs path to k src |abs path to k src
      make O=    |reldir to k src |as src |abs path to k src |abs path to output dir
      make M=    |abs path to src |as src |abs path to k src |abs path to k src
      make O= M= |abs path to src |as src |abs path to k src |abs path to k output
      
      path to kbuild file:
      
      make       | $(srctree)/$(src), $(src)
      make O=    | $(srctree)/$(src)
      make M=    | $(src)
      make O= M= | $(src)
      
      From the table above it can be seen that the only good way to find the
      home directory of the kbuild file is to locate the one of the two variants
      that is an absolute path. If $(src) is an absolute path (starts with /)
      then use it, otherwise prefix $(src) with $(srctree).
      Signed-off-by: NSam Ravnborg <sam@ravnborg.org>
      db8c1a7b
  2. 27 7月, 2005 3 次提交
  3. 26 7月, 2005 4 次提交
  4. 25 7月, 2005 2 次提交
  5. 22 7月, 2005 2 次提交
  6. 18 7月, 2005 1 次提交
  7. 15 7月, 2005 11 次提交
  8. 14 7月, 2005 8 次提交
  9. 13 7月, 2005 1 次提交
  10. 12 7月, 2005 7 次提交