Marketing blurb [1]:
QtWayland is a Qt 5 module that wraps the functionality of Wayland.
QtWayland is separated into a client and server side. The client side
is the wayland platform plugin, and provides a way to run Qt applications
as Wayland clients. The server side is the QtCompositor API, and allows
users to write their own Wayland compositors.
This is mostly needed at the moment to make upstream KDE-CI happy, therefore
we don't wire it into the metaport devel/qt5.
It requires a little change to devel/qt5-qmake, as we needed to modify the
installed bsd.conf to know about wayland/egl.
Created together with Adriaan de Groot <groot@kde.org>.
Reviewed by: rakuco, groot_kde.org
Differential Revision: https://reviews.freebsd.org/D11744
With the current code, if you use ZI, it will not expand LOCAL/ZI. It
would have worked if you use ${MASTER_SITE_ZI} everywhere though. It'll
end up trying to fetch from, literally, LOCAL/zi/some-file.tgz.
Sponsored by: Absolight
Rework the adding of dependancies in Mk/bsd.gstreamer.mk.
Previous when using USE_GSTREAMER[1] it would just add the request modules to BUILD/RUN_DEPENDS. This caused the qa script to complain because the old code didn't implicit depend on the gstreamer1 and gstreamer1-plugins[-bad] ports for the libraries they carried, even if they where present via the plugins! The new code adds implicit depends on these ports so USE_GSTREAMER[1] using ports have all the libraries included.
* The mad mp3 plugin was removed, mpg123 plugin also provides mp3 decoding. Switch over ports that used the gstreamer1 mad plugin.
* gtksink plugin renamed -> gtk
* Hook up the sndio plugin into the framework
* Add some indirect dependacies where needed
* Reorder the plugin list in bsd.gstreamer.mk so only one plugin per line. When changing plugins it doesn't result in multiple lines being changed.
* Remove mentions in bsd.gstreamer.mk of plugins mentions that where removed.
* Depend on libunwind on i386/amd64, GStreamer links to it if it is present.
PR: 220753
Exp-run by: antoine@
Repeat after me: If you change IFS, it will break something unexpected.
The problem is that we use IFS to change read's field separator. This
has the side effect of changing how sh(1) splits all string, including
in command parsing functions.
In this case, unless quoted, the strings are always splitted using IFS.
So changing IFS will change how these strings are splitted, and you end
up having a headache. For example:
$ GID_FILES="foo bar"
$ set -x
$ echo $GID_FILES
+ echo foo bar
foo bar
$ IFS=:
$ GID_FILES="foo bar"
$ set -x
$ echo $GID_FILES
+ echo 'foo bar'
foo bar
In the first case, it runs echo with two arguments, first is foo, second is bar.
In the second case, it runs echo with one argument, 'foo bar'.
To fix this, restrict the time during which IFS changes to only one
command, set, and use positional parameters to extract values.
Reported by: feld
Sponsored by: Absolight
Differential Revision: https://reviews.freebsd.org/D11632
On x86 architectures when base compiler doesn't support C++14
USES=compiler prefers Clang. As only lang/gcc* provide C++14 library
outside of base some ports need to define USE_GCC. However, adding it
would require ugly bsd.port.options.mk conditionals thus FAVORITE_COMPILER
was used. As /stable/9 reached EOL we no longer need to support ancient
libstdc++ on x86.
Since ruby detects this if it's installed, and it's more often installed now
due to other deps, and ruby provides no way to not depend on it if it's found,
pull it in as a dependency unconditionally. While here, fix plist for ruby 2.4
with the CAPIDOCS option on, and restore the MAKE_JOBS_UNSAFE flag when using
that build option since it's not fixed like I thought it was.
PR: 219796
Reported by: Grzegorz Junka <list1@gjunka.com>
libdeclarative_qmlwebsockets.so is not installed into ${QT_LIBDIR}, which
causes the dependency logic in bsd.qt.mk to actually do something equivalent to
this instead:
BUILD_DEPENDS+= ${QT_LIBDIR}/${QT_QMLDIR}/QtWebSockets/libdeclarative_qmlwebsockets.so:www/qt5-websockets-qml
RUN_DEPENDS+= ${QT_LIBDIR}/${QT_QMLDIR}/QtWebSockets/libdeclarative_qmlwebsockets.so:www/qt5-websockets-qml
which translates into something like
/usr/local/lib/qt5//usr/local/lib/qt5/qml/QtWebSockets/libdeclarative_qmlwebsockets.so:www/qt5-websockets-qml
which obviously does not exist.
Instead of settin websockets-qml_LIB, set websockets-qml_PATH like we do for
other QML ports, so that our dependency logic does not needlessly prepend
${QT_LIBDIR} there. This fixes devel/qt5's build.
PR: 220045
This splits qt5-websockets into a qt5-websockets port containing the core parts,
and a qt5-websockets-qml port with the QML parts. The QML parts depend on Qt Quick,
so on the GUI parts (and hence X11) while the core parts do not.
PR: 220045
Submitted by: Adriaan de Groot <groot@kde.org>
- Update all ports that currently use a custom definition
- Also add a link to a list of certified copyfree licenses
Approved by: portmgr (mat)
Differential Revision: https://reviews.freebsd.org/D11487
* The MATE DE is now GTK+3 based
* mate-calc has come back.
* New USE_MATE=mixer macro
* Add license
* Review dependancies
* Swich to USES=localbase
* atril/eom options reworked into option helper
Thanks to Eric Turgeon for submitting the bulk of this MATE update.
Obtained from: gnome devel repo
Move `files.pythonhosted.org` mirror to the top
The mirror `pypi.python.org` soon will be replaced with the
new Warehouse [1][2], now it's only serving the old files
and its returning `404 - Not Found` to the new files hosted
[1] https://pypi.org
[2] https://github.com/pypa/warehouse
Approved by: garga (mentor), python (sunpoet)
Differential Revision: https://reviews.freebsd.org/D11420
Using ninja instead of make (1) can lead to significant speed ups while building.
Therefore switch from having the ninja generator opt-in to having it opt-out.
Previously cmake-ports that wanted to use ninja could set
CMAKE_NINJA=yes
now, ports that do not work with ninja can set
cmake:<existing args>,noninja
Note, that needing this should be an exception and most often points to a broken
cmake of the port.
The ports using cmake were modified
* removed USES=gmake, if ninja is used
* removed MAKE_ARGS, if ninja is used
* added the cmake-argument noninja if necessary
PR: 219629
PR: 213331
Exp-run by: antoine
Reviewed by: rakuco
Differential Revision: https://reviews.freebsd.org/D10748
* qtdiag outputs diagnostics on the current Qt installation and can be helpful to find issues.
* qtpluginfo is useful while writing plugins for Qt5/KDE Plasma
Reviewed by: rakuco, mat
Differential Revision: https://reviews.freebsd.org/D11280
If NO_ARCH is set then check that no FreeBSD elf(5) files are in $STAGEDIR.
If an elf(5) file is bundles as part of the package, but is not meant to be
run directly (i.e. the elf(5) file is a payload, and not compiled) then
those files can be added to NO_ARCH_IGNORE to avoid the check from failing,
Changes to ports:
- Ports that have NO_ARCH set, but actually compile files have had NO_ARCH
removed.
- Ports that have elf(5) payloads have had those files added to
NO_ARCH_IGNORE.
- R-cran ports that do not set USES=cran:compiles have NO_ARCH set,
PR: 218976
Reviewed by: antoine, mat
Approved by: portmgr
The port's own USES may note that is only supports certain versions. If it
is attempted to build an unsupported version there's no reason to even
try. Rather than giving a WARNING, actually mark it IGNORE.
Currently this should only impact devel/py3-enum34 which does not support
the default python3 version of 3.6.
With hat: portmgr
For example a option of the "boolean" type only accepts true/false this
option is covered by ${opt}_MESON_TRUE/_FALSE.
Add option helpers ${opt}_MESON_YES/_NO for the "combo" type which
accepts yes and no.
Approved by: portmgr@ (mat@)
Differential Revision: https://reviews.freebsd.org/D11078
libdata/pkgconfig.
Fix ports that where installing the file in the wrong place.
PR: 218067
Submitted by: mat
Exp-run by: antoine
Reviewed by: rene, antoine
Sponsored by: Absolight
Differential Revision: https://reviews.freebsd.org/D10129
