The error you show below with qtscriptgenerator is because it does not
find phonon & thus there is no cpp code generated --> but the build
system does not know this for some reason & tries to build anyway.
Adding in QCA-like qmake code into the phonon mkspec file does the trick
for finding phonon via qmake. But, even with that addition
qtscriptgenerator still does not build (at least to 10.11 latest
everything). As I said, I'm looking into it. My read of the qmake /
phonon combo is that the only way using qmake to find phonon will work
is to make sure that either (1) "LIBS *= -L${prefix}/lib" is in place
before doing "CONFIG *= phonon"; or (2) including a project that sets
LIBS accordingly before adding in phonon. Otherwise, qmake will not look
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. - MLDOn Fri, Oct 30, 2015, at 05:33 AM, René J. V. Bertin wrote: > The difference here is that QCA provides hooks to install that way, or at > least > to indicate it where the various Qt components are installed. Phonon > doesn't > AFAIK (and port:phonon certainly doesn't seem to add them). > > I have been taking a look at qtscriptgenerator. It doesn't build indeed: > > :info:build make[2]: *** No rule to make target > `../../generated_cpp/com_trolltech_qt_gui/plugin.cpp', needed by > `plugin.o'. > Stop. > > but that failure is not related to phonon. I do see an issue finding > phonon, but > that appears to be more related to the fact that qtscriptgenerator looks > for a > phonon *framework* (as opposed to a .dylib). > BTW: I'll be trying the workaround described here: > https://code.google.com/p/qtscriptgenerator/issues/detail?id=39 > but I guess I should also check out why the build system looks for > headers in > ${prefix}/libexec/qt4/include which doesn't exist in my layout. > > Every other dependency of phonon I installed that uses qmake finds phonon > just > fine with libphonon in ${prefix}/lib and the Qt4 frameworks in > ${prefix}/libexec/qt4/Library/Frameworks and .dylib symlinks pointing to > those > framework binaries in ${prefix}/libexec/qt4/lib . And as far as I can > tell, that > is *not* because I also have libqt symlinks in ${prefix}/lib (my qt4-mac- > transitional subport). > > Coming back to qtscriptgenerator: I'm looking at how Ubuntu gets it to > build, > but the real question we have to ask for this port is whether it is worth > the > effort trying to resurrect abandonware. The only dependent I could find > is > amarok, and the application is built *without* qtscriptgenerator on > Linux. _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
