-
-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fails on 32-bit with unclear error message #151
Comments
mgravell
changed the title
Packaging fails on .NET framwork despite netstandard target
Packaging fails on .NET framework despite netstandard target
Oct 11, 2023
ah, I understand - editing hugely... |
mgravell
changed the title
Packaging fails on .NET framework despite netstandard target
Fails on 32-bit with unclear error message
Oct 11, 2023
Suggestion: if the library has |
Ah I didn't know that. For Linux Arm, there is only a 64bit native binary so will it be a problem? |
I don't know, honestly |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
On .NET Framework, the default target architecture (unless specified explicitly) is "any", IIRC - and will default to x86; the package doesn't have x86 binaries (only x64), so on 32-bit it fails with
Unable to load DLL 'duckdb'
Maybe add a 64-bit check, and/or explicitly specify the target architecture?
original report:
I see that there's anetstandard2.0
package in the nuget, but: it doesn't seem to work; it doesn't work in the tests here, and doesn't work in standalone packages either.If it isn't expected to work on netfx, it might be worth simply dropping the netstandard2.0 target - but this might just be a packaging snafutest setup example:with:gives:Unhandled Exception: System.DllNotFoundException: Unable to load DLL 'duckdb': The specified module could not be found. (Exception from HRESULT: 0x8007007E) at DuckDB.NET.NativeMethods.Startup.DuckDBOpen(String path, DuckDBDatabase& database, DuckDBConfig config, IntPtr& error) at DuckDB.NET.Data.Internal.ConnectionManager.GetConnectionReference(DuckDBConnectionString connectionString) at DuckDB.NET.Data.DuckDBConnection.Open() at Program.<Main>$(String[] args) in C:\Code\ConsoleApp7\ConsoleApp7\Program.cs:line 4
The text was updated successfully, but these errors were encountered: