From: rebecca@bluestop.org
To: devel@edk2.groups.io, sean.brogan@microsoft.com
Subject: Re: [edk2-devel] RFC for Edk2-ToolEnv
Date: Mon, 13 May 2019 22:01:19 -0600 [thread overview]
Message-ID: <6c39d4ce-2ec6-3ffc-6f0f-b2a1adf3c1d0@bluestop.org> (raw)
In-Reply-To: <5965.1557802506227860431@groups.io>
[-- Attachment #1: Type: text/plain, Size: 1104 bytes --]
On 2019-05-13 20:55, Sean via Groups.Io wrote:
>
> RFC Edk2-ToolEnv creation
>
>
>
> Create a new tianocore owned repository to host python code to support
> an extensible, pluggable, rich environment. This environment has
> command line interfaces to support building a product, building CI,
> running tests, and downloading dependencies. This environment also
> provides the building blocks for developers to write their own tools
> to launch in the environment and leverage the capabilities provided by
> the environment. The unique capabilities provided help support
> building products with multiple repositories and having each
> repository contribute/plugin to the build process in a scalable way.
> The environment will scan the files in the code tree (multiple repos)
> and discover plugins, dependencies, path adjustments, environment
> variable settings, etc. This provides easy methods for common repos
> to share build tools/steps.
>
Is there not an existing framework that could be used instead of
creating something new?
--
Rebecca Cran
[-- Attachment #2: Type: text/html, Size: 2651 bytes --]
next prev parent reply other threads:[~2019-05-14 4:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-14 2:55 RFC for Edk2-ToolEnv Sean
2019-05-14 4:01 ` rebecca [this message]
2019-05-14 7:37 ` [edk2-devel] " Sean
2019-05-14 22:24 ` rebecca
2019-05-14 23:23 ` Sean
2019-05-14 23:34 ` rebecca
2019-05-23 2:39 ` Michael D Kinney
2019-05-23 6:46 ` Sean
2019-05-23 17:14 ` Michael D Kinney
2019-06-11 18:55 ` Purma, Kondal R
2019-06-12 6:02 ` Sean
2019-06-28 22:13 ` Sean
2019-06-28 22:22 ` Michael D Kinney
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=6c39d4ce-2ec6-3ffc-6f0f-b2a1adf3c1d0@bluestop.org \
--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