From: Joshua Lock <josh@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: OE-Core and MacOS X
Date: Thu, 28 Apr 2011 14:22:41 -0700 [thread overview]
Message-ID: <1304025761.2171.432.camel@vorpal> (raw)
In-Reply-To: <4DB9D856.7030709@windriver.com>
On Thu, 2011-04-28 at 16:12 -0500, Mark Hatle wrote:
> I've started working on getting bitbake and OE-Core building on MacOS X. So far
> what I have are some pretty hacky patches.. but they should be a reasonable start.
>
> I've pushed my changes to the git://git.pokylinux.org/poky-contrib.git
> repository and the "mhatle/macosx/bitbake" and "mhatle/macosx/oe-core" branches.
>
> The way I am doing builds is:
>
> git clone git://git.pokylinux.org/poky-contrib.git oe-core
> cd oe-core
> git checkout mhatle/macosx/oe-core
> git clone . bitbake
> cd bitbake
> git checkout mhatle/macosx/bitbake
> cd ..
> . ./oe-init-build-env build-macosx
>
>
> Then you edit the conf/local.conf, add the following to the top of the file:
>
> BUILD_ARCH = "x86_64"
> TARGET_OS = "linux"
>
> PREFERRED_VERSION_pseudo-native = "1.0+git%"
> PSEUDOSRCREV = "481c6ff64f8aa6de01d3cb4042914f8e9f8d0abb"
>
> PATCHRESOLVE = 'noop'
>
> DISTRO = 'poky'
>
>
> This allows me to build through the stage 1 part of the build (pseudo) and onto
> the second stage.. it gets the 'gmp' and fails.
>
> On my Mac OS X machine, I need to install the following items (beyond the normal
> BSD tools):
>
> gawk, git, mercurial, sed, tar and wget
Sounds like you've made a good start at this Mark, cool! I had heard one
OE user state that chrpath can't be built on OS X which lead me to file
this bug: http://bugzilla.pokylinux.org/show_bug.cgi?id=806
Cheers,
Joshua
--
Joshua Lock
Yocto Build System Monkey
Intel Open Source Technology Center
next prev parent reply other threads:[~2011-04-28 21:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-28 21:12 OE-Core and MacOS X Mark Hatle
2011-04-28 21:22 ` Joshua Lock [this message]
2011-04-28 21:24 ` Khem Raj
2011-04-28 21:41 ` Chris Larson
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=1304025761.2171.432.camel@vorpal \
--to=josh@linux.intel.com \
--cc=openembedded-core@lists.openembedded.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.