From: Peter Maydell <peter.maydell@linaro.org>
To: Programmingkid <programmingkidx@gmail.com>
Cc: qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v2] qemu-doc.texi: Add information on compiling source code on Mac OS X
Date: Fri, 14 Aug 2015 17:28:29 +0100 [thread overview]
Message-ID: <CAFEAcA-zYtmCM-Eqx27MAWZe+RFkdFuPybKsNaTOVBg+Hbpt7g@mail.gmail.com> (raw)
In-Reply-To: <23DFB849-03EB-4C8D-8F55-5CAD6EEB692D@gmail.com>
On 14 August 2015 at 17:09, Programmingkid <programmingkidx@gmail.com> wrote:
>
> On Aug 14, 2015, at 11:16 AM, Peter Maydell wrote:
>
>> On 7 August 2015 at 21:57, Programmingkid <programmingkidx@gmail.com> wrote:
>>> Add information on compiling source code on Mac OS X
>>> to the documentation.
>>>
>>> Signed-off-by: John Arbuckle <programmingkidx@gmail.com>
>>
>>> ---
>>> qemu-doc.texi | 44 +++++++++++++++++++++++++++++++++++++++++---
>>> 1 files changed, 41 insertions(+), 3 deletions(-)
>>>
>>> diff --git a/qemu-doc.texi b/qemu-doc.texi
>>> index 0125bc7..c059c49 100644
>>> --- a/qemu-doc.texi
>>> +++ b/qemu-doc.texi
>>> @@ -3021,9 +3021,47 @@ and all other qemu-system-@var{target}.exe compiled
>>> for Win32.
>>> @node Mac OS X
>>> @section Mac OS X
>>>
>>>
>>>
>>> -The Mac OS X patches are not fully merged in QEMU, so you should look
>>> -at the QEMU mailing list archive to have all the necessary
>>> -information.
>>> +System Requirements:
>>> +@itemize
>>> +@item Mac OS 10.5 or higher
>>> +@item GCC 4.3 or higher
>>
>> I think this should be "The clang compiler shipped with Xcode 4.2 or higher,
>> or GCC 4.3 or higher".
> Sounds good.
>
>>
>> We should have an @item about any library dependencies we need that
>> aren't provided by Apple. I think that's just glib, but it's been
>> so long since I installed dependencies for QEMU I forget if we
>> need anything else third-party. (We don't need to go into detail
>> about where to get the third-party libs, but mentioning the
>> dependency is helpful I think.)
> That is a really good idea. This is probably what a mac user will have to install
> when installing QEMU for the first time:
> - libffi
> - gettext
> - glib
> - pgk-config
"pkg-config"
> - autoconfig
"autoconf"
> - automake
> - libtool
> - pixman
> This is all I had to install when installing QEMU onto Mac OS 10.9 for the first time.
>
> I could put this information in its own section like this:
>
> Additional requirements (install in order)
> 1. libffi
> 2. gettext
> 3. glib
> 4. pgk-config
> 5. autoconfig
> 6. automake
> 7. libtool
> 8. pixman
>
> Each item will be a hyperlink to each item's web site. Does this sound right?
Yes, that sounds good.
. We could add a note at the end too:
"You may find it easiest to get these from a third-party packager
such as Homebrew, Macports or Fink."
-- PMM
next prev parent reply other threads:[~2015-08-14 16:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-06 15:35 [Qemu-devel] [PATCH] qemu-doc.texi: Add information on compiling source code on Mac OS X Programmingkid
2015-08-07 17:00 ` Peter Maydell
2015-08-07 20:32 ` Programmingkid
2015-08-07 23:13 ` Peter Maydell
2015-08-08 1:06 ` Programmingkid
2015-08-07 20:57 ` [Qemu-devel] [PATCH v2] " Programmingkid
2015-08-14 15:16 ` Peter Maydell
2015-08-14 16:09 ` Programmingkid
2015-08-14 16:28 ` Peter Maydell [this message]
2015-08-14 16:45 ` Programmingkid
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=CAFEAcA-zYtmCM-Eqx27MAWZe+RFkdFuPybKsNaTOVBg+Hbpt7g@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=programmingkidx@gmail.com \
--cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).