| Weekly edition | Kernel | Security | Distributions | Search |
| Archives | Calendar | Subscribe | Write for LWN | LWN.net FAQ |
Driver porting: compiling external modules
Driver porting: compiling external modules
Posted Jul 11, 2004 6:23 UTC (Sun) by kcannon (guest, #4867)Parent article: Driver porting: compiling external modules
It's probably better to use $(CURDIR) in the Makefile rather than $(PWD). $(PWD) is set to the directory from which the original make command was issued, while $(CURDIR) is set to the current working directory (eg. as modified by recursive use of make -C). If the driver modules are distributed in a subdirectory of a larger software package, and the user is intended to issue a make command from the top-level directory, using $(PWD) in the driver Makefile will pick up the wrong path.
Cheers
-Kipp
(Log in to post comments)
Driver porting: compiling external modules
Posted Jul 12, 2004 2:20 UTC (Mon) by kcannon (guest, #4867) [Link]
Never mind... my mistake. You replace the default value of PWD with the result of $(shell pwd).
problem with $(CURDIR)
Posted Jul 31, 2005 20:42 UTC (Sun) by qu1j0t3 (subscriber, #25786) [Link]
The GNU make docs say that $(CURDIR), when used with -C, will be the 'new' directory, not the module directory, which would make it incorrect in this situation anyway... I think :-)