Those items were added with %%DEBUG%% when we updated Qt to 5.3.2. At the time,
src/dialogs/dialogs.pro had the following excerpt:
# In case of a debug build, deploy the QML files too
CONFIG(debug, debug|release): QML_FILES += $$DIALOGS_QML_FILES
but that actually changed in Qt 5.9.0, which dropped the check altogether and
always adds those files to QML_FILES.
Not shipping them causes runtime issues according to the bug report below.
PR: 225347
Submitted by: Tomasz Kowalczyk <kowalczt@zoho.eu>
- Add JSONC option, disabled by default
These options allow controlling two optional dependencies of girara,
which where being silently linked if present on the system when
compiling.
PR: 224876
Submitted by: pawel@
MFH: 2018Q1
variables deprecation revision
WITHOUT_NLS 2013-12-13 r336337
WITH_/WITHOUT_ 2014-02-24 r345870
NOPORT(DOC|EXAMPLE)S 2014-04-19 r351587
WITH_BDB_VER 2016-05-02 r414444
OVERRIDE_LINUX_BASE_PORT 2016-09-05 r421387
WITH_OPENSSL_(BASE|PORT) 2016-06-16 r416965
While there, add an ERROR variable that works like DEV_ERROR, but for
user facing errors, and move NOPORTDOCS,
NOPORTEXAMPLES and WITHOUT_NLS to it.
Cleanup bsd.sanity.mk a bit.
Fix fallout.
PR: 224613
Submitted by: mat
Exp-run by: antoine
Sponsored by: Absolight
Differential Revision: https://reviews.freebsd.org/D13490
gtkplatform is a Qt Platform Abstraction plugin providing Qt applications with
the capability to use GTK+ as a host toolkit.
It lets Qt applications render with native GTK+ menus, and use GTK+ for input
(mouse, keyboard, touch), and getting window content on screen, the same as it
uses e.g. Cocoa on macOS.
WWW: https://github.com/CrimsonAS/gtkplatform
PR: 224453
Submitted by: Greg V <greg@unrelenting.technology>
In file included from module.cc:3:
../../glib/glibmm/module.h:30:1: error: no member named 'string' in the global namespace; did you mean '::std::string'?
GTKMM_USING_STD(string)
^~~~~~~~~~~~~~~~~~~~~~~
../../glib/glibmmconfig.h:60:57: note: expanded from macro 'GTKMM_USING_STD'
# define GTKMM_USING_STD(Symbol) namespace std { using ::Symbol; }
^~
/usr/include/c++/v1/iosfwd:194:65: note: '::std::string' declared here
typedef basic_string<char, char_traits<char>, allocator<char> > string;
^
class.cc:40:5: error: non-constant-expression cannot be narrowed from type 'guint'
(aka 'unsigned int') to 'guint16' (aka 'unsigned short') in initializer list
[-Wc++11-narrowing]
base_query.class_size,
^~~~~~~~~~~~~~~~~~~~~
class.cc:40:5: note: insert an explicit cast to silence this issue
base_query.class_size,
^~~~~~~~~~~~~~~~~~~~~
static_cast<guint16>()
[...]
Reported by: antoine (via bug 224669)
Obtained from: upstream (glibmm 2.31.2)
Suggested by: tijl (autoreconf)
kernel/qx11embed_x11.cpp:486:20: error: non-constant-expression cannot be narrowed from type 'unsigned int' to 'long' in initializer list [-Wc++11-narrowing]
long data[] = {XEMBED_VERSION, XEMBED_MAPPED};
^~~~~~~~~~~~~~
kernel/qx11embed_x11.cpp:486:20: note: insert an explicit cast to silence this issue
long data[] = {XEMBED_VERSION, XEMBED_MAPPED};
^~~~~~~~~~~~~~
static_cast<long>( )
PR: 224945
This took quite a lot of time because Qt's own build system underwent
several changes in 5.8.0 that took a while to adapt to.
And, of course, qt5-webengine is a behemoth that we need to patch like crazy
due to its bundling of Chromium. In fact, most of the Chromium patches in
qt5-webengine have been imported with no changes from www/chromium@433510
("www/chromium: update to 56.0.2924.87").
New port: accessibility/qt5-speech
Bigger changes to Qt5 ports we had to make:
- Qt now allows using a configure.json file to define configuration options
and specify configuration checks that can be done when qmake is invoked.
However, configure.json checks done in a subdirectory only propagates to
subdirectories, and checks elsewhere will fail if all .pro files are being
parsed at once (i.e. qmake -recursive), so several ports had to switch to
USES=qmake:norecursive along with manual additional qmake invocations in
subdirectories in order to work. It's been mentioned in a few places such
as Qt's bug tracker that qmake's recursive mode is pretty much deprecated,
so we might switch to non-recursive mode by default in the future.
- Uses/qmake.mk: Introduce QMAKE_CONFIGURE_ARGS. qmake now accepts
arbitrary options such as '-foo' and '-no-bar' at the end of the
command-line. They can be specified in QMAKE_CONFIGURE_ARGS.
- graphics/qt5-wayland: The port can only be built if graphics/mesa-libs is
built with the WAYLAND option, so a corresponding option (off by default)
was added to the port.
- misc/qt5-doc: Switch to a pre-built documentation tarball. The existing
port was not working with Qt 5.9. Instead of trying to fix it, switch to
what Gentoo does and fetch a tarball that already contains all
documentation so that we do not have to build anything at all. The
tarball's name and location in download.qt.io look a bit weird, but it
seems to work fine.
- www/qt5-webengine: Use binutils from ports, Chromium's GN build system
generates a build.ninja that uses ar(1) with the @file syntax that is not
supported by BSD ar, so we need to use GNU ar from binutils.
- x11-toolkits/qt5-declarative-render2d: This port was merged into the main
Qt Declarative repository upstream, and into x11-toolkits/qt5-quick in the
ports tree.
Changes to other ports we had to make:
- biology/ugene: Drop a '#define point "."' that is not present in more
recent versions of the port. Defining a macro with such a common name
causes build issues with Qt 5.9, which uses |point| as an argument name in
methods.
- cad/qelectrotech: Fix plist with Qt 5.9. Directories are no longer
installed with `cp -f -R', but rather `qmake install qinstall', which does
not install
%%DATADIR%%/elements/10_electric/20_manufacturers_articles/bosch_rexroth/.directory
That's a local file that should not even have been part of the tarball
anyway.
- chinese/gcin-qt5: Add additional private Qt directories (which should not
be used in the first place) to get the port to build with Qt 5.9.
- devel/qtcreator: Fix plist with Qt 5.9. Something changed in qdoc and some
test classes no longer generate documentation files.
- security/keepassx-devel: Import a patch sent upstream almost a year ago to
fix the build with Qt 5.9.
Thanks to antoine for the exp-run, and tcberner and Laurent Cimon
<laurent@nuxi.ca> for landing changes in our qt-5.9 branch.
PR: 224849
x11-toolkits/gnome-sharp20:
- update to version 2.24.4
- use github for sources
- use autoreconf and provided bootstrap script (pre-configure)
- remove gettext-runtime, not used by port
- order USES section, move non-USES related variables to own section
x11-toolkits/gtk-sharp20:
- update to version 2.12.45
- remove gettext-runtime, not used by port
- order USES section, move non-USES related variables to own section
Differential Revision: https://reviews.freebsd.org/D13751
- Consistently use DISTVERSION instead of PORTVERSION (the former is set, not the latter)
- Only depend on libunwind on x86 arch with FreeBSD >= 11 (fixes ignored build on arm/ppc)
- Fix python dependency with depreciation of python meta ports
- Remove PYPY_BITS from pkg-plist target, no longer used
- Remove setting of PORTVERSION, DISTVERSION is set in bsd.pypy.mk
- bsd.pypy.mk:
- Define DISTVERSION once, to ensure consistency
- PYPY_DIR: Handle versions with multiple digits
- PYPY_CFFI_VER now differs in value between pypy and pypy3
- bsd.pypy.cffi.mk:
- Add FLAVORS for pypy and pypy3 [1]
- Consistently use PYTHON_IMPL instead of the hard coded "pypy"
- PLIST_FILES: use direct substitution instead of PLIST_SUB
Approved by: portmgr (mat) [1]
Differential Revision: https://reviews.freebsd.org/D13675
Upstream no longer ships the contents of misc/py-qt5-doc, so the port has been
removed.
This is also a requirement for updating the Qt5 ports, as the PyQt5 version
currently in the tree has license conflicts with later Qt versions.
Big thanks to tcberner for doing most of the work here, and antoine for the
exp-run.
PR: 224739
We were not setting the flag to select the GNUstep ABI, so were defaulting to
using the GCC-compatible version, which was likely to trigger a lot of subtle
bugs. This was noticed when C++ exceptions thrown through Objective-C stack
frames caused segfaults.
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
armv7, mark them so.
This is part two of a multipart commit to bring armv7 ports to parity
with armv6.
Approved by: portmgr (tier-2 blanket)
Obtained from: lonesome.com -exp run
It was recently killed in the base system and consumers have to use
`textproc/groff' port now, which is a real PITA: it pulls in some
obscure dependencies like `print/psutils', `graphics/netpbm', but
most importantly, `ghostscript' (unconditionally), which is a huge
abomination of its own, pulling another round of dependencies, some
of which are as crazy as `graphics/svgalib' (sic). Trying to reset
all offered knobs to `off' results in unbuildable package.
Pass NROFF as mere `echo' and be done with it. Generated manpages
remain identical.
2017-11-20 news/brag: Tcl/Tk 8.4 is no longer maintained, please use 8.5+
2017-11-20 textproc/srilm: Tcl/Tk 8.4 is no longer maintained, please use 8.5+
2017-11-20 x11-toolkits/tk84: Tcl/Tk 8.4 is no longer maintained, please use 8.5+
2017-11-20 devel/tkinspect: Tcl/Tk 8.4 is no longer maintained, please use 8.5+
2017-11-20 games/bogged: Tcl/Tk 8.4 is no longer maintained, please use 8.5+
2017-11-20 games/ttraffic: Tcl/Tk 8.4 is no longer maintained, please use 8.5+
2017-11-20 games/ifm: Tcl/Tk 8.4 is no longer maintained, please use 8.5+
2017-11-20 games/tksol: Tcl/Tk 8.4 is no longer maintained, please use 8.5+
2017-11-20 lang/tcl84: Tcl/Tk 8.4 is no longer maintained, please use 8.5+
2017-11-20 mail/tkrat2: Tcl/Tk 8.4 is no longer maintained, please use 8.5+
2017-11-20 multimedia/dtv: Tcl/Tk 8.4 is no longer maintained, please use 8.5+
2017-11-20 net-mgmt/netwag: Tcl/Tk 8.4 is no longer maintained, please use 8.5+
