public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Kilian Kegel" <KILIAN_KEGEL@OUTLOOK.COM>
To: edk2-devel-groups-io <devel@edk2.groups.io>
Cc: "Rabeda, Maciej" <maciej.rabeda@linux.intel.com>,
	Rebecca Cran <rebecca@nuviainc.com>,
	"tim.lewis@insyde.com" <tim.lewis@insyde.com>,
	Mike Kinney <michael.d.kinney@intel.com>,
	"afish@apple.com" <afish@apple.com>,
	Leif Lindholm <leif@nuviainc.com>
Subject: CdePkgBlog 2021-11-18
Date: Sun, 28 Nov 2021 20:35:13 +0000	[thread overview]
Message-ID: <AM8P190MB094511C5839EDC7A9CAFBCD9EB659@AM8P190MB0945.EURP190.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <CAKbZUD1W3RO_nLRpnm6MLOOVf9PYfAYyH9cvtEwWTrBVXbjDgw@mail.gmail.com>

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

Hi All,

as announced in my last CdePkgBlog I’d like to demonstrate how to design, create and build missing
tools for the UEFI Shell, that are still known today from the Windows command line: FIND and MORE.

Along those tools I:

  1.  describe how to deal with native UEFI ASCII and UTF16 files.
  2.  publish toro C Library stdin file/console handling as a part of a reference implementation
  3.  publish toro C Library command-line-to-argc/argv translation as part of a reference implementation
  4.  publish toro C Library concept of how to pass the OS-interface SystemTable to main() in a Standard-C-compatible sideway

Once again the tools were translated to .EFI executables using the Microsoft VisualStudio 2022 command line
without the EDK2 build process.
Please checkout my second CdePkgBlog https://github.com/tianocore/edk2-staging/tree/CdePkg/blogs/2021-11-28#cdepkgblog-2021-11-28
and enjoy the breathtaking build speed if compiler and linker are used exclusively to create FIND.EFI and MORE.EFI
Have fun,
Kilian


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

  reply	other threads:[~2021-11-28 20:35 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-27 15:48 "StdLibPkg" branch on edk2-staging Maciej Rabeda
2021-07-28 15:34 ` [edk2-devel] " Rebecca Cran
2021-07-28 15:45   ` Maciej Rabeda
2021-07-28 15:59     ` Rebecca Cran
2021-07-28 22:25   ` Tim Lewis
2021-07-28 22:44     ` Rebecca Cran
2021-08-04 11:03       ` Leif Lindholm
2021-08-05  3:35         ` Andrew Fish
2021-08-05  4:14           ` Kilian Kegel
     [not found]           ` <16984DDFBF70DC40.16396@groups.io>
2021-08-11 13:19             ` Kilian Kegel
2021-11-14 19:51               ` CdePkgBlog 2021-11-14 Kilian Kegel
2021-11-22 16:31                 ` [edk2-devel] " Maciej Rabeda
2021-11-24 20:21                   ` Kilian Kegel
2021-11-24 22:50                     ` Pedro Falcato
2021-11-28 20:35                       ` Kilian Kegel [this message]
     [not found]                       ` <16BBD01DEB5EF921.4083@groups.io>
2021-12-12 20:02                         ` CdePkgBlog 2021-12-12 Kilian Kegel
2021-12-19 20:51                           ` CdePkgBlog 2021-12-19 Kilian Kegel
2022-01-16 20:01                             ` CdePkgBlog 2022-01-16 -- Introduction of the ACPICA port to UEFI Kilian Kegel
2021-11-30 10:09                     ` [edk2-devel] CdePkgBlog 2021-11-14 Maciej Rabeda
     [not found]                     ` <16BC4B25BB307B73.14741@groups.io>
2021-11-30 20:15                       ` Maciej Rabeda

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=AM8P190MB094511C5839EDC7A9CAFBCD9EB659@AM8P190MB0945.EURP190.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