I'm not sure if this is a Qt Creator question, or just a plain qmake question 
but here goes:

I'm having a dependency problem with qmake and/or Qt Creator.

I've got an application "foo" that depends on my library "bar".  I have two 
.pro files "foo.pro" and "bar.pro" respectively.  Currently I'm building the 
"bar" library statically, so in "bar.pro" I have:

  CONFIG += staticlib

And in "foo.pro" I have:

  INCLUDEPATH += ../bar
  LIBS += ../bar.a

The problem is that when building "foo" under Qt Creator, it doesn't seem to 
realize that there is any dependency on "bar.a".  So when I find a bug or add a 
new feature to "bar" and recompile the library, the "foo" project doesn't 
realize that "bar.a" is newer than the last time I built "foo", so clicking 
Build just returns immediately without re-linking to the newly updated "bar.a".

I'm not sure if it matters or not, but they way I've been doing it currently is 
that I have two instances of Qt Creator running, one that is working with 
"bar.pro", one that is working with "foo.pro".  So when I find something that 
needs to change in the "bar" library, I use that instance of Qt Creator, and 
click the build button.  My new "bar.a" builds as expected.  Then I switch 
windows to the instance of Qt Creator that has loaded "foo.pro", press Build 
and all I get is the "Nothing to be done for 'first'" message.

So what am I doing wrong?
Sean
_______________________________________________
Qt-creator mailing list
[email protected]
http://lists.qt.nokia.com/mailman/listinfo/qt-creator

Reply via email to