Shadow Build Issue

[George H. Locktish]

I am noticing that the size of the DLLs for my release shadow build are
the same size as the DLLs for my 'minimal' shadow build.

I am testing two shadow builds: C:\Qt\4.3.2-tp1-minimal and
C:\Qt\4.3.2-tp1-release.

For C:\Qt\4.3.2-tp1-minimal, the configure command I ran was:
C:\Qt\4.3.2-tp1-minimal>C:\Qt\4.3.2-tp1\configure.exe -platform
win32-msvc2005 -xplatform wincewm50pocket-msvc2005 -qconfig minimal

For C:\Qt\4.3.2-tp1-release, the configure command I ran was:
C:\Qt\4.3.2-tp1-release>C:\Qt\4.3.2-tp1\configure.exe -platform
win32-msvc2005 -xplatform wincewm50pocket-msvc2005 -release

For both shadow builds, I then ran: setcepaths wincewm50pocket-msvc2005
and then nmake.

I am noticing that setcepaths outputs for both shadow builds:
"Could not find Qt directory... Compiling might not work
Environment Selection:Windows Mobile 5.0 Pocket PC SDK (ARMV4I)
     Windows Mobile 5.01 for Pocket PC selected, environment is set up
".  Perhaps the mention of not finding the Qt directory could be causing
problems?  However, I should mention that compilation does finish
without error.

- George

-----Original Message-----
From: Maurice Kalinowski [mailto:mkalinow at trolltech.com] 
Sent: Monday, October 29, 2007 4:09 AM
To: qtce-preview-feedback at trolltech.com
Subject: Re: Shadow Build Issue

George H. Locktish wrote:
> Thank you for your help.  Adding Perl to the path solved the issue I
was
> having.
>
> I have another question regarding shadow builds and the use of
qconfig.
> I am trying to do a shadow build with the qconfig-minimal
configuration,
> and what I am noticing is that it appears that all of the source code
is
> being compiled and linked into the DLLs (as if the qconfig is being
> ignored).  Is this what should be happening?
>
>   
It is true, that although you specify a minimal configuration, all files

are getting compiled. The difference is, that the configuration itself 
adds defines like QT_NO_LINEEDIT or QT_NO_<left-out-feature>. So the 
preprocessor removes all the code which is not supposed to get into the 
library. This is the easiest way to not manipulate the build system 
itself but being able to reduce actually compiled code.

As Thomas already suggested, you should recognize a significant size 
difference in the generated dlls.


Best Regards,

Maurice Kalinowski

To unsubscribe - send "unsubscribe" in the subject to
qtce-preview-feedback-request at trolltech.com