[KDE/Mac] kde-mac Digest, Vol 76, Issue 7

[René J.V. Bertin]

On Monday March 28 2016 10:57:17 Jonathan Schultz wrote:


> follow perfectly. I guess I need to check out the Macport documentation
> in a bit more detail.

That'd never hurt ;)

> > file:///opt/local/site-ports
> > rsync://rsync.macports.org/release/tarballs/ports.tar [default]

That ought to be fine. I suppose you installed the MacPorts release version (2.3.4), not a development version from SVN?

Maybe it might help if you executed the portindex command once more (`(cd /opt/local/site-ports ; portindex)`).

Either way, I pushed a small update to port:qt5-kde-devel yesterday, causing it to raise an error if it doesn't detect the correct PortGroup settings.

Here's what I see when I do `port -d qt5-kde-devel` : 

port -d info qt5-kde-devel
DEBUG: Changing to port directory: /opt/local/site-ports/aqua/qt5-kde-devel
DEBUG: OS darwin/13.4.0 (Mac OS X 10.9) arch i386
DEBUG: Qt5 is provided by port:qt5-kde
DEBUG: Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/variant_descriptions.conf
DEBUG: Sourcing PortGroup muniversal 1.0 from /opt/local/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/group/muniversal-1.0.tcl
DEBUG: Sourcing PortGroup compiler_blacklist_versions 1.0 from /opt/local/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/group/compiler_blacklist_versions-1.0.tcl
DEBUG: Sourcing PortGroup macports_clang_selection 1.0 from /opt/local/site-ports/_resources/port1.0/group/macports_clang_selection-1.0.tcl
DEBUG: compiler clang 600.0.57 not blacklisted because it doesn't match {clang < 500}
DEBUG: whitelisting macports-clang-3.7 because it exists, and skipping the remaining versions
DEBUG: compiler.blacklist=macports-llvm-gcc-4.2 llvm-gcc-4.2 gcc-4.2 apple-gcc-4.2 gcc-4.0
DEBUG: Sourcing PortGroup locale_select 1.0 from /opt/local/site-ports/_resources/port1.0/group/locale_select-1.0.tcl
DEBUG: Sourcing PortGroup qt5-kde 1.0 from /opt/local/site-ports/_resources/port1.0/group/qt5-kde-1.0.tcl
DEBUG: Sourcing PortGroup qt5 1.0 from /opt/local/site-ports/_resources/port1.0/group/qt5-1.0.tcl
DEBUG: Sourcing PortGroup select 1.0 from /opt/local/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/group/select-1.0.tcl
DEBUG: Sourcing PortGroup xcodeversion 1.0 from /opt/local/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/group/xcodeversion-1.0.tcl
DEBUG: Using SDK macosx10.9 : /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk
DEBUG: Re-registering default for configure.dir
DEBUG: Re-registering default for build.dir
DEBUG: Re-registering default for configure.cmd
DEBUG: universal variant already exists, so not adding the default one
DEBUG: Executing variant qt5kde provides qt5kde
DEBUG: Executing variant langselect provides langselect
DEBUG: Executing variant harfbuzz provides harfbuzz
DEBUG: Running callback portconfigure::add_automatic_compiler_dependencies
DEBUG: Finished running callback portconfigure::add_automatic_compiler_dependencies
DEBUG: Running callback portbuild::add_automatic_buildsystem_dependencies
DEBUG: Finished running callback portbuild::add_automatic_buildsystem_dependencies
qt5-kde-devel @5.6.0 (aqua)
Sub-ports:            qt5-kde-devel-x11, qt5-kde-devel-zz-docs, qt5-kde-devel-qtwebengine, qt5-kde-devel-sqlite3-plugin,

The line "DEBUG: Sourcing PortGroup qt5-kde 1.0 from /opt/local/site-ports/_resources/port1.0/group/qt5-kde-1.0.tcl" shows that qt5-kde-1.0.tcl *was* read from the custom repo (the statement is printed after the facts).

Note also that my log reads "DEBUG: Qt5 is provided by port:qt5-kde" ; in your case you should be seeing "DEBUG: Qt5 will be provided by port:qt5-kde, by request" instead.

Which brings me to another potential explanation: you already have/had port:qt5 or a number of its subports installed. That's an error situation I didn't yet handle; the update I pushed does that too.

Please let me know what difference this makes for you.

> I see what you mean, but am not clear which port directories are the
> ones I want.
> 
> If I understand correctly the whole purpose of doing this is to build
> qt/kde for x11 in order to test whether this affects the ability of
> okular/poppler to render PDFs.

I'd add that you'll be getting a Qt5 that's patched to ensures that KF5 applications expect (and find) their shared resources in XDG-compliant locations like /opt/local/share, ~/.local/share, ~/.conf etc.

I would advise using my cmake PortGroup file too as it contains a number of modifications that are optional but IMHO convenient for (port) developers.

There are a number of ports you'll probably need from site-ports/devel ; the qca ones, probably the dbus ones, maybe grantlee; you'll probably recognise them by name and then you can check quite easily if they contain a Qt5 subport or depend on Qt5.

> be trying. Would it be worth testing under El Capitan for example?

I would appreciate testers on 10.11 to have a better idea what works or breaks on that version, but I'd guess you have different priorities.
OTOH, if you really aim to develop your application for OS X too, it'll be up to you to decide whether you want to support older OS versions, or only the current version and beyond. In the latter case you'd be better off starting with 10.11 immediately.

> just prefer Mavericks because it does a better job of handling
> non-standard screen dimensions

Oh? That surprises me (though a lot less than it would have a few years ago). How so?

> 
> Another thing I could do is revert to a virgin Mavericks installation
> (one advantage of virtual machines is how easy this is) 

It would have been just as easy on "real silicon" if Apple had made good on their idea of using ZFS ;)

Cheers,
René