Explain Qt library sizes, please

[wysota]

Use the following construct:
"CONFIG(debug, debug|release) { ... }" for debug mode compilation and "CONFIG(release, debug|release){...}" for release mode compilation. Then when the compilation is in debug and release proper scopes will get activated.

[bnilsson]

Thanks, this seems to work on win32-mcvc2008.
However this does not seems to work on MacX, only GeneratedFiles/Debug is generated.
But this is not serious for me at the moment.

And still, the Win32 app wants VC90.DebugCRT to run on the other PC.
I have removed my linked-in library and put the source directly in the project, so there cannot be any debug/release mixup, if there ever was.
Any suggestions where I should look?
I have used the dependency walker and I have not found anything debug-related so far.

[wysota]

Thanks, this seems to work on win32-mcvc2008.
However this does not seems to work on MacX, only GeneratedFiles/Debug is generated.
But this is not serious for me at the moment.

It should work. Provided that debug_and_release is supported on Mac.

I have used the dependency walker and I have not found anything debug-related so far.

Did it show a dependency on the debug version of the C runtime? What exactly depended on it?

[bnilsson]

I tried again on another development PC, installed Qt like this in the VC2008 command window:

configure -static -release - no-webkit
nmake sub-src

So no static debug libraries were built.

Now I could build the release app and it finally worked at the target PC.
So far so good.

However, I failed to make the (same) VC project build a debug shared app, since the settings in the VC debug configuration was not properly set for this.
I had previously built Qt shared in the development PC so the shared libs were there also.
Is it possible to have a single VC project with both shared(debug) and static(release) builds?

And if it is, is it possible to have this generated by a single .pro file by qmake (with TARGET vcapp)?


In general, how does one usually set up the Qt/vc environment for shared debugging and static deployment?

[bnilsson]

As this discussion drifted a bit since the original question, I move the shared debug / static release build to another thread.