README.qtcopy: -no-stl or no -no-stl?

Ingo Klöcker kloecker at
Mon Jan 19 22:19:01 GMT 2004

On Monday 19 January 2004 14:20, Navindra Umanee wrote:
> Hi,
> The first ./configure example in README.qt-copy is:
> ./configure -system-zlib -qt-gif -system-libpng -system-libjpeg \
>   -plugin-imgfmt-mng -thread -no-stl -fast
> but the recommended ./configure line for GCC is:
> ./configure -system-zlib -qt-gif -system-libpng -system-libjpeg \
>   -plugin-imgfmt-mng -thread -no-exceptions -debug -fast
> Why does the first one include -no-stl but not the second one?  There
> isn't an explanation in the file as to which one is most desireable,
> speed and efficiency wise.
> ./configure --help says:
>     -no-stl ............... Do not compile STL support.
> Why would Qt need STL support anyway?

Because else you can't use algorithms and methods that STL provides. 
There are quite a few nice things in STL which don't have Qt 
counterparts for the Qt container classes (e.g. QValueList, etc.). But 
since many of the Qt container classes are STL compatible it's possible 
to use the STL algorithms with the Qt container classes. But only if 
you enabled STL support.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: signature
URL: <>

More information about the kde-core-devel mailing list