Qt Creator debugging static lib

mirswith

Ok, I seem to be narrowing it down. The problem seems to be that Qt Creator does not detect that it needs to relink my static lib. In the Compile Output it seems to think nothing has changed, which is true for everything except that it needs to relink the static lib. I do have the static lib set as a Dependency in the Projects settings, is this a bug in Qt Creator or is there a way around this? This is Qt Creator 2.0.0 on OSX, I am installing the latest on my windows box and will be testing that once Qt finishes building.

-=ben

goetz

It's more a qmake problem. Qt Creator just calls qmake and make to build everything.

giesbert

I think it's more a make than a qmake problem, isn't it?
If the pro is not changed, just make is called...

but is make called for both projects, or only for the projects ith changes?

so thejn it's a creator issue, as creator also calls make...

mirswith

Looking at the output it looks like just make is called, above that it says "Configuration unchanged, skipping qmake step.". Then in the make call it enters the shadow directory, then spits out "nothing to be done", leaves the directory and exist.

-=ben

goetz

[quote author="mirswith" date="1300225793"]Looking at the output it looks like just make is called, above that it says "Configuration unchanged, skipping qmake step.". Then in the make call it enters the shadow directory, then spits out "nothing to be done", leaves the directory and exist.

-=ben[/quote]

That's expected behavior :-)

mirswith

Shouldn't it link the static lib though since changes in the static lib occurred?

-=ben

goetz

only if you add to your .pro file:

@
PRE_TARGETDEPS = ../path/to/your/lib/liba.a
@

mirswith

AHHH.. THANK YOU! That is the bit of magic that I was missing. :D One would think that check marking the project as a Dependency in the Projects setting would accomplish this, but I am sure that would be WAY to easy! ;)

-=ben

goetz

The dependency in the project configuration basically influences the build order (that's one thing that Creator handles itself). Without the PRE_TARGETDEPS (or one of its friends), the lib is not in the dependency list of qmake (and subsequently of the Makefile) and so none of the tools cares if it changed.

tobias.hunger

mirswith: The inter-project dependencies have severe limitations. In fact we discussed to remove them again...

Please use your build system to link to sub-projects together. All of them provide means to add proper dependency tracking between (sub-)projects. We do not want to introduce a similar logic into creator itself: It would be prone to errors, hardly tested and will require the developer to understand a new set of dependency logics in addition to the one already required by the build system.

goetz

Tobias, but there will remain a configuration option to set the build order in Qt Creator?

tobias.hunger

Volker: We only talked about it and did not change any code.

goetz

Thanks Tobias for clarification. I like the dependency tool, but it would be sufficient for my use cases to set the build order. So, at least this should remain.

tobias.hunger

mirswith: You could have actually used Qt Creators wizard to add a library. That does add the required qmake magic:-) Another hidden gem in Qt Creator...

Open the .pro-file you want to add a library to. Right click anywhere in the editor and select "Add library" from the context menu to bring up a wizard to help with the task.

Yes, that is very well hidden, I only found this by accident right now. I'll open a issue with our bug tracker to make that way more visible.

dialingo

better use cmake for real projects.
cmake rebuilds all libs and dependent executables when a source file changes. In qmake you need to specify dependencies and I found this all very fragile. The trolls continue to use qmake because of requirements you probably do not have, for example running on esoteric platforms, continuing backwards compatibility, etc.
Give cmake a try!