if a port needs 2.x then set MODPY_VERSION=${MODPY_DEFAULT_VERSION_2}.
This commit doesn't change any versions currently used; it may be that
some ports have MODPY_DEFAULT_VERSION_2 but don't require it, those
should be cleaned up in the course of updating ports where possible.
Python module ports providing py3-* packages should still use
FLAVOR=python3 so that we don't have a mixture of dependencies some
using ${MODPY_FLAVOR} and others not.
in py-angr is linked to an _unversioned_ .so from py-unicorn.
LIB_DEPENDS without an associated WANTLIB is incorrect, the LIB_DEPENDS is
stripped so py-unicorn is not recorded as a dep in here. and WANTLIB requires
a versioned .so file.
convert to BUILD+RUN_DEPENDS, it's not 100% correct either but the only
sane way.
angr-vex's library is dlopen(3)ed py py-pyvex (not py-angr itself), so
register it as proper RDEP in py-pyvex (and only there).
Spotted after `pkg_add angrop' on a fresh installation where angr-vex was
not installed; even though angr has an LDEP on it, our framework does not
turn it into a RDEP unless angr also links against it.
vex is amd64-only and there is no point in attempting to build packages
only to have them fail when the RDEP on vex cannot be resolved (e.g. on
i386 as reported by sthen).
prompted by sthen@
ok kn@
angr is a suite of Python 3 libraries that let you load a binary
and do a lot of cool things to it:
- Disassembly and intermediate-representation lifting
- Program instrumentation
- Symbolic execution
- Control-flow analysis
- Data-dependency analysis
- Value-set analysis (VSA)
- Decompilation
join work with and ok kn@
rough edges will be handled in-tree
