Phil Thompson <[EMAIL PROTECTED]> wrote:

>> I can't find a way to tell configure.py (in PyQt4, latest snapshot) where
>> my specs file are located. In my Qt 4.1 installation (RPM by Suse), specs
>> files are installed into /usr/share/qt/mkspecs. PyQt4's configure detects
>> "qt_dir" as "/usr" (because qmake is located in /usr/bin/), so it tries
to
>> look for spec files in /usr/mkspecs.
>>
>> I tried exporting a QMAKESPEC env with an absolute path. This works only
in
>> half: configure.py uses os.join.path and correctly finds and parses the
>> spec file, but the installed sipconfig.py knows nothing of QMAKESPEC, so
>> when it comes to generating the Makefile adding an include directory for
>> the qplatformdefs.h, it doesn't look in the environment and simply uses
>> qt_dir + "mkspecs" (which ends up being /usr/mkspecs).
>>
>> I'm missing some pieces of information. How does qmake locate its spec
>> files? Can't PyQt4 use the same algorithm so to workaround these
problems?
>
> Does Suse set the QMAKEPATH environment variable?

No, it's not set in the env, and I can't see any script in the qt RPM.

> Once you build PyQt4, what the output of running...
>
> print QLibraryInfo.location(QLibraryInfo.DataPath)


/usr/share/qt, which is in fact the correct base path for specs files.
-- 
Giovanni Bajo

_______________________________________________
PyKDE mailing list    PyKDE@mats.imk.fraunhofer.de
http://mats.imk.fraunhofer.de/mailman/listinfo/pykde

Reply via email to