All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot on OSX
Date: Sat, 21 Mar 2015 23:17:27 +0100	[thread overview]
Message-ID: <20150321221727.GD4201@free.fr> (raw)
In-Reply-To: <87a8z6husr.fsf@dell.be.48ers.dk>

Peter, All,

On 2015-03-21 23:04 +0100, Peter Korsgaard spake thusly:
> >>>>> "Waldemar" == Waldemar Brodkorb <wbx@openadk.org> writes:
> >> 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.

Fully agreed.

Patches that are "portability cleanups", like changing '#!/bin/sh' to
'#!/usr/bin/env bash' for example, are probably acceptable.

Anything that adds complexity and/or different code-paths are probably
to be avoided. And patches to packages to make them build on MacOS are
to be banned (unless upstream accepts them first).

Seriously, there's no better platform for doing Linux development than a
Linux box. At worst, a VM would do the trick.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

      reply	other threads:[~2015-03-21 22:17 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
2015-03-21 22:17     ` Yann E. MORIN [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=20150321221727.GD4201@free.fr \
    --to=yann.morin.1998@free.fr \
    --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.