Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot on OSX
Date: Sat, 21 Mar 2015 23:04:04 +0100	[thread overview]
Message-ID: <87a8z6husr.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20150320180814.GH21001@waldemar-brodkorb.de> (Waldemar Brodkorb's message of "Fri, 20 Mar 2015 19:08:22 +0100")

>>>>> "Waldemar" == Waldemar Brodkorb <wbx@openadk.org> writes:

Hi,

>> I was just asked if it was possible to use Buildroot natively on a
 >> Mac. I recommended that he just build in a Linux VM. However, after
 >> playing around at command line and learning about Homebrew, it looked
 >> like it may not be too far off especially since Buildroot builds so
 >> much itself. Ignoring external toolchains which I would assume
 >> wouldn't work, has anyone done this?

 > Once I tried to do this, but there wasn't much interest to carry
 > needed patches in buildroot. It is hard to get these Darwin-to-Linux
 > cross-compile patches into upstream projects.
 > Recently I discussed some of the patches I am using in OpenADK with
 > a friend and we will try to reduce them and do it in a better way,
 > which might even be usable for buildroot.

In general, using anything else than a Linux system to build Linux
systems is bound to cause extra issues. To my knowledge, nobody uses
Buildroot with a !Linux host on any regular schedule.

I don't mind simple fixes, but users on !Linux should not expect full
functionality, and I am not interested in carrying any big / feature
patches for it.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2015-03-21 22:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-19 13:21 [Buildroot] Buildroot on OSX Frank Hunleth
2015-03-19 21:11 ` Arnout Vandecappelle
2015-03-20 18:08 ` Waldemar Brodkorb
2015-03-21 22:04   ` Peter Korsgaard [this message]
2015-03-21 22:17     ` Yann E. MORIN

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=87a8z6husr.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox