MODULES ordering is relevant; here cmake comes before python so cmake wins.
swapping them would mean python gets to set default targets, unless an
explicit configure style is set -- do so for clarity; no change.
No need to fiddle around with static/shared or boost/python bits in the
autoconf system when cmake just gets it right.
cmake does not build egg files by default (there's an option, though).
No symbol changes as per /usr/src/lib/check_sym.
The current autoconf build links against system boost as well,
with cmake only the python boost library is used.
This looks like a needless extra in the autoconf version.
No static library besides the dynamic one anymore.
OK rsadowski
- updates to 1.2.17
- major bump due to removed symbols
- MODPY_SETUPTOOLS because ${WRKSRC}/bindings/python/setup.py mentions
setuptools. A side effect was that this sets TEST_TARGET = test. To
get tests to run, set TEST_TARGET = check
- removes ${FILESDIR}/setup.py
- patches Jamfile with correct library version number and add include
path for boost
- patches setup.py to pass arguments to b2 to build python bindings
correctly
- backports build fix for boost 1.80.0
see: https://github.com/arvidn/libtorrent/issues/69721ec11e4e9b
- garbage collects PYTHON= CC= CXX= flags, which appear to be unused
- install python binding using MODPY_PYC_MAGIC_TAG
based on initial diff from Brad
feedback from Brad and sthen@
ok sthen@
Release notes:
https://github.com/arvidn/libtorrent/releases/tag/v1.2.13
- remove autotools and use CONFIGURE_STYLE = gnu now that default C++
standard is detected. see:
https://github.com/arvidn/libtorrent/pull/5026
- major bump because check_sym reports removed symbols
- carry ${FILESDIR}/setup.py from 1.2.11 because 1.2.12 relies on
boost-build
- remove patches/patch-configure_ac
- Uses ${MODPY_EGG_VERSION} and SUBST_CMD in setup.py to only have to
update version in one place (from sthen@)
- Uses ${MODPY_BIN} in ${FILESDIR}/setup.py (from sthen@)
- Remove -L{LOCALBASE}/lib in ${FILESDIR}/setup.py. Python bindings
incorrectly linked -ltorrent-rasterbar with
/usr/local/lib/libtorrent-rasterbar.so.3.0 instead of the freshly
built ${WRKSRC}/src/.libs/libtorrent-rasterbar.so.4.0.
rsadowski@ reviewed older version of this diff
thfr@ gave feedback on using check_sym and deprecation not necessitating
major bump
sthen@ gave feedback on python bits in setup.py
ok mariani@ who also tested deluge (older version of this diff) and
qbittorrent
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.
changelog: https://github.com/arvidn/libtorrent/blob/libtorrent-1.2.9/ChangeLog
- uses c++14 instead of clang++'s default gnu++14
- moves to autoreconf because configure defaults to c++11 instead of the
desired c++14
- bumps library major due to symbol deletion
- changes MASTER_SITES to properly download the new release
- specifies devel/boost>=1.67.0 (from rsadowski@)
- uses MODPY_VERSION for naming boost python bindings in WANTLIB and
CONFIGURE_ARGS (from rsadowski@)
- uses mt variants of libboost_system-mt and libboost_python38-mt
- links to libiconv.so.7.0 instead of libiconv.a now that upstream
updated m4 macros
- regens WANTLIB with boost_python38, boost_system (non-mt) and iconv
- Remove PYTHON_CXXFLAGS and CXXFLAGS. gnu++14 is now the default for
ports-gcc. (from brad@)
From Nam Nguyen
libtorrent(-rasterbar) is a C++ library that aims to be a good
alternative to all the other bittorrent implementations around.
The main goals of libtorrent are to be cpu efficient, memory efficient
and very easy to use.
Note that this is NOT the same library as the libtorrent package!
Based on a port by dcoppa@
Tweaks + ok bcallah@
