Skip to content

Conversation

@js6pak
Copy link
Contributor

@js6pak js6pak commented Jan 29, 2022

Simplifies packaging.
Package info was moved from .nuspec to the .csproj.
pack.bat is no longer needed, .nupkg is now made after every build.

Closes #27, closes #28, closes #31

@9ee1 9ee1 changed the title Fix packaging Fix/Update NuGet Package to Include Cross Platform Capstone Binaries Feb 24, 2022
@9ee1 9ee1 added this to the Capstone.NET 2.1.0 milestone Feb 24, 2022
@9ee1 9ee1 merged commit f7d77c5 into 9ee1:master Feb 24, 2022
@9ee1
Copy link
Owner

9ee1 commented Feb 24, 2022

This is great! Thank you very much for your contribution. I apologize about the delay in getting to this. I haven't been checking my GitHub notifications frequently.

@adamsitnik
Copy link
Contributor

@js6pak which version of Capstone have you used in this PR?

I am asking because I would like to send a PR with arm64 support for Windows and wondering if I should update other dependencies as well

@js6pak
Copy link
Contributor Author

js6pak commented Sep 26, 2022

4.0.2 which still is the latest stable version

@9ee1 9ee1 mentioned this pull request Oct 1, 2022
@zeppelin37
Copy link

You deleted the Gee.External.Capstone.targets file which was responsible for copying the native dll to the output directory.

I don't understand that: Do I not need the native dll in the output directory anymore? Is it copied with some other magic?

@js6pak
Copy link
Contributor Author

js6pak commented Dec 15, 2022

Is it copied with some other magic?

Yes, it will be copied with the poorly-documented nuget magic

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug] Cannot execute on mac .NET 6 CopyToOutputDirectory should be PreserveNewest NuGet package only contains Capstone binaries for Windows

4 participants