Luis R. Rodriguez wrote: > On Thu, Aug 6, 2009 at 9:41 AM, Pavel Roskin<proski@xxxxxxx> wrote: >> On Thu, 2009-08-06 at 09:46 -0500, Jon Loeliger wrote: >>> On Thu, 2009-08-06 at 01:08 -0700, Philip A. Prindeville wrote: >>>> Who currently owns CRDA? >>>> >>>> I started to stare at cross-compiling issues, but realized that we need >>>> two versions of reglib.o and print-regdom.o... >>>> >>>> One to link with regdumpdb (compiled with HOSTCC) and one to link with >>>> everything else (compiled with TARGET_CC)... >>>> >>>> No easy way to do this without a lot of changes. >>> I posted a 5-part patch series to address this issue. >>> To the best of my knowledge, it has not been applied yet. >>> >>> You can find it here: >>> >>> http://article.gmane.org/gmane.linux.kernel.wireless.general/35350 >> I objected against using the misleading use of the "TARGET" work in some >> variables, but there was no reaction. Failure to react to objections is >> the likely reason it wasn't applied. > > Indeed. > >> I also think that you add too much complexity to the Makefile. > > Agreed. > >> Also, the use of .config is not common. Most valuables can be specified >> on the command line. That would override the definitions in Makefile, >> and that's how it's done. > > Yeah for something so simple as CRDA it seems overkill to have a .config. > >> For instance, you can have this in Makefile: >> >> HOSTCC = gcc >> CC = $(HOSTCC) >> >> Running "make CC=/opt/mips/bin/gcc" would override CC but not HOSTCC. > > ACK, is it possible to make it simpler? > > Luis You could also have: -include .config HOSTCC ?= gcc ... and that will only set (default) the unset variables... -Philip -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
