From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Capstone 5.0
Date: Wed, 12 Jul 2023 02:21:13 +0200 [thread overview]
Message-ID: <20230712002113.9abnZ8DuwNQnjgJuxxAg6y0LJYkmutNWu9tFi5HR9No@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44967@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1658 bytes --]
New comment by classabbyamp on void-packages repository
https://github.com/void-linux/void-packages/pull/44967#issuecomment-1631673381
Comment:
would you mind adding this patch to the PR? I've tested it and it works.
```patch
From 681f1c71fe0ffe780407365ebbd91efdfc3fb8b9 Mon Sep 17 00:00:00 2001
From: classabbyamp <void@placeviolette.net>
Date: Tue, 11 Jul 2023 20:19:36 -0400
Subject: [PATCH] imhex: use system capstone
---
srcpkgs/imhex/template | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/srcpkgs/imhex/template b/srcpkgs/imhex/template
index 3f7f475038..94a058c2b1 100644
--- a/srcpkgs/imhex/template
+++ b/srcpkgs/imhex/template
@@ -1,18 +1,17 @@
# Template file for 'imhex'
pkgname=imhex
version=1.30.1
-revision=1
+revision=2
build_wrksrc="ImHex"
build_style=cmake
build_helper=qemu
-# XXX: when capstone v5 is out, -DUSE_SYSTEM_CAPSTONE=ON
configure_args="-DIMHEX_OFFLINE_BUILD=ON -DIMHEX_STRIP_RELEASE=OFF
- -DUSE_SYSTEM_CURL=ON -DUSE_SYSTEM_FMT=ON -DUSE_SYSTEM_LLVM=ON
+ -DUSE_SYSTEM_CURL=ON -DUSE_SYSTEM_FMT=ON -DUSE_SYSTEM_LLVM=ON -DUSE_SYSTEM_CAPSTONE=ON
-DUSE_SYSTEM_YARA=ON -DUSE_SYSTEM_NLOHMANN_JSON=ON -DIMHEX_DISABLE_UPDATE_CHECK=ON"
hostmakedepends="pkg-config clang-tools-extra"
makedepends="libcurl-devel fmt-devel llvm jansson-devel yara-devel json-c++
freetype-devel glfw-devel gtk+3-devel python3-devel file-devel mbedtls-devel
- clang-tools-extra"
+ clang-tools-extra capstone-devel"
short_desc="Hex editor for reverse engineers and programmers"
maintainer="classabbyamp <void@placeviolette.net>"
license="GPL-2.0-or-later"
--
2.41.0
```
next prev parent reply other threads:[~2023-07-12 0:21 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 15:18 [PR PATCH] " motorto
2023-07-10 17:09 ` [PR PATCH] [Updated] " motorto
2023-07-12 0:13 ` [PR REVIEW] " classabbyamp
2023-07-12 0:21 ` classabbyamp [this message]
2023-07-12 15:31 ` [PR PATCH] [Updated] " motorto
2023-07-12 15:31 ` motorto
2023-07-14 9:07 ` motorto
2023-07-15 13:17 ` motorto
2023-07-15 16:34 ` XVilka
2023-07-15 19:35 ` motorto
2023-07-31 11:51 ` [PR PATCH] [Updated] " motorto
2023-08-05 7:01 ` XVilka
2023-08-05 7:03 ` XVilka
2023-08-07 15:34 ` [PR PATCH] [Updated] " motorto
2023-08-07 15:37 ` motorto
2023-08-07 15:56 ` [PR PATCH] [Updated] " motorto
2023-08-09 14:04 ` motorto
2023-08-20 2:52 ` XVilka
2023-08-20 22:14 ` [PR PATCH] [Updated] " motorto
2023-08-20 22:17 ` motorto
2023-08-22 10:50 ` [PR PATCH] [Updated] " motorto
2023-08-22 10:51 ` motorto
2023-08-22 16:18 ` classabbyamp
2023-08-23 1:04 ` sgn
2023-08-23 2:41 ` XVilka
2023-08-23 14:05 ` motorto
2023-08-23 14:05 ` motorto
2023-08-23 15:17 ` sgn
2023-08-23 18:02 ` [PR PATCH] [Updated] " motorto
2023-08-23 18:03 ` motorto
2023-09-14 9:51 ` XVilka
2023-09-15 18:10 ` [PR PATCH] [Updated] " motorto
2023-09-15 19:54 ` motorto
2023-09-15 22:00 ` [PR PATCH] [Merged]: " classabbyamp
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230712002113.9abnZ8DuwNQnjgJuxxAg6y0LJYkmutNWu9tFi5HR9No@z \
--to=classabbyamp@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).