You are not logged in.

#1 2020-01-06 04:06:30

huupoke12
Member
Registered: 2017-04-24
Posts: 12

Which architecture when building .NET Core packages?

Which value should I set in the arch variable when creating PKGBUILD for .NET Core packages, there are not any wiki page mentioning packaging .NET Core applications (only Mono).

Offline

#2 2020-01-06 11:23:55

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 7,813

Re: Which architecture when building .NET Core packages?

When there are no specific guidelines the general guidelines are valid, check https://wiki.archlinux.org/index.php/Ar … guidelines .

After reading it you should be able to answer your own question,


Multi-init booting with apg Openrc and systemd coexisting
Automounting : not needed, i prefer pmount
Aur helpers : makepkg + my own local repo === rarely need them

Offline

#3 2020-01-06 11:29:16

huupoke12
Member
Registered: 2017-04-24
Posts: 12

Re: Which architecture when building .NET Core packages?

I have already read that, but the question I wanted to ask is: The compiled .NET Core application is architecture-specific or not? Can it be run on other architectures without re-compiling or not?

Offline

#4 2020-01-06 11:43:15

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 7,813

Re: Which architecture when building .NET Core packages?

That depends on the application itself and you haven't named it.


For now, put x86_64 as arch .

Once your package builds, run

namcap your-package.pkg.tar.xz

and post the output.

namcap checks many things, one of them is whether the value in the arch array matches the created binaries.


Multi-init booting with apg Openrc and systemd coexisting
Automounting : not needed, i prefer pmount
Aur helpers : makepkg + my own local repo === rarely need them

Offline

#5 2020-01-06 12:06:15

huupoke12
Member
Registered: 2017-04-24
Posts: 12

Re: Which architecture when building .NET Core packages?

Thanks for mentioning namcap, it checked it with it and it reminded me of custom libraries were compiled so the application is x86_64:

osu-lazer-git W: ELF file ('usr/lib/osu-lazer/libbass.so') lacks FULL RELRO, check LDFLAGS.
osu-lazer-git W: ELF file ('usr/lib/osu-lazer/libbass_fx.so') lacks FULL RELRO, check LDFLAGS.
osu-lazer-git W: ELF file ('usr/lib/osu-lazer/libe_sqlite3.so') lacks FULL RELRO, check LDFLAGS.
osu-lazer-git W: ELF file ('usr/lib/osu-lazer/libstbi.so') lacks FULL RELRO, check LDFLAGS.
osu-lazer-git W: unneeded dependency on a package run when needed by hooks.
osu-lazer-git E: Missing custom license directory (usr/share/licenses/osu-lazer-git)
osu-lazer-git W: Dependency included and not needed ('dotnet-sdk')
osu-lazer-git W: Dependency included and not needed ('ffmpeg')
osu-lazer-git W: Dependency included and not needed ('shared-mime-info')

Offline

#6 2020-01-06 12:16:58

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 7,813

Re: Which architecture when building .NET Core packages?

TL;DR : please post your PKGBUILD if you want help with these.

osu-lazer-git W: ELF file ('usr/lib/osu-lazer/libbass.so') lacks FULL RELRO, check LDFLAGS.
osu-lazer-git W: ELF file ('usr/lib/osu-lazer/libbass_fx.so') lacks FULL RELRO, check LDFLAGS.
osu-lazer-git W: ELF file ('usr/lib/osu-lazer/libe_sqlite3.so') lacks FULL RELRO, check LDFLAGS.
osu-lazer-git W: ELF file ('usr/lib/osu-lazer/libstbi.so') lacks FULL RELRO, check LDFLAGS.

These indicate archlinux default flags aren't used, this can usually be solved but how depends on the specific build system (cmake, autotools, meson, ninja etc) the software uses.

osu-lazer-git W: unneeded dependency on a package run when needed by hooks.

This message is new for me, maybe others can help.

osu-lazer-git E: Missing custom license directory (usr/share/licenses/osu-lazer-git)

this needs to be corrected.

osu-lazer-git W: Dependency included and not needed ('dotnet-sdk')
osu-lazer-git W: Dependency included and not needed ('ffmpeg')
osu-lazer-git W: Dependency included and not needed ('shared-mime-info')

Could be false positives.


Multi-init booting with apg Openrc and systemd coexisting
Automounting : not needed, i prefer pmount
Aur helpers : makepkg + my own local repo === rarely need them

Offline

#7 2020-01-06 12:42:15

huupoke12
Member
Registered: 2017-04-24
Posts: 12

Re: Which architecture when building .NET Core packages?

The package is on the AUR along with its PKGBUILD (I adopted it from the previous maintainer):
https://aur.archlinux.org/packages/osu-lazer-git/

Last edited by huupoke12 (2020-01-06 14:05:20)

Offline

#8 2020-01-06 13:47:38

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 7,813

Re: Which architecture when building .NET Core packages?

The missing license directory is due to the use of $pkgname%-git) in the package() function .

This results in licences being in /usr/share/licenses/osu-lazer folder instead of /usr/share/licenses/osu-lazer-git folder.

To avoid / minimize conflicts with the osu-lazer stable package I'd personally use ${pkgname} throughout the osu-lazer-git PKGBUILD and append  -git to provided sourcefiles (so osu-launcher-git ).

This would look cleaner and may allow osu-lazer & osu-lazer-git to coexist .

Last edited by Lone_Wolf (2020-01-06 13:48:10)


Multi-init booting with apg Openrc and systemd coexisting
Automounting : not needed, i prefer pmount
Aur helpers : makepkg + my own local repo === rarely need them

Offline

Board footer

Powered by FluxBB