summaryrefslogtreecommitdiffstats
path: root/qmake/generators/makefile.cpp
diff options
context:
space:
mode:
authorThiago Macieira <thiago.macieira@nokia.com>2008-10-20 07:59:51 (GMT)
committerThiago Macieira <thiago.macieira@nokia.com>2009-08-17 10:48:24 (GMT)
commit5bc8c27e9406fd55693e3a3963030c6d9a89b08a (patch)
tree94beac30107d3b09550094a0e00e6c26b01eb5d1 /qmake/generators/makefile.cpp
parent8096d2bbbb1f4becaaefe2219560f8dd558235de (diff)
downloadQt-5bc8c27e9406fd55693e3a3963030c6d9a89b08a.zip
Qt-5bc8c27e9406fd55693e3a3963030c6d9a89b08a.tar.gz
Qt-5bc8c27e9406fd55693e3a3963030c6d9a89b08a.tar.bz2
Add LIBS_PRIVATE to qmake.
The difference between LIBS and LIBS_PRIVATE is that private libraries are those that are not part of the public interface of a library. For example, if you're writing a Qt application and link to QtGui, you definitely need the development files for QtCore, but not necessarily for Glib and GThread, or maybe even X11. The private libraries are necessary only in static builds, so the information should still be published in .prl and pkg-config files. Reviewed-By: Marius Storm-Olsen
Diffstat (limited to 'qmake/generators/makefile.cpp')
-rw-r--r--qmake/generators/makefile.cpp2
1 files changed, 2 insertions, 0 deletions
diff --git a/qmake/generators/makefile.cpp b/qmake/generators/makefile.cpp
index 9580101..bf0e6df 100644
--- a/qmake/generators/makefile.cpp
+++ b/qmake/generators/makefile.cpp
@@ -967,6 +967,8 @@ MakefileGenerator::writePrlFile(QTextStream &t)
libs = project->values("QMAKE_INTERNAL_PRL_LIBS");
else
libs << "QMAKE_LIBS"; //obvious one
+ if(project->isActiveConfig("staticlib"))
+ libs << "QMAKE_LIBS_PRIVATE";
t << "QMAKE_PRL_LIBS = ";
for(QStringList::Iterator it = libs.begin(); it != libs.end(); ++it)
t << project->values((*it)).join(" ") << " ";