From mboxrd@z Thu Jan  1 00:00:00 1970
From: ydroneaud@opteya.com (Yann Droneaud)
Date: Sat, 08 Dec 2012 19:16:08 +0100
Subject: question about building a module
In-Reply-To: <CAHdPZaOWeqAS1sHHMYRY=f5iUAqDiGSzH2+bJyxWreQQSSmjZQ@mail.gmail.com>
References: <CAGXs5wW1kzfkVpVgOfyQWfeRwkb0g6dME9e=njOXtUENy0iNNA@mail.gmail.com>
	<1354953796.27902.9.camel@test.quest-ce.net>
	<CAHdPZaOWeqAS1sHHMYRY=f5iUAqDiGSzH2+bJyxWreQQSSmjZQ@mail.gmail.com>
Message-ID: <1354990568.27902.13.camel@test.quest-ce.net>
To: kernelnewbies@lists.kernelnewbies.org
List-Id: kernelnewbies.lists.kernelnewbies.org

Le samedi 08 d?cembre 2012 ? 04:02 -0500, devendra.aaru a ?crit :
> On Sat, Dec 8, 2012 at 3:03 AM, Yann Droneaud <ydroneaud@opteya.com> wrote:

> > cd net/bluetooth
> > make -C $PWD/../../ M=$PWD modules
> >
> > (But if you change a configuration parameter in .config,
> > you will need to do a full build)
> 
> why? is that creates a linker errs while your module uses some symbols
> that are not exported?
> 

It's to create the autogenerated files built from .config.
Especially include/generated/autoconf.h header.

It's probably doable using only "make prepare" or "make
modules_prepare".

Regards.

-- 
Yann Droneaud
OPTEYA