From: "Sean" <spbrogan@outlook.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"rebecca@bsdio.com" <rebecca@bsdio.com>,
"joe.hasselstrom@icloud.com" <joe.hasselstrom@icloud.com>
Subject: Re: [edk2-devel] Port C Tools to Python
Date: Wed, 21 Jun 2023 08:07:35 +0000 [thread overview]
Message-ID: <BY3PR19MB4900B6726D1F45EC90C80FCEC85DA@BY3PR19MB4900.namprd19.prod.outlook.com> (raw)
In-Reply-To: <b625a521-cca8-4bd0-bac1-2ae880a21668@app.fastmail.com>
[-- Attachment #1: Type: text/plain, Size: 1351 bytes --]
This has moved over to https://github.com/tianocore/edk2-basetools/issues
I am sure any help you could offer would be appreciated.
Thanks
Sean
________________________________
From: devel@edk2.groups.io <devel@edk2.groups.io> on behalf of Rebecca Cran <rebecca@bsdio.com>
Sent: Tuesday, June 20, 2023 6:25:21 PM
To: joe.hasselstrom@icloud.com <joe.hasselstrom@icloud.com>; devel@edk2.groups.io <devel@edk2.groups.io>
Subject: Re: [edk2-devel] Port C Tools to Python
I believe someone is currently working on it.
—
Rebecca
On Tue, Jun 20, 2023, at 4:56 PM, joe.hasselstrom@icloud.com wrote:
> Greetings,
>
> I was wondering if the wiki task "Port C Tools to Python” is still
> relevant for the EDK2 project and if so I’d like to start working on
> it. Any suggestions on getting started?
>
> Task description found at
> https://github.com/tianocore/tianocore.github.io/wiki/Tasks#port-c-tools-to-python
>
> … snip
> Large Projects
>
> Port C Tools to Python
>
> Port tools currently implemented in C to Python. This removes the need
> to run a C compiler to build the tools required to build EDK II
> firmware.
>
> • Project Size: Large
> • Difficulty: Hard
> • Language: C, Python
> • Mentor:
> • Suggested by: @mdkinney <https://github.com/mdkinney>
> … end snip
>
> Thanks,
> - Joe
[-- Attachment #2: Type: text/html, Size: 2693 bytes --]
prev parent reply other threads:[~2023-06-21 8:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 22:56 Port C Tools to Python Joe Hasselstrom
2023-06-21 1:25 ` Rebecca Cran
2023-06-21 8:07 ` Sean [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-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=BY3PR19MB4900B6726D1F45EC90C80FCEC85DA@BY3PR19MB4900.namprd19.prod.outlook.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