<html><body><div style="color:#000; background-color:#fff; font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:12pt"><div><span><br></span></div> <div class="qtdSeparateBR"><br><br></div><div style="display: block;" class="yahoo_quoted"> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 12pt;"> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 12pt;"> <div dir="ltr"> <font face="Arial" size="2"> On Wednesday, June 18, 2014 6:47 AM, Anders Darander <anders.darander@gmail.com> wrote:<br> </font> </div> <br><br> <div class="y_msg_container">On 18 June 2014 15:03, John Bougs <<a ymailto="mailto:bogusemail98230@yahoo.com" href="mailto:bogusemail98230@yahoo.com">bogusemail98230@yahoo.com</a>> wrote:<br>> I am working with a kernel module that has a few kconfig options
associated<br>> with it. The makefile for the module as it is does not support out-of-tree<br>> builds. I am trying to change the the makefile to do out-of-tree builds.<br><br>First, why do you want to build the module out-of-tree?<br><br>For 3rd party modules I can understand that need, OTOH, in that case your<br>question wouldn't have existed.<br><br><br>I am working with a third party module that I am building out of tree. I trying this across multiple platforms. I am placing the module code in our VCS... out of tree seems to be a cleaner, simpler, les complicated solution to me.<br><br>Without trying to sound confrontational, why not build it out of tree?<br><br><br><br></div> </div> </div> </div> </div></body></html>