defined via Mk/bsd.default-versions.mk which has moved from GCC 7.4 t
GCC 8.2 under most circumstances.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, as a double check, everything INDEX-11 showed depending on lang/gcc7.
PR: 231590
While here, chase some KDE4 ports and functionality, these are scheduled for
removal on 2018-12-31. Change the default option/flavor to QT5 where applicable
or use alternative toolkits like GTK.
Submitted by: tcberner
Reviewed by: adridg, jhale, rene, tcberner
Approved by: portmgr (implicit, flavor hook)
Differential Revision: https://reviews.freebsd.org/D17741
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
Upstream has renamed its libraries and we no longer need to patch
devel/qscintilla-qt5 to create a library whose name does not conflict with
devel/qscintilla's. However, the library names are different so we need to bump
PORTREVISION in several ports (the SOVERSION has changed too).
Thanks to antoine for the exp-run.
PR: 225928
toplsqltext.cpp:80:19: error: cannot initialize a member subobject of type 'const char *' with an rvalue of type 'bool'
{ NULL, NULL, false, false}
^~~~~
Bring in some long overdue updates, some of which are required for us to
later land the PyQt5 ports.
One big change with this update is that the PyQt4 ports now install their
.sip files into share/py-sip/PyQt4 instead of share/py-sip. This way we do
not end up with directories like share/py-sip/QtCore, which are especially
confusing once PyQt5 lands and starts installing files with the same names.
Other noteworthy items:
- PORTREVISION has been bumped on ports depending on devel/qscintilla2
because libqscintilla2.so's SOVERSION has changed.
- graphics/seexpr has been converted to USE_PYQT, as the file it used to
define a build-time dependency on x11-toolkits/py-qt4-gui has moved.
Once again, big thanks to Tobias Berner <tcberner@gmail.com> and Guido Falsi
(madpilot@) for their initial work on these ports as part of the effort to
land PyQt5 into the tree (see D2910 in Phabricator for an earlier version of
the PyQt5 patch set).
PR: 205143
- Use OPTIONS helpers where possible.
- Drop qt4-linguist dependency - the port does not use it (and it already contains prebuilt translations).
- Regenerate patches.
PR: 201724
Submitted by: s3erios@gmail.com
... And bump PORTREVISION on ports that depend on devel/qscintilla2 due to
the shlib version change.
This is brought to you by the KDE on FreeBSD team. Besides updating to newer
upstream releases, this commit also contains a lot of under-the-hood changes
to the PyQt/QScintilla/SIP ports. Their Makefiles had accumulated a lot of
cruft over time, so it was time for some summer cleaning:
- General, belated changes:
* Use OPTIONS helpers wherever possible, stop including
<bsd.port.options.mk> when not necessary, stop checking for
${PORT_OPTIONS:MDOCS} and ${PORT_OPTIONS:MEXAMPLES} when not necessary,
add options such as DOCS and/or DEBUG where they were only checked for.
- QScintilla ports:
* Drop the API option from py-qt4-qscintilla2. It had been broken ever
since staging support was added, and its existence does not make much
sense: QScintilla is a hard dependency regardless of the state of this
option anyway, they all come from the same tarball and the configuration
script assumes the .api file will always be installed.
- PyQt ports:
* The configure.py patch shared by all PyQt ports has been trimmed down to
the minimum. Changes for Qt3 compatibility or for things that are just
not needed anymore have been removed.
* Several post-configure targets in the PyQt ports have been removed, as
they had no effect on the way the ports were built whatsoever.
* In some cases, instead of calling Python's py_compile.py on `ls *.py
*/*.py */*/*.py` to generate .pyc and .pyo files, we just call
compileall.py, which is made for this kind of task.
* The patch + sed hack to build py-qt4-dbussupport has been replaced by
only extracting the dbus/ directory for that port and excluding it from
all others.
* Move the bulk of the code in all Makefiles to bsd.pyqt.mk, like the
non-Python Qt ports do with bsd.qt.mk and the QT_DIST variable. A large
portion of all PyQt Makefiles were very similar and contained a lot of
boilerplate code that can be shared among all of them since they all
come from the same tarball. bsd.pyqt.mk now has a PYQT4_DIST variable
that, when set, automatically sets several common variables and the
do-configure target for a port. This allows us to considerably reduce
the size of all the py-qt4-* Makefiles.
* To make the above possible and also to allow us to use as many OPTIONS
helpers as possible, the ARGS variable is now called CONFIGURE_ARGS.
That's what it was used for anyway.
PR: 191990
Since FreeBSD 8.4 and FreeBSD 9.1 make(1) do support :tu and :tl as a
replacement for :U and :L (which has been marked as deprecated)
bmake which is the default on FreeBSD 10+ only support by default
:tu/:tl a hack has been added at the time to support :U and :L to ease
migration. This hack is now not necessary anymore
Note that this makes the ports tree incompatible with make(1) from
FreeBSD 8.3 or earlier
With hat: portmgr
Add OPTIONS for SQL backends
Disable Oracle support by default (so tora can be compiled for amd64 with other SQL backends)
PR: ports/148328
Submitted by: Cezary Morga <cm@therek.net>
Approved by: itetcu@ (mentor) implicit
Feature safe: yes
-Update libtool and libltdl to 2.2.6a.
-Remove devel/libtool15 and devel/libltdl15.
-Fix ports build with libtool22/libltdl22.
-Bump ports that depend on libltdl22 due to shared library version change.
-Explain what to do update in the UPDATING.
It has been tested with GNOME2, XFCE4, KDE3, KDE4 and other many wm/desktop
and applications in the runtime.
With help: marcus and kwm
Pointyhat-exp: a few times by pav
Tested by: pgollucci, "Romain Tartière" <romain@blogreen.org>, and
a few MarcusCom CVS users. Also, I might have missed a few.
Repocopy by: marcus
Approved by: portmgr
Specifically, newer autoconf (> 2.13) has different semantic of the
configure target. In short, one should use --build=CONFIGURE_TARGET
instead of CONFIGURE_TARGET directly. Otherwise, you will get a warning
and the old semantic may be removed in later autoconf releases.
To workaround this issue, many ports hack the CONFIGURE_TARGET variable
so that it contains the ``--build='' prefix.
To solve this issue, under the fact that some ports still have
configure script generated by the old autoconf, we use runtime detection
in the do-configure target so that the proper argument can be used.
Changes to Mk/*:
- Add runtime detection magic in bsd.port.mk
- Remove CONFIGURE_TARGET hack in various bsd.*.mk
- USE_GNOME=gnometarget is now an no-op
Changes to individual ports, other than removing the CONFIGURE_TARGET hack:
= pkg-plist changed (due to the ugly CONFIGURE_TARGET prefix in * executables)
- comms/gnuradio
- science/abinit
- science/elmer-fem
- science/elmer-matc
- science/elmer-meshgen2d
- science/elmerfront
- science/elmerpost
= use x86_64 as ARCH
- devel/g-wrap
= other changes
- print/magicfilter
GNU_CONFIGURE -> HAS_CONFIGURE since it's not generated by autoconf
Total # of ports modified: 1,027
Total # of ports affected: ~7,000 (set GNU_CONFIGURE to yes)
PR: 126524 (obsoletes 52917)
Submitted by: rafan
Tested on: two pointyhat 7-amd64 exp runs (by pav)
Approved by: portmgr (pav)
