Sam Ravnborg wrote:
KERNELSRC equals /usr/ammasso/src/sles9/2.6.5-32smp in your example KERNELOUTPUT equals ??? in your example
KERNELOUTPUT = $KERNELSRC. There's a reason why it's called an "external" module. My module is not built with the kernel.
You may say it is inconsistent, improvements are welcome.
This is what I think kbuild needs:
1) The ability to compile an external module and specify where the targets go.
2) The ability to compile an external module without writing to the kernel source tree. In a group development environment, it's normal to have one kernel source tree that's been mounted read-only and that all developers share. With kbuild, each developer needs to have write access to the source tree because a whole bunch of stuff (I have no idea what) is written to the source tree, even when compiling an external module. This is bad, very bad.
-- Timur Tabi Staff Software Engineer [EMAIL PROTECTED]
------------------------------------------------------- This SF.Net email is sponsored by: InterSystems CACHE FREE OODBMS DOWNLOAD - A multidimensional database that combines robust object and relational technologies, making it a perfect match for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 _______________________________________________ kbuild-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kbuild-devel
