From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot and kernel modules
Date: Wed, 12 Nov 2014 22:27:52 +0100 [thread overview]
Message-ID: <20141112222752.228404f0@free-electrons.com> (raw)
In-Reply-To: <CAEk40fw3Kgtgq=mKdR3ib40tLtD5x4SF0sT0QJrrwKVCO_+BZA@mail.gmail.com>
Dear Sid Bharij,
On Wed, 12 Nov 2014 12:25:45 -0600, Sid Bharij wrote:
> So I have the driver source file and makefile for it.
> Where does this part go into ? Does it go into the Config.in file or some
> top level makefile or the same makefile needed for compiling the driver
> code?
You seem to misunderstand what Buildroot is. Buildroot is a build
system, its aim is to build the various components of your embedded
Linux system. It is not meant to carry the source code of those
individual components.
So your driver source file and makefile for it has to be its own
project, stored somewhere (most likely under version control), and
Buildroot will download it from where it's located and build it.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-11-12 21:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-12 5:04 [Buildroot] Buildroot and kernel modules Sid Bharij
2014-11-12 10:03 ` Thomas Petazzoni
2014-11-12 12:21 ` Paassen, Hiram van
2014-11-12 12:34 ` Thomas Petazzoni
2014-11-12 18:25 ` Sid Bharij
2014-11-12 21:27 ` Thomas Petazzoni [this message]
2014-11-12 22:19 ` Sid Bharij
2014-11-12 22:20 ` Thomas Petazzoni
2014-11-12 19:26 ` Bryce Schober
2014-11-12 21:03 ` Thomas Petazzoni
-- strict thread matches above, loose matches on Subject: below --
2013-06-19 15:26 [Buildroot] buildroot " jerryalex at tx.rr.com
2013-06-19 15:35 ` Thomas Petazzoni
[not found] ` <20130619155518.8G4TE.59637.root@cdptpa-web08-z02>
2013-06-20 7:39 ` Thomas Petazzoni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141112222752.228404f0@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox