From: "Rebecca Cran" <rebecca@nuviainc.com>
To: discuss@edk2.groups.io, rebecca@bsdio.com, aladyshev22@gmail.com,
edk2-devel-groups-io <devel@edk2.groups.io>
Subject: Re: [edk2-discuss] State of the `edk2-libc` project
Date: Mon, 2 Aug 2021 14:22:13 -0600 [thread overview]
Message-ID: <d1963a26-9ed5-1d4d-cd50-31eef20969fd@nuviainc.com> (raw)
In-Reply-To: <05AF4C60-A693-4D83-B069-ABC45FB79D17@bsdio.com>
By the lack of replies, I suspect we should bring it up as a topic of
discussion in the Community Meeting next week.
--
Rebecca Cran
On 7/14/21 1:43 PM, Rebecca Cran wrote:
> I submitted a patch to fix it several weeks ago, but it never got committed.
>
> Rebecca Cran
>> On Jul 14, 2021, at 11:36 AM, Konstantin Aladyshev <aladyshev22@gmail.com> wrote:
>>
>> Hello!
>>
>> What is the state of the `edk2-libc` project?
>>
>> The last commit is dated Apr 29, 2019. I've tried to compile
>> `edk2-libc` with the master `edk2` and have come to some build issues.
>>
>> For example this edk2 commit (13 Oct 2020 "MdePkg: Remove code wrapped
>> by DISABLE_NEW_DEPRECATED_INTERFACES"
>> https://github.com/tianocore/edk2/commit/9c1f455f5f0ee63ce080940bf974aac4fefe526b)
>> have dropped support for several functions, but these functions are
>> still used in `edk2-libs`:
>> - `StrCpy` and `StrCpy` functions are used in
>> https://github.com/tianocore/edk2-libc/blob/master/StdLib/LibC/Wchar/Copying.c
>> - `AsciiStrCat` and `AsciiStrnCat` functions are used in
>> https://github.com/tianocore/edk2-libc/blob/master/StdLib/LibC/String/Concatenation.c
>> In the modern `edk2` all these old functions are replaced with their
>> safe versions (StrCpyS, StrCpyS, AsciiStrCatS, AsciiStrnCatS).
>>
>> My question is should these unsafe string functions be deprecated in
>> the `edk2-libc` as well? And more importantly does the tianocore
>> community have any plans for support of `edk2-libc` project or can it
>> be counted as obsolete?
>>
>> Best regards,
>> Konstantin Aladyshev
>>
>>
>>
>>
>>
>
>
>
>
>
parent reply other threads:[~2021-08-02 20:22 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <05AF4C60-A693-4D83-B069-ABC45FB79D17@bsdio.com>]
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=d1963a26-9ed5-1d4d-cd50-31eef20969fd@nuviainc.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