The native runtimes are not linked/removed from app builds
The native runtimes are not linked/removed from app builds
BY 10 May 2018Tizen .NET
I have a NuGet (SkiaSharp) that I will be releasing (or maybe released by the time you read this) that has several native runtime assets:
“win7-x64”
“win7-x86”,
“osx”
“linux-x64”
“linux-x86”
“tizen-armel”
“tizen-x86”
When I build and install the app on the device/emulator, ALL the runtimes are also added to the app package.
This results in a much larger package than expected – as well as additional libraries that are not actually supported at all.
I would expect the Tizen build process to only copy the runtimes that it supports – such as “tizen-armel”, “tizen-x86” (since this one is not supported maybe just this “linux-x86”, “tizen-armel”)
The native runtimes are not linked/removed from app builds
I have a NuGet (SkiaSharp) that I will be releasing (or maybe released by the time you read this) that has several native runtime assets:
When I build and install the app on the device/emulator, ALL the runtimes are also added to the app package.
This results in a much larger package than expected – as well as additional libraries that are not actually supported at all.
I would expect the Tizen build process to only copy the runtimes that it supports – such as “tizen-armel”, “tizen-x86” (since this one is not supported maybe just this “linux-x86”, “tizen-armel”)
BY
16 Apr 2025
Tizen Studio
BY
04 Nov 2024
Tizen Studio
BY
02 Apr 2024
Tizen Studio