Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Betteridge <lists.nick.betteridge@gmail.com>
To: Jean-Michel Hautbois <jeanmichel.hautbois@yoseli.org>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] Linux kernel make target
Date: Thu, 6 Jul 2023 09:52:48 +0100	[thread overview]
Message-ID: <aebc452f-16e7-d5bb-3ee2-4ec982dd16e7@gmail.com> (raw)
In-Reply-To: <0bc3ae44-0a96-4a72-ee9a-8620cb474c3d@yoseli.org>


>>
>> I'm unable to find an option in menuconfig which allows me to specify 
>> a kernel target for 'make' - is this possible? In other words, I can 
>> see how to specify the kernel source location, the defconfig etc, but 
>> I also need to specify the target - in my case it's 'make 
>> nanopi6-images'.
>
> If this target is a defconfig, you can use BR2_LINUX_KERNEL_DEFCONFIG.
> But I think this is a custom target in a non-upstream kernel.
> In this case, I don't think you will be able to do it directly and 
> will probably need to modify linux/Config.in and linux/linux.mk files.
>
It works, of course! Setting the 'kernel image target name' to 
'nanopi6-images' and 'kernel image name' to 'Image' - I had neglected to 
set the 'kernel image name'.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2023-07-06  8:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-05  5:21 [Buildroot] Linux kernel make target Nick Betteridge
2023-07-05  5:30 ` Jean-Michel Hautbois
2023-07-05  5:49   ` Nick Betteridge
2023-07-06  8:52   ` Nick Betteridge [this message]

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=aebc452f-16e7-d5bb-3ee2-4ec982dd16e7@gmail.com \
    --to=lists.nick.betteridge@gmail.com \
    --cc=buildroot@buildroot.org \
    --cc=jeanmichel.hautbois@yoseli.org \
    /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