suppose I have modules A,B,C, where C is Common, ie both A, B are dependent upon it.
IIUC, this Makefile addition will work, C.ko will be built if either of A or B are, and wont be compiled 2x. obj-$(A) += A.o C.o obj-$(B) += B.o C.o But, it would be bad if a user tried to configure A as built-in and B as modular; A will want C built-in, but B will want it as a module. Linker errors are likely to ensue. How to use kbuild dependencies to prevent this ? AFAICT, dependencies control the presentation of config items, but not not the tristate vs bool characteristics.. ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ kbuild-devel mailing list kbuild-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kbuild-devel
