On quarta-feira, 12 de setembro de 2012 17.49.19, Sid Deb wrote: > Hi, > I'm porting a graphics app from qt4.6 to qt5.0.beta1 and I've run into a > situation where qmake refuses to name my output library correctly. I'm > working on OSX 10.6.8. > > Here are the relevant items from the .pro file: > CONFIG += staticlib debug_and_release > TEMPLATE = lib > TARGET_EXT = a > TARGET = libUIComponents-QT > > This results in a library called "libUIComponents-QT." and not > "libUIComponents-QT.a" as expected, which obviously causes problems when > trying to link against it. I've tried omitting the TARGET_EXT specifier, > but I get the same result. It seems that qmake adds the '.' but not the > extension, no matter what options I tried setting. Renaming the library > "fixes" the problem, but is obviously not a viable solution. > > This was giving the correct result under qt4 (without the TARGET_EXT > specifier). > > Is this a bug or has qt5 changed how this works, or is something wrong with > my setup here?
Static building is not working properly right now. In fact, it might not work
until Qt 5.1. YMMV.
Also, please use CONFIG += static instead of staticlib. The two should be
equivalent, but the one I recommend is the official.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Intel Sweden AB - Registration Number: 556189-6027
Knarrarnäsgatan 15, 164 40 Kista, Stockholm, Sweden
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
