Do not use #include <capstone/..>
This ensures compatibility with both capstone v3 and capstone as
installed on most distributions, where the pkg-config file of capstone
already adds -I/usr/include/capstone (with that dir directly containing
the headers).
Something does not work well with static (it hasn't at least from the
moment build-static started running full tests). To avoid all kind of
brokeness all around, let's switch back to no-tests. We will enable them
together with the proper fixes for the static build.
* Fix#3929 - Enable LTO in sys/static.sh
* Update Ubuntu to 20.04 for static build
* Use `gcc-ar` when needed
* Do not use "c" option for ${AR}
* Use `$$AR` instead of `$AR`
* Aim to fix `-dynamiclib` issue outside darwin
* Run tests for static LTO build
Co-authored-by: pancake <pancake@nopcode.org>
Co-authored-by: Anton Kochkov <xvilka@gmail.com>
* Make sure meson can build with `system` = `android`.
* Add support for binr/blob in meson build
* Create release GitHub Actions workflow
* Add publish-docker-image job
* Also create Ubuntu packages and ship static windows zip
* Fix re-definition of RAnalBlockCb and RAnalAddrCb
* Small compilation fixes for gcc-4
* Check PTRACE_GETREGSET before using it
* Add GH workflow to run on centos:6 for prerelease branches
* Fix configure.acr
* Move radare2-shell-parser/tree-sitter into shlr
* compile new shell parser by default, available with cfg.newshell variable
* Add README for radare2-shell-parser
* Improve CI
* Add gitattributes file
* Try to run newshell tests on newshell- PRs
GH actions pull_request.branches only filter the base branch.
* Make it clearer which builds run tests and which do not
Makes the coverity scan neither download of the Coverity Build Tool nor
execute any of the following steps for forked repositories, avoiding
sending GitHub alerts to those repo owners.
With https://github.com/actions/labeler/issues/12
being an issue, the action's labeler is useless for PRs that come from a fork.
This one runs on a cron timer instead and doesn't suffer from the same issue.
