14 Jul
2012
14 Jul
'12
4:20 a.m.
I notice that this problem is within Qt's builtin
libmng
instance. Does anyone even use the obsolete builtin libraries from Qt3, or
can I just blow this directory away and force linking against the
system's libmng instance?
Sounds like a reasonable idea, so I'll play the role of PITA --- I mean devil's
advocate. :-)
I have the following in my (T)Qt3 build scripts:
-qt-imgfmt-mng
That build option exists as a carryover from the days when Slackware still supported
KDE3/Qt3.
* What happens right now with automake 1.11 if I delete that build option? Will (T)Qt3
find the installed libmng headers and libraries? Or will (T)Qt3 build without any mng
support?
* When I use that build option, is my (T_Qt3 package using built-in mng support and
ignoring the installed libmng package?
* If you delete the built-in mng support from (T)Qt3, I presume I need to update my build
script and delete the -qt-imgfmt-mng build option?
* If you remove the built-in mng support, what happens when a distro does not support
libmng? (Unlikely, but what if?)
* What harm is there to retain the built-in mng support and just update the make/configure
files to be automake 1.12 compatible?
Darrell