[PyQt] QScintilla2 for Qt4/Qt45 Co-installability

[Scott Kitterman]

On Sunday, March 09, 2014 17:26:13 Phil Thompson wrote:
> On 09-03-2014 4:41 pm, Scott Kitterman wrote:
> > Sigh. Phone auto correct. ..
> > 
> >  Debian/Ubuntu
> >  
> >  Scott K
> > 
> > On March 9, 2014 9:48:30 AM EDT, Scott Kitterman
> > 
> > <debian at kitterman.com> wrote:
> >> Ive been investigating extending the Deviant/Unintuitive packages
> >> for QScintilla2 to also build for Qt5.
> >> 
> >> Both the build for Qt4 and Qt5 produce identically named
> >> libqscintilla2 so files. I can easily mark the packages as
> >> conflicting so they cant be installed at the same time, but that
> >> seems less than ideal.
> >> 
> >> Do you have any suggestions about how to proceed on making the
> >> libraries co-installable?
> 
> The current snapshot installs a qscintilla2.prf file so that is now the
> recommended way of adding QScintilla to a .pro file. That then makes it
> more acceptable to call the library different names when compiled
> against different versions of Qt.

I think I have the library piece of it figured out now.  I am stuck on 
configuring the Python bindings to build with Qt5.  Here's what I have so far 
for the Python configure command when I'm trying to build with Qt5 (QSciQt5 is 
the directory where the Qt5 build of the library is done):

python$* ../configure.py -n ../../QSciQt5/ -o ../../QSciQt5 \
   --sip-incdir=/usr/include/python$* -c --pyqt=PyQt5 --qmake=/usr/bin/qmake \
   --destdir=/usr/lib/python$*/dist-packages/PyQt5;

This configures, but not fully for Qt5.  In the generated Qsci.pro file, there 
is:

api.path = /usr/share/qt4/api/python

Also the Qt include path when compiling the extenstion is still Qt4 (and 
nothing in the .pro says it should be different.  It looks like setting --
pyqt=PyQt5 only affects there the files go by default, not what Qt version is 
actually used during the build.  

How do I pass options to qmake and how do I set api.path?

Scott K