From: Mark Hatle <mark.hatle@windriver.com>
To: Roger Smith <roger@sentientblue.com>, <yocto@yoctoproject.org>
Subject: Re: Building on MacOS X
Date: Thu, 12 Jan 2017 09:38:33 -0600 [thread overview]
Message-ID: <56c0100f-a4c3-482a-93f9-55168d8b71d1@windriver.com> (raw)
In-Reply-To: <F2336301-06DF-41BD-B64E-82D421DB9366@sentientblue.com>
On 1/12/17 9:14 AM, Roger Smith wrote:
> Is there any documentation for running the Yocto build system on Mac OS X or
> macOS as Apple now calls it? I am working with the Intel Aero board. Before I go
> down the rabbit hole of fixing issues like this one (and I am using the bash
> shell), I’d like to know if anyone has build it on os x before.
As far as I am aware, nobody has ever finished this work.
There are numerous places (scripts primarily) that will expect GNU
util-linux/coreutils (and similar) extensions.
In addition, the pseudo program, used to emulate filesystem permissions and
related items only partially works on MacOS. (I know it was working at one
point, but Apple changed some of the system properties [preloaded library] for
security reasons, and ended up making pseudo no longer work. You may want to
look into this before getting too far in. Without pseudo, there is no way to
perform a build/package.)
Some -very- old work:
http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib-archive/refs/heads
search for macosx
(I'd love to see a native bitbake/oe-core work on MacOS X... but as far as I
know the work stalled a while back due to lack of interest by people.)
Most of the people I know using MacOS X for development are using virtual box
(or similar) and a Linux based VM.
--Mark
> thanks
>
>
> source oe-init-build-env
> readlink: illegal option -- f
> usage: readlink [-n] [file ...]
> -bash: /scripts/oe-buildenv-internal: No such file or directory
>
>
prev parent reply other threads:[~2017-01-12 15:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-12 15:14 Building on MacOS X Roger Smith
2017-01-12 15:34 ` Burton, Ross
2017-01-12 15:39 ` Tim Orling
2017-01-12 15:42 ` Burton, Ross
2017-01-12 16:21 ` Belisko Marek
2017-01-12 16:27 ` Khem Raj
2017-01-12 16:50 ` Andrea Galbusera
2017-01-12 17:41 ` Roger Smith
2017-01-12 17:47 ` Burton, Ross
2017-01-12 22:59 ` Mark Hatle
2017-01-13 8:50 ` Clemens Lang
2017-01-14 19:45 ` Roger Smith
2017-01-14 19:49 ` Tim Orling
2017-01-16 11:19 ` Burton, Ross
2017-01-17 2:33 ` Brian Avery
2017-01-12 22:32 ` Tim Orling
2017-01-12 17:55 ` Maciej Borzęcki
2017-01-12 18:03 ` Burton, Ross
2017-01-12 18:12 ` Andrea Galbusera
2017-01-12 18:43 ` Maciej Borzęcki
2017-01-12 22:16 ` Tim Orling
2017-01-12 15:38 ` Mark Hatle [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=56c0100f-a4c3-482a-93f9-55168d8b71d1@windriver.com \
--to=mark.hatle@windriver.com \
--cc=roger@sentientblue.com \
--cc=yocto@yoctoproject.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 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.