From: "Rebecca Cran" <rebecca@bsdio.com>
To: Andrew Fish <afish@apple.com>, devel@edk2.groups.io
Cc: lersek@redhat.com
Subject: Re: [edk2-devel] [tianocore.github.io.wiki PATCH 1/1] Xcode.md: Update instructions to work on modern macOS and Xcode versions
Date: Wed, 21 Jul 2021 08:24:30 -0600 [thread overview]
Message-ID: <dc62a00d-796e-8b07-82ec-6ad2d4e72d96@bsdio.com> (raw)
In-Reply-To: <B191E7B0-4CFC-4D73-ACD1-A6DD9344212A@apple.com>
[-- Attachment #1: Type: text/plain, Size: 2146 bytes --]
I think most people (including myself) use brew nowadays, which installs
to /usr/local/bin so the instructions work.
I was wondering if we should remove the MacPorts instructions?
--
Rebecca Cran
On 7/20/21 11:37 PM, Andrew Fish wrote:
> These Xcode instructions look good to me in general. Thanks for doing
> this I usually do things following a non public path.
>
> I think to make these instructions work you need to update
> *_XCODE5_*_MTOC_PATH
>
> By default, this will install |mtoc| at |/opt/local/bin/mtoc|.
> https://github.com/tianocore/edk2/blob/master/BaseTools/Conf/tools_def.template#L2957
> <https://github.com/tianocore/edk2/blob/master/BaseTools/Conf/tools_def.template#L2957>
>
> *_XCODE5_*_MTOC_PATH = /usr/local/bin/mtoc
>
>
> We could change this to match the brew default location, I think this
> location is way out of date. I think the other things get fixed by the
> path variables.
>
> Thanks,
>
> Andrew Fish
>
>
>
>> On May 25, 2021, at 5:36 AM, Rebecca Cran <rebecca@bsdio.com
>> <mailto:rebecca@bsdio.com>> wrote:
>>
>> On 5/25/21 6:21 AM, Laszlo Ersek wrote:
>>
>>> The idea is to use the wiki of any one of your projects on
>>> github.com <http://github.com> --
>>> most fittingly, your edk2 fork's wiki.
>>>
>>> The URL to clone the "real" wiki repo from is:
>>>
>>> git://github.com/tianocore/tianocore.github.io.wiki
>>> <git://github.com/tianocore/tianocore.github.io.wiki>
>>>
>>> And the repo URL of the wiki of your edk2 fork *should be*:
>>>
>>> git@github.com <mailto:git@github.com>:bcran/edk2.wiki.git
>>>
>>> I'm not sure if you first need to enable the wiki function, for your
>>> edk2 fork, on github.com <http://github.com>. Maybe that's hidden
>>> somewhere between the
>>> project (fork) settings. Either way, once your wiki repo exists, just
>>> force-push to it whatever your local clone contains. And, only the
>>> "master" branch matters for rendering, AFAICT.
>>
>>
>> Ah, got it - thanks.
>>
>> The updated Xcode.md page is at
>> https://github.com/bcran/edk2/wiki/Xcode
>> <https://github.com/bcran/edk2/wiki/Xcode>
>>
>>
>> --
>> Rebecca Cran
>>
>>
>>
>>
>>
>>
>>
>
[-- Attachment #2: Type: text/html, Size: 9581 bytes --]
next prev parent reply other threads:[~2021-07-21 14:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <167D7C25411C8F3B.21893@groups.io>
2021-05-10 19:40 ` [edk2-devel] [tianocore.github.io.wiki PATCH 1/1] Xcode.md: Update instructions to work on modern macOS and Xcode versions Rebecca Cran
2021-05-17 13:27 ` Rebecca Cran
2021-05-21 18:28 ` Rebecca Cran
2021-05-23 8:51 ` Laszlo Ersek
2021-05-23 16:12 ` Rebecca Cran
2021-05-23 21:00 ` Andrew Fish
2021-06-04 2:18 ` Rebecca Cran
2021-05-25 12:21 ` Laszlo Ersek
2021-05-25 12:36 ` Rebecca Cran
2021-07-21 5:37 ` Andrew Fish
2021-07-21 14:24 ` Rebecca Cran [this message]
2021-07-21 14:30 ` Andrew Fish
2021-07-21 23:57 ` Rebecca Cran
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-list 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=dc62a00d-796e-8b07-82ec-6ad2d4e72d96@bsdio.com \
--to=devel@edk2.groups.io \
/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