Runtime: Eliminate Windows PAL layer for non-Windows CoreCLR builds

Created on 4 Feb 2020 · 1Comment · Source: dotnet/runtime

Fix/investigate usage of Windows file in non-windows CoreCLR builds.

https://github.com/dotnet/runtime/blob/ce925072739702ebf8f6a4c6131ca3b73b81a44f/src/libraries/System.Private.CoreLib/src/System.Private.CoreLib.Shared.projitems#L1449-L1501

This usage is suspicious. It is also non-conventional.

Recommend:

Remove files from set which are not needed for non-windows builds.
Rename file paths if possible to remove confusion.

/cc @marek-safar @jkotas @danmosemsft @stephentoub @Anipik

See comments https://github.com/dotnet/runtime/pull/28819#discussion_r374680113

area-PAL-coreclr

Source

sdmaclea

Most helpful comment

CoreCLR uses PAL layer that emulates Windows API on Unix. This is bridge for that PAL layer.

It would be nice to get rid of the CoreCLR Windows API emulating PAL layer and replace it something leaner (ideally written in C# as much as possible - we have some prior art for this in CoreRT).

We can use this issue to track elimination of the Windows PAL layer.

jkotas on 4 Feb 2020

👍4

>All comments

CoreCLR uses PAL layer that emulates Windows API on Unix. This is bridge for that PAL layer.

It would be nice to get rid of the CoreCLR Windows API emulating PAL layer and replace it something leaner (ideally written in C# as much as possible - we have some prior art for this in CoreRT).

We can use this issue to track elimination of the Windows PAL layer.

jkotas on 4 Feb 2020

👍4

Was this page helpful?

0 / 5 - 0 ratings