SSL_CIPHER and SSL_CTX will become opaque in libssl. Add the two accessors
SSL_CTX_get_cert_store() and SSL_CIPHER_get_bits() to the qsslsocket
symbol wrangling and use them inside the code similar to what was done
in wkhtmltopdf. This adds two symbols to QtNetwork, so bump its minor and
those of the two remaining dependent libraries.
no response from maintainer
Disable QtOpenGL, QtMultimedia, QtXmlPatterns, QtScriptTools, QtWebKit,
phonon, QtDeclaratin, QtScriptTools to save CPU- and lifetime.
Nothing depends on it.
Many +1
They mostly consist to make gcc-8 pose as gcc-4.9.
Bump SHARED_LIBS due to an ICU-related qtcore change.
While here, fix trailing whitespaces in DESCR and move
HOMEPAGE to https.
OK sthen@ jca@
some existing COMPILER lines with arch restrictions etc. In the usual
case this is now using "COMPILER = base-clang ports-gcc base-gcc" on
ports with c++ libraries in WANTLIB.
This is basically intended to be a noop on architectures using clang
as the system compiler, but help with other architectures where we
currently have many ports knocked out due to building with an unsuitable
compiler -
- some ports require c++11/newer so the GCC version in base that is used
on these archirtectures is too old.
- some ports have conflicts where an executable is built with one compiler
(e.g. gcc from base) but a library dependency is built with a different
one (e.g. gcc from ports), resulted in mixing incompatible libraries in the
same address space.
devel/gmp is intentionally skipped as it's on the path to building gcc -
the c++ library there is unused in ports (and not built by default upstream)
so intending to disable building gmpcxx in a future commit.
have been missed previously listed because Qt likes to dlopen() things
so check-lib-depends can't find it, which would stop qt4 getting updated
when ssl/crypto libs are updated.
/usr/local/lib/qt4/bin/findtr: a /usr/bin/perl -w script text executable
/usr/local/lib/qt4/bin/syncqt: a /usr/bin/perl -w script text executable
These are both perl scripts, so use INSTALL_SCRIPT instead of
INSTALL_PROGRAM.
While here: qt-project.org -> qt.io in some comments.
This removes support of separate qmake versions in one port: as we
discovered, there are no ports actually needing this; strangers like
print/poppler don't use qmake in build.
This should be transparent to current ports. But expect more tweaks there:
for now, qt?.port.mk forces qmake.port.mk inclusion, but that will be
reworked to a more common scheme.
Same idea from (at least) espie@ and me; also, espie@ agrees on the plan.
an opt-in. Actual qmake-based ports will be switched on case-by-case
basis in the near future.
Unslacking after discussion with at least naddy@ & espie@ from... 2014?!
Oh my.
FD_SETSIZE (1024 by default) file descriptors. This is often the case
for KDE4 apps when using libinotify as directory monitoring backend.
Positive feedback from deraadt@, final okay sthen@
It was the same story again: TLSv1_*_method() are TLSv1.0, not TLSv1.x.
Should fix problems landry@ and sthen@ (and likely others) were seeing.
Joint work with and final okay sthen@
