Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/7] lttng-modules: new package
Date: Thu, 12 Jan 2012 23:05:50 +0100	[thread overview]
Message-ID: <201201122305.51006.arnout@mind.be> (raw)
In-Reply-To: <20111222141605.160d5b67@skate>

On Thursday 22 December 2011 14:16:05 Thomas Petazzoni wrote:
> > In fact, since building kernel modules from buildroot is not uncommon
> > anymore (there are some packages in the tree that do it, plus
> > user-specific packages, wouldn't it be a good idea to provide a small
> > infrastructure for building kernel modules? This would prevent such
> > mistakes. Instead of gentargets, we could have something like
> > kernelmodule.
> > What do you think about that?  
> 
> I don't know. I am not exactly sure because there is no real standard
> way for packaging external kernel modules. If you look at linux-fusion,
> RTAI or lttng-modules, you'll see that the build mechanism is very
> different. I'm not sure there is a real pattern here that we can
> factorize nicely in an infrastructure. Which pattern do you see?

 RTAI is different because it is much more than a kernel module.  But I
do see a pattern for linux-fusion, lttng-modules and others I've been
using locally.  They generally have a Makefile that tries to be smart
about the kernel sources, and eventually calls a sub-make as

 $(MAKE) -C $(KERNELDIR) M=$(PWD) <extracflags> <target>

 I think we can do the latter directly from buildroot.

 In some cases there is a user-space component in the same package, but
that normally can be built separately as well.


 Regards,
 Arnout

-- 
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
Essensium/Mind                                     http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium                BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2012-01-12 22:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-22  9:57 [Buildroot] [pull request v2] Pull request for branch for-2012.02/lttng Thomas Petazzoni
2011-12-22  9:57 ` [Buildroot] [PATCH 1/7] liburcu: new package Thomas Petazzoni
2011-12-22  9:57 ` [Buildroot] [PATCH 2/7] lttng-modules: " Thomas Petazzoni
2011-12-22 13:03   ` Thomas De Schampheleire
2011-12-22 13:16     ` Thomas Petazzoni
2012-01-12 22:05       ` Arnout Vandecappelle [this message]
2011-12-22  9:57 ` [Buildroot] [PATCH 3/7] lttng-tools: " Thomas Petazzoni
2011-12-22  9:57 ` [Buildroot] [PATCH 4/7] popt: add host variant for host-lttng-babeltrace Thomas Petazzoni
2011-12-22  9:57 ` [Buildroot] [PATCH 5/7] util-linux: " Thomas Petazzoni
2012-01-12 22:12   ` Arnout Vandecappelle
2012-01-13  8:23     ` Thomas Petazzoni
2011-12-22  9:57 ` [Buildroot] [PATCH 6/7] lttng-babeltrace: new package Thomas Petazzoni
2011-12-22  9:57 ` [Buildroot] [PATCH 7/7] lttng-libust: " Thomas Petazzoni
  -- strict thread matches above, loose matches on Subject: below --
2011-12-21 22:30 [Buildroot] [pull request] Pull request for branch for-2012.02/lttng Thomas Petazzoni
2011-12-21 22:30 ` [Buildroot] [PATCH 2/7] lttng-modules: new package 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=201201122305.51006.arnout@mind.be \
    --to=arnout@mind.be \
    --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