From: Nicholas Kinar <n.kinar@usask.ca>
To: buildroot@busybox.net
Subject: [Buildroot] Updated status on the compilation of busybox on Mac OS X
Date: Sun, 29 Nov 2009 14:31:25 -0600 [thread overview]
Message-ID: <4B12DA1D.3020508@usask.ca> (raw)
In-Reply-To: <87einh2n3w.fsf@macbook.be.48ers.dk>
>
> OK. I still think you'll have an easier time doing your buildroot work
> on a (virtual) Linux box, but it's your choice..
>
Of course, Linux is much easier at many things, which is the reason why
it is used for projects such as Busybox.
> Yes, the gumstix people unfortunately haven't been that good at
> submitting their fixes back to us :/
>
That's always an issue with having a forked or separate build tree from
the main project. IMHO, I don't like separate build trees, but
apparently it is the sometimes the way that software development is
accomplished.
> I agree that there isn't any technical reason why BR shouldn't work on
> MacOSX, but currently there's no active developers using it (I do write
> this on a macbook, but I very rarely boot into macosx).
>
Strangely enough, I'm also writing this on a macbook, and I boot more
into Linux than any other of the three operating systems that I run. I
won't mention the name of the third operating system, but I tend to use
it only for engineering software that won't run on Linux. ;-)
> The problem isn't just getting the makefiles of BR to work on MacOSX,
> the biggest problem is all the build scripts of the individual packages.
>
Agreed.
> With that said, patches to make stuff work better on MacOSX are welcome,
> as long as they aren't too ugly / add too much extra complexity for such
> a rarely used setup.
>
>
This would be something to add to my to-do list. I know that making
FOSS software run on a non-free OS is somewhat of a contradiction, but
IMHO it helps to encourage adoption among a segment of users that
exclusively use a setup such as Mac OS X. I believe that a good example
of this type of adoption is Firefox, which runs on all of the "Big
three" operating systems.
Besides, it might be kind of fun to ensure that buildroot can run on all
flavours of GNU/Linux/Unix.
Nicholas
next prev parent reply other threads:[~2009-11-29 20:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-29 1:39 [Buildroot] Updated status on the compilation of busybox on Mac OS X Nicholas Kinar
2009-11-29 8:46 ` Peter Korsgaard
2009-11-29 14:47 ` Nicholas Kinar
2009-11-29 18:37 ` Peter Korsgaard
2009-11-29 20:31 ` Nicholas Kinar [this message]
2009-12-01 13:48 ` Thomas Petazzoni
2009-12-01 15:21 ` Nicholas Kinar
2009-12-01 15:34 ` Peter Korsgaard
2009-12-02 1:47 ` Nicholas Kinar
2009-12-02 15:57 ` Nicholas Kinar
2009-12-02 15:59 ` Austin Foxley
2009-12-02 22:47 ` Nicholas Kinar
2009-12-02 18:40 ` Peter Korsgaard
2009-12-02 22:48 ` Nicholas Kinar
2009-12-02 22:55 ` Nicholas Kinar
2009-12-03 8:30 ` Peter Korsgaard
2009-12-03 14:54 ` Nicholas Kinar
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=4B12DA1D.3020508@usask.ca \
--to=n.kinar@usask.ca \
--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