Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Can not create driver package with local sources
Date: Fri, 17 Aug 2018 23:37:50 +0200	[thread overview]
Message-ID: <20180817233750.12cbc85e@windsurf> (raw)
In-Reply-To: <VI1PR0802MB22211E2F46DD87FB8C69FFF6EA3D0@VI1PR0802MB2221.eurprd08.prod.outlook.com>

Hello Fabrice,

On Fri, 17 Aug 2018 14:06:35 +0000, Fabrice Mousset | GEOCEPT GmbH
wrote:

> I try to create a custom package to build a linux driver which sources are stored locally, but this doesn't work, because source files are not copy to build directory.
> I am using BuildRoot 2018.05.
> 
> Here is my mk file:
> ---
> BR2_PACKAGE_SITEC_S4_LP_VERSION      = 1.0
> BR2_PACKAGE_SITEC_S4_LP_SITE         = $(TOPDIR)/package/sitec-s4-lp/src
> BR2_PACKAGE_SITEC_S4_LP_SITE_METHOD  = local
> BR2_PACKAGE_SITEC_S4_LP_DEPENDENCIES = linux
> 
> define BR2_PACKAGE_SITEC_S4_LP_BUILD_CMDS

All those prefixes are wrong. The variables in the .mk file should be
prefixed by SITEC_S4_LP, not BR2_PACKAGE_SITEC_S4_LP.

As your .mk file is written, none of those variables are taken into
account, so it's exactly as if your file contained just:

$(eval $(kernel-module))
$(eval $(generic-package))

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-08-17 21:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-17 14:06 [Buildroot] Can not create driver package with local sources Fabrice Mousset | GEOCEPT GmbH
2018-08-17 21:37 ` Thomas Petazzoni [this message]
2018-08-20  6:57   ` Fabrice Mousset | GEOCEPT GmbH

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=20180817233750.12cbc85e@windsurf \
    --to=thomas.petazzoni@bootlin.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