From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot on Windows Subsystem for Linux (WSL)
Date: Tue, 19 Jan 2021 08:06:27 +0100 [thread overview]
Message-ID: <87ft2xe77w.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CA+h8R2oGKpEX8fwJw6SHHbQnV7uvcZkArz3X8m_5Sk39U5PbLA@mail.gmail.com> (Christian Stewart's message of "Mon, 18 Jan 2021 19:52:30 -0800")
>>>>> "Christian" == Christian Stewart <christian@paral.in> writes:
> Hi Peter,
> On Mon, Jan 18, 2021 at 12:15 PM Peter Korsgaard <peter@korsgaard.com> wrote:
>>
>> >>>>> "Christian" == Christian Stewart <christian@paral.in> writes:
>> > The Buildroot system works as expected in the WSL environment. The
>> > buildroot output tar.gz can be imported directly into WSL 2.0. WSL 1.0
>> > requires using the WSL-DistroLauncher project to load the distribution
>> > via a Windows Appx.
>>
>> > This is an interesting way to use Buildroot under Windows.
>>
>> Cute. Besides the fact that you are booting a (heavily patched) Linux
>> kernel, is there any specific advantages to just creating a docker
>> container or a classic VM from a Buildroot build?
> By my (limited) understanding, WSL2 promises tighter integration
> between Linux and the Windows OS.
> I haven't tested it, but docs say you can override the kernel image.
You haven't tested it? Didn't the defconfig you point to build a Linux
kernel as well?
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2021-01-19 7:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 9:08 [Buildroot] Buildroot on Windows Subsystem for Linux (WSL) Christian Stewart
2021-01-18 20:15 ` Peter Korsgaard
2021-01-19 3:52 ` Christian Stewart
2021-01-19 7:06 ` Peter Korsgaard [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=87ft2xe77w.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.