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

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

On 12 January 2017 at 15:39, Tim Orling <timothy.t.orling@linux.intel.com>
wrote:

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

Yes, this is the link I was failing to find, thanks Tim.  This is basically
the official way of using OE on Windows or Mac.

Ross

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

  reply	other threads:[~2017-01-12 15:43 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 [this message]
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=CAJTo0Lb9Lo5TEdu5f_1CVcyeRLEBZxv1uOoU7GosDfLDwPjrXg@mail.gmail.com \
    --to=ross.burton@intel.com \
    --cc=roger@sentientblue.com \
    --cc=timothy.t.orling@linux.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.