Sam Ravnborg wrote:
Today it is not possible to tell kbuild to store output files in a different directory when building external modules. So for an external module located in .../external/foo output files for the module will be stored in ../external/foo no matter usage of O=
I understand that now, and I think that needs to change.
Now you have a kernel ready for building external modules So you shift to your external module dir and do: make -C /.../repository/kernel/2.6 O=~/my-kernel M=`pwd`
Ah, I get it. Now I see the real value of O=. I'll pass this along to my developement team. Thanks!
------------------------------------------------------- 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
