Re: glibc warnings

Justin Karneges <[email protected]>
Newsgroups gmane.comp.autopackage.devel
Message-ID <[email protected]>
On Wednesday 28 November 2007 9:21 am, Eugene Zolenko wrote:
> >Qt4 should still be shipped/statically linked as it's still uncommon.
> >This will change when KDE 4 comes out, but for now, I think shipping
> >it is the best approach.
>
> Also, I think Qt isn't very backwards binary compatible. So if you build
> with 4.2.2 and on target system user has 4.2.0 there might be problems.
> That is almost anecdotal fact though, as I didn't investigate much. So
> shipping them and installing private copy might be the way to go (that's
> what we do).

Qt follows the simple interface compatibility scheme of major.minor.patch.  
4.2.2 would indeed be backwards compatible with 4.2.0.  Similarly, 4.2.0 
would be forwards compatible with 4.2.2.  The interface version of both would 
be 4.2.  Qt has always made these interface guarantees.  Whether they live up 
to their promise is another matter.

> >When I was packaging a Qt 4 app, I ended up building a custom Qt with
> >apgcc. It's not that hard to do--edit the linux-g++ mkspec from the
> >source tarball and change all the "g++"s to "apg++", and all the
> >"gcc"s to "apgcc"s. I'm pretty sure that using an apbuild compiled
> >version of Qt got rid of the errors for me.
>
> That's what I run to build Qt with apbuild on FC6 (this is commercial
> package though, so you might have to change something). I don't remember
> if I had glibs warnings, but the binaries build on FC6 work fine on FC3.
>
> #!/bin/bash
> ./configure -nomake examples -no-qt3support -qt-gif -no-tablet
> find . -name Makefile -execdir sed -i "{s/^CC.*= gcc$/CC = apgcc/;
> s/^CXX.*= g++$/CXX = apg++/; s/^LINK.*= g++$/LINK = apg++/}" '{}' ';'

Ready for mine? :)

Copy mkspecs/common/g++.conf to mkspecs/common/apg++.conf, with the latter 
file containing the gcc/apgcc and g++/apg++ substitutions.  Copy 
mkspecs/linux-g++ (it's a directory) to mkspecs/linux-apg++.  Change 
mkspecs/linux-apg++/qmake.conf to "include" apg++.conf rather than g++.conf.

./configure -platform linux-apg++ (among other options)

Probably overkill for personal use. :)  However, if I have good luck with 
autopackage and Qt, I might suggest to Trolltech that they add a linux-apg++ 
mkspec just like this so you can build it out of the box.

-Justin

---------------------------------------------------------------------
To unsubscribe, e-mail: autopackage-dev-unsubscribe-OfajU3CKLf1/[email protected]
For additional commands, e-mail: autopackage-dev-help-OfajU3CKLf1/[email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.