From dbed10b8d6a90c4ae1fbdfe667e4aecac3bcf37a Mon Sep 17 00:00:00 2001 From: Andrew Date: Mon, 9 Dec 2024 11:21:02 -0500 Subject: [PATCH] Update packages/deb/README.md Co-authored-by: Rot127 <45763064+Rot127@users.noreply.github.com> --- packages/deb/README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/packages/deb/README.md b/packages/deb/README.md index fa37f550726..359f75bd5ca 100644 --- a/packages/deb/README.md +++ b/packages/deb/README.md @@ -4,7 +4,9 @@ This assumes your working directory is in the `packages/deb/` directory. To build a Debian package for Capstone, run the script, where `` is going to be the version attached to both the `capstone.pc` file and the Debian package itself. The version is expected to be compliant with Debian versioning (a major/minor/patch), e. g. `5.0.4`. Debian versions can also support values to indicate pre-release, e. g. `6.0.0-Alpha1`. -Note if a value such as `6.0.0-Alpha1` is provided, the major/minor/patch number is extracted for `capstone.pc`, which would have version `6.0.0`, but the Debian package would have the full version name on the control file. +**Note**: if a value such as `6.0.0-Alpha1` is provided, the major/minor/patch number is extracted for `capstone.pc`, which would have version `6.0.0`, but the Debian package would have the full version name on the control file. + +**Note**: Currently the package is hard coded to the `amd64` architecture. Independently on what machine you built it. Also see [issue #2537](https://github.com/capstone-engine/capstone/issues/2537). ```bash ./setup.sh