Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
This PR follows #349 and adds GitHub actions to build, test and upload pre-built binaries & source package to PyPI (under the name
pycdc
) for most platforms. This allows end users to simply run:to install the library, without having to clone or build anything in most cases (with the exception of arm based macs and other exotic platforms that need to have pre-installed build environments to run the above command).
There are two new workflow files triggered by hand or by the following events:
vx.y.z
(version bump branches): build and test python binaries against major platformspycdc
name and enabling the Trusted Publisher featureI've restricted python versions to 3.7 to 3.10, since I was not able to build the lib for python < 3.7 and python 3.11 doesn't seem well supported atm (in particular,
tests/test_bindings.py
fails with in 3.11). In theory, python 3.11 could be used to run decompile code, but only of lower versions of python at the moment, which might be confusing ? Let me know what you think.I also took the liberty of adding some shields to the readme to reflect the state of the project (tests / pypi version / installable python versions).