search

RDunkley / meta-dotnet-core

BitBake recipes to use the pre-built binaries provided by Microsoft for .Net Core and their remote debugger.
MIT License
34 stars 28 forks source link

Consider using INSANE_SKIP="staticdev" instead of RDEPENDS=-staticdev #18

Closed Tragetaschen closed 4 years ago

Tragetaschen commented 4 years ago

I have noticed on my image that using aspnet-core or dotnet-core would pull in a lot of -dev dependencies and a python3 interpreter amongst other things. I was able to trace those back to the RDEPENDS="aspnet-core-staticdev" dependency.

With a .bbappend containing

FILES_${PN}-staticdev_remove = "${datadir}/dotnet/shared/Microsoft.NETCore.App/${PV}/*.a"
RDEPENDS_${PN}_remove = "aspnet-core-staticdev"
INSANE_SKIP_${PN} += "staticdev"

the *.a files are provided through the main package. Since that would normally trigger a QA error, it is suppressed with the INSANE_SKIP.

The *.a files are an integral part of the .NET Core installation and not meant for development in the bitbake sense, so this seems like the better approach.

RDunkley commented 4 years ago

Thanks for the fix. I didn't realize it was adding so many additional files.