All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Orling <timothy.t.orling@linux.intel.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Building on MacOS X
Date: Thu, 12 Jan 2017 07:39:11 -0800	[thread overview]
Message-ID: <990F24BD-1C6F-4985-8E33-0C8E5B59E84A@linux.intel.com> (raw)
In-Reply-To: <CAJTo0LZiwodwfYbokKD1n9hK_ddxYFFzpTiLixZSkVnzTtQxVQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1643 bytes --]

You can also build using Docker containers:
https://github.com/crops/docker-win-mac-docs/wiki <https://github.com/crops/docker-win-mac-docs/wiki>

> On Jan 12, 2017, at 7:34 AM, Burton, Ross <ross.burton@intel.com> wrote:
> 
> 
> On 12 January 2017 at 15:14, Roger Smith <roger@sentientblue.com <mailto:roger@sentientblue.com>> 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.
> 
> If you install all of the GNU tools using brew or similar and put them first on $PATH then you can get bitbake started.  Then you need to stub out the linux-specific bits in bitbake.  I've previously started on this work already (http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=ross/darwin <http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=ross/darwin>).  The next step is figuring out how to configure OE to build and link natively on OSX using LLVM instead of GCC.
> 
> However all of this is mostly academic because in Sierra (iirc) onwards there is tighter security on processes, which means that pseudo won't work even if you port it to macOS.
> 
> So unless you fancy some non-trivial engineering the short version is just use something like Docker to run a Linux system on your Mac.
> 
> Ross
> -- 
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto


[-- Attachment #2: Type: text/html, Size: 2885 bytes --]

  reply	other threads:[~2017-01-12 15:39 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 [this message]
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

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=990F24BD-1C6F-4985-8E33-0C8E5B59E84A@linux.intel.com \
    --to=timothy.t.orling@linux.intel.com \
    --cc=ross.burton@intel.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.