>>>>> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:

| It appears that KDE autoconf code always uses -nounload when
| supports it. This flag appears to avoid unloading qt designer
| plugins | when exiting uic.

Lars> So a way to avoid bugs in uic plugins?
I do not know really. The flag is undocumented, but it appears in
--help and in a few archived mailing list.

So the best argument I have is really "KDE does it". :)

JMarc
FWIW, I found two occurrences of nounload in the qt-x11-free-3.3.5 source (ftp://ftp.trolltech.com/qt/source/qt-x11-free-3.3.5.tar.bz2)

In ./qt-x11-free-3.3.5/tools/designer/uic/main.cpp

// see ### in widgetdatabase.cpp
extern bool dbnounload;
...
} else if ( opt == "nounload" ) {
       dbnounload = TRUE;

and

"Options:\n"
        "\t-o file         Write output to file rather than stdout\n"
"\t-pch file Add #include \"file\" as the first statement in implementation\n"
        "\t-nofwd          Omit forward declarations of custom classes\n"
        "\t-nounload       Don't unload plugins after processing\n"
        "\t-tr func        Use func() instead of tr() for i18n\n"
        "\t-L path         Additional plugin search path\n"
        "\t-version        Display version of uic\n"
        "\t-help           Display this information\n"



And in /qt-x11-free-3.3.5/tools/designer/shared/widgetdatabase.cpp

// ### Qt 3.1: make these publically accessible via QWidgetDatabase API
#if defined(UIC)
bool dbnounload = FALSE;
QStringList *dbpaths = 0;
#else
extern QString *qwf_plugin_dir;
#endif


Anand


Reply via email to