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
=Version 1.3.37=
2017-12-25 David Freese <w1hkj@bellsouth.net>
318525f: TS990 / xmlrpc server mods
6ae502c: IC7200 filter width
ab52166: Rotate log
c028b78: Get PTT
72540db: Comm timeout
77df05d: IC7200/7300 notch
1591335: TS990 changes
ab76f02: Remove xmlrpc client
d4eba84: UI service paradigm
8e3ed6f: IC718
d7e240d: IC7200
7b24e97: Extras drop down panel
96fc5cd: start-stop
dbdd895: OS X race conditions
b1c196e: PTT xmlrpc get
5c2d2a0: Value by VFO
7f2cd8b: UI wide power button
a16b2c9: Comp Level
=Version 1.3.36=
fc88084: IC 9100
cc62a5a: K2
2017-10-18 steve AG7GN <steve.magnuson@gmail.com>
ce45cb2: IC7100
2017-10-14 David Freese <w1hkj@bellsouth.net>
6236378: KH6TY
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
The CAN code might not be entirely working on FreeBSD (I have not checked), but
there is no reason not to build it and have it be tested more widely.
Reviewed by: tcberner, adridg
Differential Revision: https://reviews.freebsd.org/D13107
invoked FdTOx (convert floating point to 64-bit integer) instruction
with odd register number as the second argument, while apparently[*]
an even number is required:
fdtox %f10, %f15
It caused ``Illegal operands'' error when compiling `draw_symbols.c':
{standard input}: Assembler messages:
{standard input}:2686: Error: Illegal operands
{standard input}:2695: Error: Illegal operands
{standard input}:2835: Error: Illegal operands
{standard input}:2844: Error: Illegal operands
{standard input}:2854: Error: Illegal operands
{standard input}:2864: Error: Illegal operands
Fix the build by forcing -O0 when compiling this file on sparc64.
- Remove OPTCFLAGS option which enabled "optimized" CFLAGS ``-O2 -pipe'':
these are our default CFLAGS for a long time
[*] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56890
- Remove FLAVOR from py-docutils dependency in comms/uhd, in this case
it needs the rst2html command, not the docutils module
- Mark some ports as not compatible with python3
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
Availability release of WSJT-X Version 1.8.0.
Changes since "Release Candidate 3" (wsjtx-1.8.0-rc3) are very minor; they are
described in the Release Notes posted here:
http://physics.princeton.edu/pulsar/k1jt/Release_Notes_1.8.0.txt
Installation packages for Windows, Linux, Macintosh, and Raspian Jessie
have been posted on the WSJT web site here:
http://physics.princeton.edu/pulsar/k1jt/wsjtx.html
You can also download the packages from our SourceForge site:
https://sourceforge.net/projects/wsjt/files/wsjtx-1.8.0-rc3/
(It may take a short time for the SourceForge site to be updated.)
If you are upgrading from -rc1, you will need to do a one-time reset of
the default list of suggested operating frequencies. Go to
*File->Settings->Frequencies*, right click on the table and select *Reset*.
We hope you will enjoy using WSJT-X Version 1.8.0.
-- 73, Joe, K1JT, for the WSJT Development Group
removed, I did miss that one. (It's directly used as a filename)
The other places are do not cares.
- It makes no sense to remove gets() without removing potentially
just as bad scanf() calls and it's bad practice to use scanf anyway
I'm paranoid with implementations of fgets() (Non FreeBSD to be clear)
hence the use of -1 in the length argument of fgets().
- I'll see if upstream is willing to accept these diffs.
Submitted by: Max Khon <fjoe@freebsd.org>
Reported by: Max Khon <fjoe@freebsd.org>
Simple TTY terminal application which features a straightforward
commandline interface to easily connect to TTY devices for basic
input/output.
WWW: https://tio.github.io
PR: 222719
Submitted by: Dmitri Goutnik <dg@syrec.org>
