* kbuild: building external module in separate output directory
@ 2013-02-13 15:28 Yann Droneaud
0 siblings, 0 replies; only message in thread
From: Yann Droneaud @ 2013-02-13 15:28 UTC (permalink / raw)
To: kernelnewbies
Hi,
With kbuild, we can build external modules using:
make -C $KERNEL_BUILDDIR M=$PWD
But I'm looking for the proper way to not clobber my module source
directory with files from the build, eg. I'd like the build to output
the files in another directory.
I'd like to do:
mkdir obj-$ARCH
cd obj-$ARCH
make -C $KERNEL_BUILDDIR M=$PWD/.. O=$PWD
But O= is not supported for external module. It can only be used when
building the kernel (and its modules) itself.
I have found people explaining that the currently only way is to
copy/link the sources inside the object directory.
But I find this tasteless and error prone.
Do someone know another method or a patch to the kbuild system to
improve external module compilation ?
Regards.
--
Yann Droneaud
OPTEYA
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2013-02-13 15:28 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-02-13 15:28 kbuild: building external module in separate output directory Yann Droneaud
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).