- Update devel/py-efl to 1.13.0
- Update graphics/evas_generic_loaders-* to 1.13.0
- Update multimedia/emotion_generic_players-vlc to 1.13.0
- Update x11-toolkits/elementary to 1.13.0
and -fvisibility-inlines-hidden and uses it if available to reduce shared
library size. Unfortunately, this hides Fl_XFont_On_Demand::value, which
in turn causes undefined reference errors during linking. Fix by marking
Fl_XFont_On_Demand class as FL_EXPORT for the time being (Gentoo Linux is
doing the same)
- Do not strip libraries for now: FLTK uses the same command for installing
both dynamic and static libraries, but "fltk-config(1) --compile" prefers
static, which breaks programs like `graphics/iccexamin' (threading test)
- Pull another patch from Gentoo to fix segmentation fault in vncview(1) of
port `net/tigervnc' (Gentoo bug #529856 by Maxim Britov)
- Do not leak non-existent (build-time only) -Lfoo references in LDFLAGS as
it can potentially lead to various sporadic bugs in programs which obtain
these flags through fltk-config(1). To prevent build-time conflicts that
this gimmick was originally used for, we change shared linking command of
fluid(1) accordingly
Since these are one-line changes likely to be merged upstream sooner rather
than later, perform them with sed(1) instead of trivial patches.
Reported and reviewed by: antoine
knobs; resurrect documentation/Makefile patch; bring back recalculation of
${ETCDIR} length in Fl_Preferences.cxx, trim CONFIGURE_ARGS (again), etc.
- Restore correct LDFLAGS+= -L../src (previously -L${WRKSRC}/src), otherwise
the build fails with e.g. previous version of FLTK libraries installed
- Take maintainership to prevent Kato's monkeys jeopardizing it all over again
- Install code examples as PORTEXAMPLES (we do not install any documentation
because it requires LaTeX stack to build)
- Since `post-patch' target is a bit too verbose now, make it .SILENT
- Do not compile things with -Os by default (already honors user's CXXFLAGS)
- Do not blindly strip libraries and fluid(1) binary (respect ${STRIP} value)
- Sort the knobs, remove "default=yes" arguments from CONFIGURE_ARGS
- In post-staging era, conditional installation of documentation is no
longer necessary, so simplify the patch and drop post-install target
Make sure we use openjpeg1 in poppler, while openjpeg2 support
was added there still bugs in openjpeg2 that need to be fixed.
Add patches to inkscape for API changes in poppler 0.29.0 [2].
PR: 196599 [1]
Submitted by: olivierd@ [1]
Exp-run by: antoine@
Obtained from: upstream [2]
Some dependent ports may need USES=compiler:c++11-lib as well
PR: 196703 [1], 197031 [2]
Submitted by: beastie@tardisi.com [1], amdmi3 [2]
Approved by: portmaster@bsdforge.com (maintainer)
MFH: 2015Q1
Also tested with CMake 3.0.2. The patch itself contains an explanation of
what is being changed and why.
There is no need to bump PORTREVISION as there are no functional changes.
Update totem to 3.14 now that we have gstreamer 1.4 and minor gnome updates.
Update evolution suite to 3.12.9.
Make sure gtk30 pulls in adwait-icon-theme, since it now the default theme [3].
PR: 195290 [1], 195289 [2], 195455 [3]
Obtained from: gnome devel repo
Changelog:
Fixed error with conflicting libvte/Gtk versions
Fixed ebuild (by Ilya Mochalov).
Suppress "invalid option" for -e.
Fixed missing link to math library (by Thomas Koch)
Miminum required version for Gtk-2 changed to 2.24.
Miminum required version for libvte changed to 0.28.
Rebuild po-files due to source changes.
This knob was turned on for all version of FreeBSD in r369875
(2014-10-03) and officially deprecated. Since then, it was gradually
removed from many ports when they needed an update.
x11-servers/xorg-server was the last major user of this knob. The port
was updated to xserver 1.14 in r374982 (2014-12-19). The update got rid
of the knob, clearing the path to the final removal.
This commit changes ports who were checking for WITH_NEW_XORG and remove
its handling from bsd.port.mk.
While here, two sanity checks are added to warn user about WITH_KMS and
WITH_NEW_XORG which have no effect now.
Differential Revision: https://reviews.freebsd.org/D1351
Reviewed by: antoine, bapt, kwm
Approved by: portmgr (antoine, bapt), kwm
These ports require msgfmt. FreeBSD doesn't fail to build these ports
because a default option on gvfs brings in this tool. The same gvfs
option is off by default on DragonFly and thus the missing dependencies
were unmasked. Explicitly add gettext-tools to get msgfmt.
the 32 ports that still use it. Bump PORTREVISION on their dependent
ports except the ones that depend on these:
audio/libogg
audio/libvorbis
devel/pcre
ftp/curl
graphics/jpeg
graphics/libart_lgpl
graphics/tiff
textproc/expat2
textproc/libxslt
In these cases the same trick as in the recent gettext update is used.
The ports install a symlink with the old library version. When enough
of their dependent ports have had regular updates the remaining ones can
get a PORTREVISION bump and the links can be removed.
Also remove the devel/pcre dependency from USE_GNOME=glib20. It causes
over 2200 packages to depend on devel/pcre while less than 200 actually
link with it. The glib20 package still depends on devel/pcre so this
should not make a difference for ports with USE_GNOME=glib20. Also,
libdata/pkgconfig/glib-2.0.pc lists pcre as a private library so
USE_GNOME=glib20 should not propagate it.
PR: 195724
Exp-run by: antoine
Approved by: portmgr (antoine)
This update was brought to you in collaboration with Gustua Perez
Make sure gtk30 pulls it the default theme (adwaita-icon-theme).
Update the extra gnome-shell-extensions so they work with gnome-shell 3.14.
Drop metacity from gnome3 meta-port.
Remove the gtile gnome-shell extension since it proven to be buggy.
Exp-run done by antoine@ for gdk-pixbuf2 deprecated API.
PR: 195414
Obtained from: gnome dev repo
first contains runtime libraries such as libintl and the latter contains
developer tools such as msgfmt. Ports that use gettext will usually need
a LIB_DEPENDS on gettext-runtime and a BUILD_DEPENDS on gettext-tools.
USES=gettext-runtime can be used to set a LIB/BUILD/RUN_DEPENDS on
devel/gettext-runtime and USES=gettext-tools can be used to set a
BUILD/RUN_DEPENDS on devel/gettext-tools. USES=gettext is now the same
as "USES=gettext-runtime gettext-tools" meaning a LIB_DEPENDS on
devel/gettext-runtime and a BUILD_DEPENDS on devel/gettext-tools.
Update gettext to 0.19.3.
Remove :oldver from converters/libiconv and devel/gettext-runtime. Leave
symlinks with the old library versions to avoid the need to bump
PORTREVISION on a large number of dependent ports. When most of the
dependent ports have had normal version updates, PORTREVISION can be
bumped on the remaining ones (low number) and the links can be removed.
Fix some ports that installed files in lib/locale instead of share/locale.
PR: 194038
Reviewed by: bapt
Exp-run: antoine
Approved by: portmgr (antoine)
Before, we had:
site_perl : lib/perl5/site_perl/5.18
site_perl/perl_arch : lib/perl5/site_perl/5.18/mach
perl_man3 : lib/perl5/5.18/man/man3
Now we have:
site_perl : lib/perl5/site_perl
site_arch : lib/perl5/site_perl/mach/5.18
perl_man3 : lib/perl5/site_perl/man/man3
Modules without any .so will be installed at the same place regardless of the
Perl version, minimizing the upgrade when the major Perl version is changed.
It uses a version dependent directory for modules with compiled bits.
As PERL_ARCH is no longer needed in plists, it has been removed from
PLIST_SUB.
The USE_PERL5=fixpacklist keyword is removed, the .packlist file is now
always removed, as is perllocal.pod.
The old site_perl and site_perl/arch directories have been kept in the
default Perl @INC for all Perl ports, and will be phased out as these old
Perl versions expire.
PR: 194969
Differential Revision: https://reviews.freebsd.org/D1019
Exp-run by: antoine
Reviewed by: perl@
Approved by: portmgr
- Update x11-toolkits/elementary to 1.12.0
- Update x11-wm/enlightenment to 0.19.1
- Update graphics/evas_generic_loaders-* to 1.12.0
- Update devel/e_dbus to 1.7.10
- Update benchmarks/expedite to 1.7.10
- Move some of x11-wm/e17-module-* to x11-wm/e-module-*
and update to recent snapshots
- Add multimedia/emotion_generic_players-vlc
- Add multimedia/rage
Reviewed by: crees, antoine
- Remove CPPFLAGS/LDFLAGS augmentation, it is not needed
- Sort USES, make COMMENT more in line with pkg-descr
- Remove @dirrm lines from pkg-plist and convert to PLIST_FILES
since it is down to four lines now
Gnome 3.14.1 and Cinnamon 2.2.16 are supported on FreeBSD 9.3-RELEASE and up.
This commit removes the old GNOME 2 desktop, bindings and some ports that
can't be compiled. A few ports where updated to more recent versions to
allow them to compile with this update.
Apart from updating ports to newer versions
GDM is more integrated with gnome-shell now, and handles several things for
the GNOME desktop such as screen locking. If you want to use GNOME 3 via
startx, you will have to add your own lock screen/screensaver. For example xscreensaver
can be used for sessions started without GDM.
Shell Extensions can be installed via https://extensions.gnome.org/ , we have
ported a few that can't be installed via this way.
The old gnome-utils and gnome-games ports where split up into single ports
and where converted to meta-ports.
gnome-terminal requires a UTF-8 locale to run, gdm handles this already, but
if you use startx you need to do this yourself.
Upgrade instructions:
Delete the old and conflicting packages:
# pkg delete clutter gnome-utils gnome-panel gnome-keyring vala-vapigen \
guile gcalctool gnome-media libgnomekbd
# pkg delete gnome-screensaver gnome-applets bug-buddy evolution-exchange \
evolution-webcal gnome-system-tools seahorse-plugins gnome-control-center
For package users the following lines will be enough:
# pkg upgrade
# pkg install gnome3
For ports users should do the following:
# portmaster -a
# portmaster x11/gnome3
We are currently aware of two issues. The first issue is a bug in the
file monitoring code in the glib20 port. This bug causes glib programs
to crash when files in a monitored directory are added or removed.
Upstream is aware of the problem, but since the problem is quite complex
there is no solution yet. This problem isn't restricted to BSD.
The second issue is that on certain video cards totem will display a
purple/pink overlay on the video. It not clear yet where the issues
comes from.
Major thanks goes to Gustau Perez for being a driving force behind getting
GNOME 3 up to speed again. Also thanks to Antoine Brodin for running the exp-runs.
This update was also made possible by:
Joe Maloney
Kris Moore
Beeblebrox
Ryan Lortie
Antoine Jacoutot
and everyone I missed
Since r372179 we are using the QML headers from the tarball, not the ones
installed system-wide by qt5-qml.
While this is not a problem and is kind of intended, it also means we need
to apply patches like this one to both ports now.
Simply patching src/src.pro to remove those directories from the build does
not work in all cases. If an older version of qt5-quick is installed, their
.pri files in mkspecs/modules will be picked up, and in the end when linking
programs such as tools/qmltestrunner something like this happens:
c++ [...] -Wl,-rpath-link,/usr/local/lib -o ../../bin/qmltestrunner
-L${WRKSRC}/lib -lQt5QuickTest [...]
The -rpath-link linker option will make ${LOCALBASE}/lib take precedence in
directory lookups, so when the newly-built libQt5QuickTest.so asks for
libQt5Quick.so in its DT_NEEDED section the older version installed in
${LOCALBASE}/lib will be used instead of the one that has just been built.
If the new version has symbols the older one does not (Qt releases are
backwards, not forwards, compatible), the build will fail.
So instead of patching src/src.pro, we let the configuration process proceed
without any patching so that the local .pri files are created in
${WRKSRC}/mkspecs and the Makefiles are created in a way that -rpath-link is
not passed to the linker anymore. We only need to symlink the existing
libraries built by lang/qt5-qml (this is similar to what we do with qtbase
ports to avoid rebuilding tools such as qmake and moc), and then change the
Makefiles in src/qml and src/qmldevtools so that nothing gets built.
This might even be a solution for other ports that got .pro patches in
r372179, since depending on which parts depend on which the same thing could
happen in the future.
I'm not bumping PORTREVISION because the resulting binaries will not change
and this only fixes the build where it was broken before.
PR: 194870
Proudly presented by the KDE on FreeBSD team, with several guest stars.
This update took way longer than initially expected due to us previously
accumulating assumptions and changes to Qt's build system that finally bit
us back with the 5.3 release series, so we had to do a fair amount of
cleanup.
New ports:
- comms/qt5-serialport: Qt functions to access serial ports, originally
based on work by Fernando Apesteguia. [1]
- devel/qt5-qdoc: Qt documentation generator, the Qt5 equivalent of
devel/qt4-qdoc3. Originally worked on by Tobias Berner.
It had already been half-split from devel/qt5-buildtools,
we just needed to finish the work.
Dead ports:
- devel/qt5-qmldevtools: Merged into lang/qt5-qml.
Minor changes:
- devel/qt5: Add x11/qt5-x11extras and the new ports to the dependency list.
- graphics/qt5-imageformats: The port now supports the JPEG2000, WEBP,
Direct Draw Surface and ICNS formats.
- multimedia/qt5-multimedia: The ALSA and PULSEAUDIO options are now
mutually exclusive due to changes introduced in
Qt 5.3.0 (the ALSA code is now a proper plugin
that is only built if PulseAudio is not used).
- x11/qt5-x11extras: Add USE_LDCONFIG since the port installs a shared
library.
The big changes:
- bsd.qt.mk: Set QMAKESPEC instead of QMAKEPATH. [3]
QMAKEPATH does much more than we want now that we call qmake from the top
of ${WRKSRC}. qmake uses QMAKEPATH when evaluating the QMAKE_MKSPECS
property, which is in turn used by qt_config.pri to load the .pri files in
mkspecs/modules.
In practice, this means that if people have an older Qt installation those
files will be used and QT_CONFIG will have values such as "gui" even if
one is building a port like textproc/qt5-xml, which passes -no-gui to the
configure script. Consequently, unintended code paths may be enabled or
the configuration step can just fail if the .pro files expect values that
are not present in the system-wide, older .pri files.
We avoid all those problems if we use QMAKESPEC, as qmake does not take
its value into account when evaluating the QMAKE_MKSPECS property and will
only parse the files in the mkspec's directory (mkspecs/freebsd-clang, for
example, instead of all the files in mkspecs).
- Stop explicitly passing ${LOCALBASE} to the compiler. [3]
qmake's behavior has changed in Qt 5, and the paths set in QMAKE_INCDIR
and QMAKE_LIBDIR in the mkspecs are passed before any others, such as the
ones in the build directory themselves.
In practice, this means that we end up with linker calls like this:
c++ -o libfoo.so foo.o bar.o -L/usr/local/lib -L/wrkdir/build/lib
-lQt5Gui -lQt5Core
So if one already has Qt installed in the system, the older, already
present version of the libraries in /usr/local/lib will be used instead of
the newly-built ones in /wrkdir/build/lib.
QTBUG-40825 discusses this behavior upstream, but there has been no
agreement on a solution yet.
For now, the solution adopted is to make the compiler and the linker aware
of those paths but only try them last after all others, and this is
achieved by setting the CPATH and LIBRARY_PATH environment variables when
qmake is being used.
In addition to setting them in CONFIGURE_ENV and MAKE_ENV, we also need to
stop changing QMAKE_INCDIR and QMAKE_LIBDIR as well as filter those paths
from the pkg-config calls qtbase's configure script makes.
- Call qmake from the root of the ${WRKSRC}.
In Qt 5.3, Qt's build infrastructure has undergone some changes that make
our previous approach of calling qmake from the directories we want to
build stop working. Things would break even more in Qt 5.4, in which
qtbase's configure script does not accept the -process, -fully-process and
-dont-process arguments anymore (it always behaves as if -process had been
used).
Bite the bullet and start calling qmake from ${WRKSRC}. The largest part of
this change involves changing lines in Makefiles from
WRKSRC_SUBDIR= foo/bar
to
BUILD_WRKSRC= ${WRKSRC}/foo/bar
INSTALL_WRKSRC= ${WRKSRC}/foo/bar
as well as adding patches to .pro files to avoid entering other
subdirectories and removing post-configure targets that are not necessary
anymore.
Since qmake needs to be called from the top of ${WRKSRC} anyway, we can
also simplify the configuration process for the qtbase ports a little.
Looking at r10019 it is not clear why we started calling qmake in the
pre-configure target in addition to the post-configure one (while also
skipping it in do-configure), but we can now drop this call since letting
configure behave as if -process had been passed means it will call qmake
on its own and overwrite the files generated by the pre-configure call. We
still need to call qmake in post-configure though, as the configure script
does not pass -recursive when calling qmake and we need to be able to call
make from any subdirectory when building.
PR: 194762 [1]
PR: 194566 # exp-run with base GCC and clang
PR: 194088 [3]
- Add several PORTDOCS to pkg-plist.
- Fix two orphaned files
- Deprecate @dirrm{,try} in favor of @dir where absolutely necessary.
Submitted by: antoine
Differential Revision: https://reviews.freebsd.org/D987
Approved by: swills (mentor)
Alias is a new USES tool that allows DragonFly to masquerade as FreeBSD
by setting CFLAGS+= -D__FreeBSD__. For some ports, this fixes the build
without the need for additional patches.
Approved by: portmgr (bapt, blanket)
- Patch libtool so it uses the same library version specification as on
Darwin, Linux and other systems. Given the version current:revision:age
a library will be given the extension .so.major.age.revision with major
equal to current-age. Before libtool would use .so.current on FreeBSD.
- Patch libtoolize to remove two cases of umask 0 that caused libltdl
files to be copied world writable (--ltdl option)
- Let USES=libtool patch this new version correctly
- Adjust all ports with USES=libtool:build and bump PORTREVISION on their
dependent ports if a library version changed
PR: 194068
Exp-run by: antoine
Approved by: portmgr (antoine)
Cython changes its temporary variable handling and now fails on the file:
kivy/graphics/sahder/pyx
This has already been fixed upstream so just backport that fix.
Also, update the USE_PYTHON et al variables.
PR: 194065
Reported by: John Marino (marino@FreeBSD.org)
Obtained from: https://github.com/kivy/kivy/commit/b2bc566
The Fedora 10 infrastructure ports have been in use since June 2009 and, while
having served a great deed, have become unsupported upstream and hence affected
by unfixed security vulnerabilities. In addition to that, many recent Linux
binaries need newer libc / stdlibc++ versions.
This commit adds the linux-c6- userland as drop-in replacement for the -f10
infrastructure, as well as upgrading the linux_base-c6 port to CentOS 6.5.
If you want to switch to linux-c6 ports, please define at /etc/make.conf:
OVERRIDE_LINUX_BASE_PORT=c6
OVERRIDE_LINUX_NONBASE_PORTS=c6
Additionally, please add the following line to /etc/sysctl.conf:
compat.linux.osrelease=2.6.18
Upgrading procedures are shown in /usr/ports/UPDATING.
This work has been inspired by Artyom Mirgorodskiy's post to emulation@ in
November 2013, using and extending mav@'s work. It has been tested extensively
and most reported issues were already fixed. Please report any additional bug
or "features" to the emulation mailing list.
Many thanks to: mav@, rene@, allanjude@, netchild@, antoine@, everyone who's
filed Issues and Pull requests on GitHub,
PR: 186820
Differential Revision: https://reviews.freebsd.org/D793
Reviewed by: allanjude, antoine, bapt, rene
Approved by: portmgr (antoine, bapt)
Approved by: koobs (mentor)
Sponsored by: Perceivon Hosting Inc.
creates. This fixes a problem on arm where the shared object will attempt to
access symbols in libgcc, however the .so files don't link against libgcc the
build fails.
PR: 193791
Submitted by: andrew
Reviewed by: tijl
Approved by: bapt (mentor)
Also the compat NO_INSTALL_MANPAGES shim.
Differential Revision: https://reviews.freebsd.org/D730
Reviewed by: antoine
With hat: portmgr
Sponsored by: Absolight
- Convert to USES=libtool and bump dependent ports
- Add INSTALL_TARGET=install-strip
- Remove patches that renamed include directories and libraries so they
didn't conflict with early development versions of glib/gtk 2.0
Remove patches and hacks that were used to work around the previous
situation
This allows to stage more ports as a regular user
Differential Revision: https://reviews.freebsd.org/D703
Reviewed by and discussed with: bapt
With hat: portmgr
dependencies to the Requires field in pkgconfig files that should only be
needed with static linking and cause a lot of overlinking with shared
linking. They should be added to the Requires.private field instead, but
since this port doesn't install any static libraries they can just be
removed.
The flag was added because several ports that depend on this port failed to
link because of missing libraries when the linker enforced explicit
linking. The pkgconfig files in this port then provided the links.
These ports have all been fixed now.
PR: 192062
Exp-run by: antoine
Approved by: portmgr (antoine)
rubyforge.org shutdown on May 15, 2014. This commit accounts for that by doing
several things:
- Deprecate ruby that had only rubyforge.org as MASTER_SITES (and so are now
only fetchable via our cache)
- Deprecate ports that depend on those
- Update the WWW pkg-descr line that points to rubyforge.org for rubygem ports
(which are still fetchable from rubygems.org)
The next step will be to remove rubyforge.org from bsd.sites.mk, after these
deprecated ports are deleted.
Phabric: D591
With hat: ruby
Approved by: portmgr (because of committing to unstaged graphics/mingplot port)
(ports that are dependencies of other ports)
net-p2p/transmission-cli: add USES=libtool and remove PTHREAD_LIBS
sysutils/deltup: simplify patch by using MAKE_ARGS
x11-fm/rox-filer: convert to USES=shared-mime-info
x11-wm/emerald: remove PTHREAD_LIBS
PR: 192062
Please use USES=python instead of USE_PYTHON.
USE_PYTHON=yes becomes USES=python
USE_PYTHON=2.7+ becomes USES=python:2.7+
USE_PYTHON_BUILD=3.3 becomes USES=python:3.3,build
...
A new PYTHON_FEATURES variable was added, which enables certain features for a
port and replaces some knobs at the same time;
PYTHON_FEATURES=distutils replaces USE_PYDISTUTILS
PYTHON_FEATURES=autoplist replaces PYDISTUTILS_AUTOPLIST
PYTHON_FEATURES=py3kplist replaces PYTHON_PY3K_PLIST_HACK
PYTHON_FEATURES=noegginfo replaces PYDISTUTILS_NOEGGINFO
PYTHON_FEATURES=concurrent replaces PYTHON_CONCURRENT_INSTALL
PYTHON_FEATURES=pythonprefix replaces USE_PYTHON_PREFIX
Some knobs have been deprecated and are to be removed in the near future:
PYTHON_MASTER_SITES - use MASTER_SITE_PYTHON instead
PYTHON_PKGNAMESUFFIX - use PYTHON_PKGNAMEPREFIX instead
PYDISTUTILS_INSTALLNOSINGLE - deprecated without replacement
Some knobs have been removed completely:
PYTHON_MASTER_SITE_SUBDIR
PYTHON_DISTNAME
PYTHON_WRKSRC
Several variables specific to the Python framework are no longer passed to the
build environment to avoid polluting dependency builds.
PYTHON_VERSION is not passed to .MAKEFLAGS anymore
PYTHON_DEFAULT_VERSION,
PYTHON_DEFAULT_PORTVERSION and
PYTHONBASE are not passed to the make environment anymore
The conversion required a couple of ports to be updated to fit the changes and
new requirements. Those included "bsd.python.mk" directly or contained checks
in places, for which the USES framework would fail to provide correct values.
Python modules directly using the upstream Python package (such as py-tkinter
or py-sqlite3) were updated to avoid using the now unnecessary and remmoved
knobs from "bsd.python.mk".
Phabric: D399
exp-run: 167368 192357
PR: 167368 192357
Reviewed by: antoine, wg
Exp-run award: antoine
With hat: python@
Approved by: portmgr
minor COMMENT typos and surrounding whitespace fixes. A few Makefiles
where not included as they contain Latin-1 characters that break
the Phabricator workflow. Category X.
CR: D511
Approved by: portmgr (bapt)
There will not be any more updates to gtkada version 2. There are two
gtkada ports (the other is gtkada3) and portscout is seeing the distfile
for the other one and falsely reporting gtkada has an update.
in r363436 and remove the UPDATING entry because it did not guarantee
that all ports were updated nor that they were updated in the right order.
Also remove libgcrypt.la again.
PR: 192342
Approved by: portmgr (implicit, bump unstaged ports)
Changes:
* Major API changes to FXThreadPool: mostly, much more sane
implementation, and optional FXCompletion parameter passed to perform
wait on subset of tasks; see FXCompletion notes below.
* Added FXCompletion synchronization object. FXCompletion is now used in
FXTaskGroup, FXThreadPool, but can also be used in your own programs
whenever one thread needs to await the completion of multiple worker
threads.
* Fixed bug in FXJSON parser: properly stop parsing at offending
character.
* Byte order mark handling fix in FXJSON parser.
* Added toChars() API to FXVariant; it returns empty string unless variant
is of type string. This is very similar to asChars(), except that
toChars() is safe (always returns a non-NULL pointer).
* Renamed toPointer() to toPtr() in FXVariant for consistency.
* FXParallel implementation changes: don't kick off tasks via FXThreadPool
in ParallelFor if there's only one task. Also, split ParallelFor into a
number of pieces corresponding to the number of threads available in the
FXThreadPool, unless this number is passed explicitly.
* Ensured FXParallelForFunctor's are aligned in ParallelFor.
* Updated VC++ 2008 Visual Studio project files.
- Remove a patch that was applied upstream
and/or tabs before the =. This made doing regular expressions
on the ports tree really difficult.
Approved by: portmgr (not really, but touches unstaged ports)
The Qt Quick Controls module provides a set of controls that can be
used to build complete interfaces in Qt Quick.
Submitted by: Tobias Berner <tcberner@gmail.com> via the kde-freebsd mailing list
... 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
when an older version of a package is installed. This is the case when an
executable links with installed libraries and with uninstalled libraries
that link with other uninstalled libraries. For each of the directly
linked libraries the executable will have an rpath (/usr/local/lib for the
installed libraries and a path under WRKDIR for each of the uninstalled
libraries), but not for the indirect libraries. Both ld(1) and rtld(1)
search the rpath of the executable first before any rpath of libraries, so
the indirectly linked libraries will be found in /usr/local/lib if they are
installed instead of in WRKDIR.
With this commit executables will overlink with uninstalled indirect
libraries again so their location is added to the rpath of the executable.
This partially reverts r358784.
PR: 191611
Approved by: portmgr (bapt)
- Bump PORTREVISION on all ports that depend on security/gnutls and
adjust all ports that depend on security/gnutls3
- Update mail/anubis to version 4.2 which supports gnutls 3.x
- Update mail/libvmime to a development snapshot (recommended by upstream
developers)
PR: 191274
Exp-run by: antoine
Approved by: portmgr (antoine)
It applies to -imageformats in Qt4, but -gui in Qt5. Noted by antoine@. A
PORTREVISION bump was unavoidable to make sure people who build
qt5-gui-5.2.1_3 without the patch rebuild the port with it.
MFH: 2014Q3
Security: 904d78b8-0f7e-11e4-8b71-5453ed2e2b49
The GIF handler is part of qt{4,5}-imageformats, not qt{4,5}-gui. Big pointy
hat to me.
I've chosen not to force users to rebuild the -gui ports yet again with a
PORTREVISION bump since the code built in those ports is the same regardless
of whether the patch is applied or not.
Submitted by: RyoTa SimaMoto <liangtai.s16@gmail.com>
MFH: 2014Q3
Security: 904d78b8-0f7e-11e4-8b71-5453ed2e2b49
This new configure argument will list all required libraries in the
generated pkgconf files. Before any library indirectly pulled in, such
as libm, was not listed.
This fixes numerous regression in dports and it's more correct anyway.
phabric: D411
Approved by: gnome (kwm)
Changes:
* Added verbose option to reswrap.
* Updated BMP loader routines, some bullet-proofing against malicious
bitmap files.
* Changes in FXVariant: operator bool returns true for non-zero numerical
values, non-empty arrays or non-empty dictionaries. It only returns
false if the variant is FXVariant::null. This new interpretation strokes
much better with common usage patterns.
* Added asChars() API to FXVariant.
* FXPtrList now index with FXival.
* Print routines fxprintf() are now supporting NaN and Inf printouts. Also
fixed -0 printout.
* Change in FXThreadPool::wait() routine: now waits till all jobs are
finished.
* Added executeAndWait() routine to FXThreadPool and FXTaskGroup.
* Small change in FXParallel: ensure tasks are aligned in memory.
* Added FXEXEIcon and FXEXEImage. These should icons or bitmaps embedded
in Windows Executable files.
* Added FXCOLORREF2RGB and FXRGB2COLORREF macros for Windows based FOX
applications.
* Some complex math transcendentals added.
* Population-count inline functions added to fxendian.h. These use x86
builtins when possible.
* API fixes (bad parameter signatures) fixed in the list-widgets.
* CDECL attributes in some FXApp member functions (Windows Only).
