From now on, ports that depend on Qt4 will have to set
USES= qt:4
USE_QT= foo bar
ports depending on Qt5 will use
USES= qt:5
USE_QT= foo bar
PR: 229225
Exp-run by: antoine
Reviewed by: mat
Approved by: portmgr (antoine)
Differential Revision: →https://reviews.freebsd.org/D15540
The full message is:
/usr/bin/ld:
Graphics/CMakeFiles/vtkGraphics.dir/vtkProbeFilter.cxx.o(.text+0x182c):
sibling call optimization to '_ZN14vtkProbeFilter26SetValidPointMaskArrayNameEPKc'
does not allow automatic multiple TOCs; recompile with -mminimal-toc or
-fno-optimize-sibling-calls, or make
'_ZN14vtkProbeFilter26SetValidPointMaskArrayNameEPKc' extern
This is beyond the scope of what I understand how to fix.
Ports using USE_PYTHON=distutils are now flavored. They will
automatically get flavors (py27, py34, py35, py36) depending on what
versions they support.
There is also a USE_PYTHON=flavors for ports that do not use distutils
but need FLAVORS to be set. A USE_PYTHON=noflavors can be set if
using distutils but flavors are not wanted.
A new USE_PYTHON=optsuffix that will add PYTHON_PKGNAMESUFFIX has been
added to cope with Python ports that did not have the Python
PKGNAMEPREFIX but are flavored.
USES=python now also exports a PY_FLAVOR variable that contains the
current python flavor. It can be used in dependency lines when the
port itself is not python flavored. For example, deskutils/calibre.
By default, all the flavors are generated. To only generate flavors
for the versions in PYTHON2_DEFAULT and PYTHON3_DEFAULT, define
BUILD_DEFAULT_PYTHON_FLAVORS in your make.conf.
In all the ports with Python dependencies, the *_DEPENDS entries MUST
end with the flavor so that the framework knows which to build/use.
This is done by appending '@${PY_FLAVOR}' after the origin (or
@${FLAVOR} if in a Python module with Python flavors, as the content
will be the same). For example:
RUN_DEPENDS= ${PYTHON_PKGNAMEPREFIX}six>0:devel/py-six@${PY_FLAVOR}
PR: 223071
Reviewed by: portmgr, python
Sponsored by: Absolight
Differential Revision: https://reviews.freebsd.org/D12464
UNIQUENAME was never unique, it was only used by USE_LDCONFIG and now,
we won't have conflicts there.
Use PKGBASE instead of LATEST_LINK in PKGLATESTFILE, the *only* consumer
is pkg-devel, and it works just fine without LATEST_LINK as pkg-devel
has the correct PKGNAME anyway.
Now that UNIQUENAME is gone, OPTIONSFILE is too. (it's been called
OPTIONS_FILE now.)
Reviewed by: antoine, bapt
Exp-run by: antoine
Sponsored by: Absolight
Differential Revision: https://reviews.freebsd.org/D3336
- Add an OPTION to build without legacy code
- Fix Qt4 includes (fixes a conflict when both Qt3 and Qt4 are installed)
Reported upstream: http://www.vtk.org/Bug/view.php?id=13888
vendors:
Remove any reference to bsdjava and freebsd Java Vendors, as the both are
outdated, have security issues and expired.
Mark icedtea6-stubs as broken as it doesn't build with any of the left supported
vendors.
Switch tuxguitar to be able to use openjdk16 [1]
Approved by: gahr [1]
This setting has not had any effect since r1.13 to bsd.cmake.mk, as it
was only useful when we supported FreeBSD < 7.
Approved by: avilla (mentor), portmgr (miwi)
Feature safe: yes
