It's complicated

[Tragetaschen]

The current state of this repository is "It's complicated".

My wish for it is to provide .NET Core runtime and ASP.NET Core built from source and maybe the SDK as well. However, doing that is a non-trivial amount of work. Starting with the actual source repositories is a non-starter as it would mean replicating the entire dependency chain within the Yocto recipe(s) and that has proven to be a very moving target in the past. The closest thing as a starting point currently is the source-build repository, but that one isn't prepared for cross compilation (yet?).

Beyond that, at least the Linux/ARM target has a lot of opinions baked into the build process like wanting to build the Rootfs by itself or explicitly versioned clang executables. It basically expects a very specific Ubuntu host for compilation. For the 2.2.3 build I massaged parts of this into the recipe, but since then a lot of things have changed engineering-wise and are likely to continue changing (case in point: the recent merge into a single runtime repository)

Currently every now and then, I check with the dotnet repositories and evaluate if there is a path forward. For my own images, I have migrated to https://github.com/RDunkley/meta-dotnet-core with the introduction of .NET Core 3.0, which provides the entire .NET Core + ASP.NET Core runtimes from the Microsoft-provided binaries.

[ghost]

Thanks for your clarifications. May I ask you on which ARM CPU you tried the layer "meta-dotnet-core" from RDunkley? I'm using it on a i.MX6 Board from Phytec and the DotNET DLLs seem to get stuck.

EDIT: I'm trying to delete 'libcoreclrtraceptprovider.so'. This seems to make things better :D

Your layer did a perfect job in circumventing the shell scripts from the source-build repo and its a pity that Microsoft doesn't provide a better build infrastructure, that would make it easier to build .NET Core for Yocto.