What I'm planning on doing for Phonon is modifying its mkspec file to
correctly do "LIBS *=..." no matter where Phonon is installed. That
seems like a nice robust solution.
goldendict does not seem to actually use Phonon. It does use qmake, but
does no do "CONFIG *= phonon" anywhere. No idea why the dependency is
there. It does not work with ffmpeg-devel, so it won't build for me. I
really wish the ffmpeg folks would decide where to put their headers &
not change them.
py*-pyqt4 doesn't actually use qmake to determine where phonon is
located; it does that for just the Qt* libraries / frameworks. It uses
some other magic to determine info for phonon. MacPorts sets CFLAGS to
include "-I${prefix}/include" and LDFLAGS to include "-L${prefix}/lib",
so it's no great surprise that phonon is being found.
qtscriptgenerator uses qmake to find phonon via the "CONFIG *= phonon"
command, and it fails because of the aforementioned reasons. - MLD
On Fri, Oct 30, 2015, at 11:18 AM, René J.V. Bertin wrote:
> Michael Dickens wrote:
>
> > is to make sure that either (1) "LIBS *= -L${prefix}/lib" is in place
>
> That seems like a small enough modification to qtscriptgenerator that if
> it works is much preferable to "hiding" phonon under libexec/qt4 ...
>
> > in ${prefix}/lib for phonon. What other projects use qmake and require
> > phonon? I'd like to test out this theory before pushing changes into
> > phonon. - MLD
>
> I was under the impression you knew better than I, but there's the list
> of all ports that declare a dependency on phonon in their Portfile
> (excluding qt4-mac and qt4-x11):
>
> %> fgrep -il qmake `fgrep -il phonon -R
> /opt/local/var/macports/sources/svn.macports.org/trunk/dports/
> --include=Portfile `
> /opt/local/var/macports/sources/svn.macports.org/trunk/dports/devel/qtscriptgenerator/Portfile
> /opt/local/var/macports/sources/svn.macports.org/trunk/dports/office/goldendict/Portfile
> /opt/local/var/macports/sources/svn.macports.org/trunk/dports/python/py-pyqt4/Portfile
>
>
> I checked again this morning: goldendict builds though I can see no trace
> of it actually depending on phonon in the build log nor in the resulting
> binary. I have py27-pyqt4+phonon and py34-pyqt4 installed, and as far as
> I can tell those are fully functional:
>
> %> otool -L
> /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/PyQt4/phonon.so
> /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/PyQt4/phonon.so:
> /opt/local/lib/libphonon.4.dylib (compatibility version 4.4.0,
> current version 4.8.3)
>
> /opt/local/libexec/qt4/Library/Frameworks/QtGui.framework/Versions/4/QtGui
> (compatibility version 4.8.0, current version 4.8.7)
>
> /opt/local/libexec/qt4/Library/Frameworks/QtCore.framework/Versions/4/QtCore
> (compatibility version 4.8.0, current version 4.8.7)
> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
> (compatibility version 45.0.0, current version 1265.21.0)
> /usr/lib/libc++.1.dylib (compatibility version 1.0.0, current
> version 120.0.0)
> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current
> version 1197.1.1)
>
> R
> _______________________________________________
> macports-dev mailing list
> macports-dev@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev
_______________________________________________
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
