<z3ntu>
bamse: With `CONFIG_QRTR=m` is it meant that both `qrtr.ko` and `ns.ko` exist? Or should the ns parts be built into `qrtr.ko`?
<bamse>
z3ntu: that sounds like a really good idea, thought they were built into the same module
<z3ntu>
I can prepare a patch :)
<z3ntu>
qrtr.ko depends on ns.ko but I doubt anybody will want to have ns.ko loaded without qrtr.ko :D
<bamse>
right
<minecrell>
z3ntu: it's quite difficult to get a module named qrtr.ko which includes multiple C code files if you also have a qrtr.c file :/
<z3ntu>
Right, I'm getting `make[1]: *** No rule to make target 'qrtr.o', needed by 'modules-only.symvers'. Stop.` ...
<minecrell>
I ran into this problem several times before and it's rather frustrating. The only clean way seems to use a module name that does not exist as source file as well :(
<z3ntu>
scratch my previous message
<z3ntu>
with "obj-$(CONFIG_QRTR) := qrtr.o" "qrtr-y:= ns.o" qrtr.c isn't getting compiled which is probably what you mean
<minecrell>
AFAIK if you do qrtr-y := ... you're basically overriding the rule that normally builds qrtr.o from qrtr.c
ahalaney has quit [Remote host closed the connection]