From: Trevor Woerner <twoerner@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: [meta-darwin] Re: building an SDK for MacOSX
Date: Sun, 9 Aug 2015 19:42:54 -0400 [thread overview]
Message-ID: <55C7E57E.7010502@gmail.com> (raw)
In-Reply-To: <55C277BF.5020309@gmail.com>
Hi Richard (and everyone),
Any thoughts on this, is my understanding correct? It would be
fantastically great if I could generate MacOSX-hosted OE SDKs built on
my Linux machine to target embedded ARM boards... it would *really* help
"sell" OE to the people at work :-D
On 08/05/15 16:53, Trevor Woerner wrote:
> I came across RP's meta-darwin today that I'm hoping will enable me to
> build an OpenEmbedded SDK that can be used by my colleagues who work in
> a MacOSX environment?
>
> Is my understanding correct?
>
> Has anyone tried this lately? The last commit was from almost exactly a
> year ago.
Has anyone used this recently?
>
> The description in the README is a bit vague. I've never used a MacOSX
> system so I'm not entirely sure of the filesystem layout. What exactly
> is needed to create the OSX-sdk.zip file?
> /usr/include
> /usr/lib
> /lib
A coworker had a look at his machine and provided me with the following
information:
/usr/lib: 87MB
/lib : Not available
/usr/include: Not availabe
/usr/local/lib: 20MB
/usr/local/include: 2.2MB
Does that sound right? Is the above what I need a zip of to use this layer?
Best regards,
Trevor
prev parent reply other threads:[~2015-08-09 23:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-05 20:53 building an SDK for MacOSX Trevor Woerner
2015-08-09 23:41 ` Richard Purdie
2015-08-09 23:44 ` Trevor Woerner
2015-08-09 23:42 ` Trevor Woerner [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=55C7E57E.7010502@gmail.com \
--to=twoerner@gmail.com \
--cc=richard.purdie@linuxfoundation.org \
--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.