Date: Sun, 9 Mar 2003 12:48:48 -0600 (CST) From: Jonathan Lemon <jlemon@flugsvamp.com> To: leafy@leafy.idv.tw, current@freebsd.org Subject: Re: How does a module decide what to support? Message-ID: <200303091848.h29Imm4S028389@mail.flugsvamp.com> In-Reply-To: <local.mail.freebsd-current/20030309171452.GA2510@leafy.idv.tw>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <local.mail.freebsd-current/20030309171452.GA2510@leafy.idv.tw> you write: >From my observations (yes, please correct me if I am wrong), that >modules define what to support in their respective makefiles in the form >of > >SRC= aaa.c bbb.c opt_*.h > >Where opt_*.h are automagically generated if they are not in machine@ >(and the generated files are just empty files that indicate that the >kernel file does not specify this option), else they are linked from >machine@. > >If some makefile list >SRC= a.c b.c opt_inet.h opt_inet6.h >and kernel config lists 'option INET' *only*, then opt_inet.h has >'#define INET 1' in it and opt_inet6.h is empty. > >Is this correct? Yes, I believe so. This is why module makefiles should explicitly create the opt_* files with the #define set, so the module supports all options. See the recent commits I did to the if_tun module, for example (thanks for pointing it out). -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200303091848.h29Imm4S028389>