public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Sean" <sean.brogan@microsoft.com>
To: Rebecca Cran <rebecca@bluestop.org>,devel@edk2.groups.io
Subject: Re: [edk2-devel] RFC for Edk2-ToolEnv
Date: Tue, 14 May 2019 00:37:52 -0700	[thread overview]
Message-ID: <24134.1557819472326069609@groups.io> (raw)
In-Reply-To: <6c39d4ce-2ec6-3ffc-6f0f-b2a1adf3c1d0@bluestop.org>

[-- Attachment #1: Type: text/plain, Size: 1040 bytes --]

Rebecca,

If you know of anything I am interested as I don't like building and supporting something unnecessary.

This tooling isn't trying to reinvent anything but is really focused on providing reusable/sharable functionality that can then be pieced together by a platform to produce the required output.  Today in edk2 you see shell script files (bash/bat) and a lot of redefinition of variables and assumptions.  This is made much worse in complex closed src code bases, complicated pre and post build requirements, and even then managing the path and locations to tools and scripts is a fragile mess.  In practice this environment has made our build process much more reliable, lower cost to maintain, and immune to necessary churn at all levels of the code tree.  It also has allowed our products to get significant code reuse so we lower the cost of ongoing maintenance and new feature introduction.

Looking forward to gathering more input from the community as we all don't need to build similar things.

Thanks
Sean

[-- Attachment #2: Type: text/html, Size: 1113 bytes --]

  reply	other threads:[~2019-05-14  7:37 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 ` [edk2-devel] " rebecca
2019-05-14  7:37   ` Sean [this message]
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=24134.1557819472326069609@groups.io \
    --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