Static .lib availability
The SDK currently appears to only provide an import library for the DLL.
Is it possible to also provide a static .lib build? I'm trying to static link noesis as part of my C# Native AOT app.
Is it possible to also provide a static .lib build? I'm trying to static link noesis as part of my C# Native AOT app.
Re: Static .lib availability
Static linking unfortunately requires us to provide different binaries for each compiler version, CRT configuration, and build setting, which dramatically increases the number of distributions we would have to maintain and support.
For that reason, we only ship public binaries as dynamic libraries. This ensures compatibility across toolchains and keeps the SDK maintainable.
If you have access to the source code, you can build Noesis as a static library for your environment.
For that reason, we only ship public binaries as dynamic libraries. This ensures compatibility across toolchains and keeps the SDK maintainable.
If you have access to the source code, you can build Noesis as a static library for your environment.
Re: Static .lib availability
Just curious, have you considered using the newer .NET P/Invoke source generation attributes like:The SDK currently appears to only provide an import library for the DLL.
Is it possible to also provide a static .lib build? I'm trying to static link noesis as part of my C# Native AOT app.
Code: Select all
[LibraryImport(
"nativelib",
EntryPoint = "to_lower",
StringMarshalling = StringMarshalling.Utf16)]
internal static partial string ToLower(string str);
You should be able to use the DLLs and still take advantage of NativeAOT though.
"Make it exist,"
-- Arkaen Solutions
-- Arkaen Solutions
Who is online
Users browsing this forum: Baidu [Spider] and 4 guests