[Qt-interest] Library Dependencies on Solaris

[Jake Colman]

>>>>> "TM" == Thiago Macieira <thiago at kde.org> writes:

   TM> On Tuesday 7. September 2010 23.29.15 Jake Colman wrote:

   TM> Ah, right. I didn't notice that it's only from QWS (Embedded
   TM> Linux), not the X11 port.
   >> 
   TM> For X11, Qt uses freetype if you have it.
   >> 
   >> But why does it insist on using freetype from /usr/sfw even if I
   >> configure with "-no-fontconfig -no-freetype qt-freetype"?  That sounds
   >> like a bug, not a feature.

   TM> Like I said, -no-freetype and -qt-freetype are only QWS options. Therefore, 
   TM> they don't apply to you.

   TM> -no-fontconfig does apply to you, but it's pointless to try to
   TM> build like that.  You want fontconfig.

I need to build Qt for use on a stock Solaris system and a stock Solaris
system does not have freetype.  Since fontconfig is also not included
with stock Solaris, configure does not try to activate fontconfig for
me.  The only thing it does try and use is freetype because qmake.conf
looks for /usr/sfw.  Should I assume that fontconfig and freetype are
prerequisites for successful use of Qt?

   TM> And, like I said, we do not test those options.

But Solaris 10 with Studio 12 is a supported configuration for Qt.  So
am I being unreasonable?

   TM> Which proves it's an indirect dependency. There's nothing in
   TM> QtGui that links to libiconv, but there is in QtCore. So it must
   TM> be coming from a library that QtGui does link to.
   >> 
   >> I would have thought so too but here is the ldd from libQtCore:
   >> 
   >> libpthread.so.1 =>	 /lib/libpthread.so.1
   >> librt.so.1 =>	 /lib/librt.so.1
   >> libm.so.2 =>	 /lib/libm.so.2
   >> libdl.so.1 =>	 /lib/libdl.so.1
   >> libaio.so.1 =>	 /lib/libaio.so.1
   >> libmd.so.1 =>	 /lib/libmd.so.1
   >> libc.so.1 =>	 /lib/libc.so.1
   >> /platform/SUNW,Sun-Fire-V440/lib/libmd_psr.so.1
   >> /platform/SUNW,Sun-Fire-V440/lib/libc_psr.so.1
   >> 
   >> It cannot be that one of these files in /lib or /platform is pulling in
   >> libiconv!

   TM> No. It's one of those in libQtGui that aren't in
   TM> libQtCore. Probably glib.

But what is pulling in glib?  I'm not asking for it!

Bottom line: I will be installing my app onto systems that will have a
stock, hardened Solaris installation.  I can only build Qt with
dependencies on those libraries that I know will be available on that
kind of bare-bones installation?  Is that possible?  If not, what are
the minimum requirements?

As a point of reference, this is my ./configure command-line:

./configure -prefix /HOME1/colman/qt-4.6.3-new -debug -commercial
-shared -fast -no-accessibility -qt3support -no-scripttools
-no-xmlpatterns -no-multimedia -no-audio-backend -no-phonon
-no-phonon-backend -no-svg -no-webkit -no-javascript-jit -no-script
-qt-zlib -qt-gif -qt-libtiff -qt-libpng -qt-libmng -qt-libjpeg
-no-openssl -no-cups -no-dbus -make libs -make tools -nomake examples
-nomake demos -nomake docs -nomake translations -no-glib -no-fontconfig
-no-openvg -no-gtkstyle -no-iconv -no-xrender -no-opengl -qt-freetype 

Thanks for your on-going help.

...Jake


-- 
Jake Colman | Director, Software Development
Principia Partners LLC
101 West Elm Street | Conshohocken | PA 19428 | +1 (610) 755 9770
t: +1 (610) 755 9786 | c: +1 (610) 348 2788 | f: +1 (201) 221 8929
e: colman at ppllc.com | w: www.principiapartners.com
Credit technology innovation awards winner 2008 and 2009