Darren J Moffat wrote:
> Does it really make sense to have all of QT hidden away in /usr/qt4 ? I
> was expecting at least some things like include files or libraries to be
> under /usr/include and /usr/lib respectively.
>
> My concern is how are autoconf, and the like, scripts that need to find
> QT libraries and includes going to find it ? Are we expecting that
> everyone will know to do something like this:
>
> ./configure --with-qt-include=/usr/qt4/4.4.1/include \
> --with-qt-libs=/usr/qt4/4.4.1/lib/
>
> Is there no pkg-config .pc file for QT that can be placed in
> /usr/lib/pkgconfig to help with this ?
PKG_CONFIG_PATH can be set to /usr/qt4/4.4.1/lib/pkgconfig:${PKG_CONFIG_PATH}.
Or, one can say --with-qt-include=${QTDIR}/include --with-qt-libs=${QTDIR}/lib
> Is this the common layout on Linux based distributions where GNOME is
> considered the primary desktop rather than KDE ? What is they layout
> when KDE is the primary desktop ?
SUSE organizes as /usr/lib/qt3 /usr/lib/qt4, etc
The question is: what happens when we want to include a newer version of QT (QT
4.5.0 is already out), which comes with newer and likeable features ? The two
versions have to be able to coexist someohow, without creating conflicts.
>
>> This Fasttrack proposes an overall "Uncommitted" Interface
>> Stability Classification for QT4. Considering the ABI Micro
>> Release Stability guarantee provided by Trolltech ASA, a
>> "Committed" Interface Stability Classification would have been
>> appropriate. However, QT4's dependency on
>> External/Evolving/Uncommitted Interfaces makes an overall
>> "Committed" Interface Classification inaproppriate.
>
> That doesn't follow. Just because you have lower classified
> dependencies doesn't mean you can't be higher than them. That is the
> definition of what we do in ARC. Everything is built on something of a
> lower classification at some level. So if this really could be
> Committed other than for the incorrect assumption on the dependencies it
> should be Committed.
It can't be Committed because [1] it doesn't really implement any known
Industry
standard, and [2] we don't control QT's Interface Stability level.
--
Stefan Teleman
Sun Microsystems, Inc.
Stefan.Teleman at Sun.COM
