Hi Andrea,
As you already know, all your dependencies need to be packed. I assume when you were building for mono, the mono package had provided them for you?
Having to deal with source-building dependencies is a problem anyone faces to include a .NET application in a distro. Even when the dependencies are open-source, there is no tooling that will help you get those dependencies built. I think it's worth raising a ticket in the https://github.com/dotnet/core/ repository. I doubt it will get a high priority, but it's good to make explicit the general problem, which could be improved by better tooling. Do you want to create such a ticket? Otherwise, I can write one up.
If you run into build issues, feel free to ask them on the mailing list. You can also find us on the Libera.Chat #fedora-dotnet channel for some live interaction.
Thanks, Tom
On Tue, Jan 11, 2022 at 3:23 AM Timotheus Pokorra mailinglists@tpokorra.de wrote:
Hello,
In mono I used to have this in the SPEC file: ExclusiveArch: %mono_arches
I am not aware of something that already exits for .NET, but that's a good idea. We should investigate this for .NET.
For mono, those arches are defined in this file: https://src.fedoraproject.org/rpms/redhat-rpm-config/blob/rawhide/f/macros.m...
# arches that mono builds on %mono_arches %{ix86} x86_64 sparc sparcv9 ia64 %{arm} aarch64 alpha s390x ppc ppc64 ppc64le
all the best, Timotheus _______________________________________________ DotNet SIG mailing list -- dotnet-sig@lists.fedoraproject.org To unsubscribe send an email to dotnet-sig-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/dotnet-sig@lists.fedoraproject... Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure