From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 8D156E0034A; Thu, 12 Jan 2017 10:12:42 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-1.5 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HTML_MESSAGE, RCVD_IN_DNSWL_NONE, RCVD_IN_SORBS_SPAM autolearn=no version=3.3.1 X-Spam-HAM-Report: * -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no * trust * [74.125.82.67 listed in list.dnswl.org] * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider * (gizero[at]gmail.com) * 0.5 RCVD_IN_SORBS_SPAM RBL: SORBS: sender is a spam source * [74.125.82.67 listed in dnsbl.sorbs.net] * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 0.0 HTML_MESSAGE BODY: HTML included in message * -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's * domain * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid * -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature Received: from mail-wm0-f67.google.com (mail-wm0-f67.google.com [74.125.82.67]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 4F215E0030B for ; Thu, 12 Jan 2017 10:12:40 -0800 (PST) Received: by mail-wm0-f67.google.com with SMTP id r126so5505009wmr.3 for ; Thu, 12 Jan 2017 10:12:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=kyCYMIV9imTYP3IZ9txtY5r/2Dmeq9pf3UAE4dqpY2Q=; b=e4+53PwVqPNVJBexuFdxY1JlmcLjLJRMUXgnkRilnQhwS+sJbrDhvQXOpeski37puj I7Y9wN8j+WMzxNpLBmgg47tTfoscAJ4/BR2Y2WViLR9NM+xX35LlpG9cv2cZRDcmkuNq FDCGFNU5jUoseZ1Ky8zayhGIZt8JofG0VH/prkA5rT57PQBxGcQ2p/qUr0DRpzOzoA8W RB9ygT5VPCP/gd7RWzqp7G8wrOA/du1LUgbEkWGRATM+T62ZFMC0Ocv5iAgkMXsrwGS6 Yve/iool04AIgCQiCySV2W55mPtnq3Dk6vMA3/0/EGbc5/UmkNga2qOdFdYbRHOsW4V9 TrFQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=kyCYMIV9imTYP3IZ9txtY5r/2Dmeq9pf3UAE4dqpY2Q=; b=ZX7Rss4QnUjj++3BsuA774MPIL3Qei5PfguU/4JkImndAdP7ZQQ2bpJZk/CGUW14C7 wOAGMyOJjIkhiMNwjIE1ICXvjJxskH/ziC7XccxJm5/2yzdAIyOiyZJlju//pgdyy/+d NN59Z3/VkIjlmMHFN3tSj3dRXaIBycuMHsa/A56Pbwp8gTpmwMXdnh9F3BlYpWhxOrXP 0FHB6x2I0PQbOSrQoqEM19J+z/cUD+n49u3srxa6It4UH11hgP0cRtH+PAzpyir3sY2q rX3n7FRRim1K3PKpWjbgpM1zP0La5D+HwIecW09QFyVRAa0/WDhEDv7H81k2XNA5+FDO LO5w== X-Gm-Message-State: AIkVDXJhXSexoDAKsTqHJhM6G+OkAB+KU/I+XFeRt6eY5o3c0WqFbG5weoKP3ov2qGH2arrrOFsdprftz67yzw== X-Received: by 10.223.162.10 with SMTP id p10mr8281753wra.160.1484244759282; Thu, 12 Jan 2017 10:12:39 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.169.38 with HTTP; Thu, 12 Jan 2017 10:12:38 -0800 (PST) In-Reply-To: References: <990F24BD-1C6F-4985-8E33-0C8E5B59E84A@linux.intel.com> From: Andrea Galbusera Date: Thu, 12 Jan 2017 19:12:38 +0100 Message-ID: To: =?UTF-8?Q?Maciej_Borz=C4=99cki?= Cc: "yocto@yoctoproject.org" Subject: Re: Building on MacOS X X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jan 2017 18:12:42 -0000 Content-Type: multipart/alternative; boundary=f403045ed4b2a30ac70545e9a9c4 --f403045ed4b2a30ac70545e9a9c4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Thu, Jan 12, 2017 at 6:55 PM, Maciej Borz=C4=99cki wrote: > On Thu, Jan 12, 2017 at 4:39 PM, Tim Orling > wrote: > > You can also build using Docker containers: > > https://github.com/crops/docker-win-mac-docs/wiki > > IIRC docker on mac relies on docker-machine, which in turn spins up a > virtualbox VM. > Not anymore! There's a native implementation [1] but still a linux kernel around anyway! ;-) [1] https://www.docker.com/docker-news-and-press/docker-released-native-mac-and= -windows-apps-optimize-developer-experience > > > > > > On Jan 12, 2017, at 7:34 AM, Burton, Ross wrote= : > > > > > > On 12 January 2017 at 15:14, Roger Smith wrote= : > >> > >> Is there any documentation for running the Yocto build system on Mac O= S > 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=E2=80=99d 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 t= he > > linux-specific bits in bitbake. I've previously started on this work > > already > > (http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/ > log/?h=3Dross/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 > > > > > > > > -- > > _______________________________________________ > > yocto mailing list > > yocto@yoctoproject.org > > https://lists.yoctoproject.org/listinfo/yocto > > > > > > -- > Maciej Borzecki > RnDity > -- > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > --f403045ed4b2a30ac70545e9a9c4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On T= hu, Jan 12, 2017 at 6:55 PM, Maciej Borz=C4=99cki <maciej.borzeck= i@rndity.com> wrote:
On Thu, Jan 12, 2017 at 4:39 PM, Tim Or= ling
<timothy.t.orling@li= nux.intel.com> wrote:
> You can also build using Docker containe= rs:
> https://github.com/crops/docker-win-mac-d= ocs/wiki

IIRC docker on mac relies on docker-machine, which in turn spins up = a
virtualbox VM.

Not anymore! There's= a native implementation [1] but still a linux kernel around anyway! ;-)

=C2= =A0


>
> 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> wrote:
>>
>> Is there any documentation for running the Yocto build system on M= ac OS X
>> or macOS as Apple now calls it? I am working with the Intel Aero b= oard.
>> Before I go down the rabbit hole of fixing issues like this one (a= nd I am
>> using the bash shell), I=E2=80=99d like to know if anyone has buil= d 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.=C2=A0 Then you need to stub= out the
> linux-specific bits in bitbake.=C2=A0 I've previously started on t= his work
> already
> (http://git.yoctopro= ject.org/cgit/cgit.cgi/poky-contrib/log/?h=3Dross/darwin). > The next step is figuring out how to configure OE to build and link na= tively
> on OSX using LLVM instead of GCC.
>
> However all of this is mostly academic because in Sierra (iirc) onward= s
> there is tighter security on processes, which means that pseudo won= 9;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=
>
>
>
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto=
>



--
Maciej Borzecki
RnDity
--
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto<= br>

--f403045ed4b2a30ac70545e9a9c4--