On Sat, Nov 13, 2004 at 02:58:03PM -0600, Timur Tabi wrote:
> 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.
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=
> 2) The ability to compile an external module without writing to the
> kernel source tree.
This is indeed supported.
Say you have kernel source located at:
/.../repository/kernel/2.6
And you want ouput files for the -kernel- placed in ~/my-kernel
Then you do:
$ md ~/my-kernel
$ cd /.../repository/kernel/2.6
$ make O=~/my-kernel *config
$ make O=~/my-kernel modules_prepare
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`
What do you miss?
PS. Fixed my mailer so from: address is OK now.
Sam
-------------------------------------------------------
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
