-
-
Notifications
You must be signed in to change notification settings - Fork 36
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
Unified native package #103
Comments
This is not possible, at least yet. Before making a versatile package, I must configure GH runners for all runtimes and synchronize builds.
|
Well, having unified package with other package as sources doesn't mean you have to use that one. Everyone, who cares about restore speed/storage space can just stick with the way they handle native dependencies before. It's just one more option for a user. |
As the CI was configured this could be possible now. The unified runtime package which contains both arm64/x64 references is now packed with this approach. The name of the bundle could be as follows if there are no objections: |
Great! I don't have any objections with naming, it looks clear enough to me 👍 |
Resolved in #131 |
Works great on my end, many thanks for keeping an eye on this! |
It's great to see the progress on NET bindings for gdal is still an ongoing work!
Though I'm no longer an active contributor to GIS community, after looking at increasing number of native gdal packages, I came up with idea of creating the additional nuget package, combining references to all native ones, like NetVips.Native does.
That way the library users will have to write only one explicit dependency in their .csproj files and all the new (theoretical) platforms, like e.g. linux-arm64, can be added with a simple version bump from a library-user perspective.
The text was updated successfully, but these errors were encountered: