[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [bluetooth-dev] a few build issues
> -----Original Message-----
> From: Gordon McNutt [mailto:email@example.com]
> Sent: Monday, March 12, 2001 23:30
> To: firstname.lastname@example.org
> Subject: [bluetooth-dev] a few build issues
> 1. I'm thinking of moving the CONFIG_BLUETOOTH from bluetooth/Config.in
> up to char/Config.in, and then sourceing bluetooth/Config.in only when
> it is not "n". This will allow me to leave the char/Makefile untouched
> when I remove/replace my link to the bluetooth CVS repository. Does
> anybody see a problem with that approach?
Why do you have to modify char/Makefile? I can see that you need to modify
the file that includes bluetooth/Config.in, but not the Makefile. Actually,
'make config', 'make oldconfig' and 'make xconfig' all handle the lack of
a Config.in file without problems. 'make menuconfig', however, does not :(
I think I prefer to have all the Bluetooth related configuration options
together in one file. You could always add an extra option in your kernel
tree to allow Bluetooth configuration at all.
> 2. Although we just recently added the -MD option to gcc for automatic
> dependency generation, the kernel builds dependencies with the 'dep'
> target. Does anyone know why the kernel uses 'dep' instead of -MD? Is it
> to speed up kernel builds? And do we want to conform to that practice
> instead of using -MD?
I see no reason for this. Though, I wish the .d files had been hidden :(
To unsubscribe from this list: send the line "unsubscribe bluetooth-dev" in
the body of a message to email@example.com