Qt-interest Archive, May 2008
Problem with assistant
Message 1 in thread
I compiled qt 4.4 on windows and it was compiled ok, but assistant does not
have any documentation. I tried add qch files from QTDIR\doc\qch folder but
it says it is invalid assistant files. What did i wrong ?
--
[ signature omitted ]
Message 2 in thread
"nntp.trolltech.com" <eskon2005@xxxxxxx> сообщил/сообщила в новостях
следующее: news:g0kbcn$95u$1@xxxxxxxxxxxxxxxx
>I compiled qt 4.4 on windows and it was compiled ok, but assistant does not
>have any documentation. I tried add qch files from QTDIR\doc\qch folder but
>it says it is invalid assistant files. What did i wrong ?
>
> --
> Sergey Kondryukov
> sergey@xxxxxxxxxxx
>
I'm not sure it's related but i changed mkspec to compile qt as static
library. Could it corrupt assistant or doc build process ?
--
[ signature omitted ]
Message 3 in thread
nntp.trolltech.com wrote:
> "nntp.trolltech.com" <eskon2005@xxxxxxx> ÑÐÐÐÑÐÐ/ÑÐÐÐÑÐÐÐ Ð ÐÐÐÐÑÑÑÑ
> ÑÐÐÐÑÑÑÐÐ: news:g0kbcn$95u$1@xxxxxxxxxxxxxxxx
>> I compiled qt 4.4 on windows and it was compiled ok, but assistant
>> does not have any documentation. I tried add qch files from
>> QTDIR\doc\qch folder but it says it is invalid assistant files. What
>> did i wrong ?
>
> I'm not sure it's related but i changed mkspec to compile qt as static
> library. Could it corrupt assistant or doc build process ?
>
Did you recompile assistant (run "nmake sub-tools")? And do you get any
debugging output from assistant (dbgview)?
Assistant relies on the qsqlite plugin, maybe loading it fails. The qch
files are prebuilt, and there should be no need to recreate them.
Regards
Kai KÃhne
--
[ signature omitted ]
Message 4 in thread
>>> I compiled qt 4.4 on windows and it was compiled ok, but assistant does
>>> not have any documentation. I tried add qch files from QTDIR\doc\qch
>>> folder but it says it is invalid assistant files. What did i wrong ?
>>
>> I'm not sure it's related but i changed mkspec to compile qt as static
>> library. Could it corrupt assistant or doc build process ?
>>
> Did you recompile assistant (run "nmake sub-tools")? And do you get any
> debugging output from assistant (dbgview)?
>
> Assistant relies on the qsqlite plugin, maybe loading it fails. The qch
> files are prebuilt, and there should be no need to recreate them.
>
> Regards
Yes, i suspect that static compilation disabled plugins. BTW, does it
require
SQLite installed on system ?
--
[ signature omitted ]
Message 5 in thread
Sergey Kondryukov wrote:
>
> Yes, i suspect that static compilation disabled plugins. BTW, does it
> require
> SQLite installed on system ?
Unless you specified "-system-sqlite" while running configure, no.
Did you include the configure option "-qt-sql-sqlite"?
Kai Koehne
--
[ signature omitted ]
Message 6 in thread
Hi,
> I'm not sure it's related but i changed mkspec to compile qt as static
> library. Could it corrupt assistant or doc build process ?
Did you modify the mkspecs files? This shouldn't be needed to compile Qt as a
static library:
http://doc.trolltech.com/4.4/install-win.html
--
[ signature omitted ]
Message 7 in thread
"Dimitri" <dimitri@xxxxxxxxxxxxx> сообщил/сообщила в новостях следующее:
news:g0r8t2$m0j$1@xxxxxxxxxxxxxxxx
> Hi,
>
>> I'm not sure it's related but i changed mkspec to compile qt as static
>> library. Could it corrupt assistant or doc build process ?
>
> Did you modify the mkspecs files? This shouldn't be needed to compile Qt
> as a static library:
> http://doc.trolltech.com/4.4/install-win.html
>
> --
> Dimitri
>
May be i missed something but i don't see in your link any help concerning
static compilation.
I mean real static compilation which require MT options in VC compiler, not
just using "static"
in configure. Changing mkspecs worked nice in all previous versions.
--
[ signature omitted ]
Message 8 in thread
Hi,
> May be i missed something but i don't see in your link any help
> concerning static compilation.
Running:
configure -help
should display the "-static" option, which builds static Qt libraries.
> I mean real static compilation which require MT options in VC compiler,
> not just using "static"
> in configure. Changing mkspecs worked nice in all previous versions.
Option /MT is about static C runtime libraries, not static Qt libraries. Using
/MT is discouraged with plugins and DLLs, it's very easy to get things wrong:
http://msdn.microsoft.com/en-us/library/abx4dbyh.aspx
Because a DLL built by linking to a static CRT will have its own
CRT state, it is not recommended to link statically to the CRT
in a DLL unless the consequences of this are specifically desired
and understood.
--
[ signature omitted ]
Message 9 in thread
"Dimitri" <dimitri@xxxxxxxxxxxxx> сообщил/сообщила в новостях следующее:
news:g0sjg8$9dc$1@xxxxxxxxxxxxxxxx
> Hi,
>
>> May be i missed something but i don't see in your link any help
>> concerning static compilation.
>
> Running:
> configure -help
> should display the "-static" option, which builds static Qt libraries.
>
>> I mean real static compilation which require MT options in VC compiler,
>> not just using "static"
>> in configure. Changing mkspecs worked nice in all previous versions.
>
> Option /MT is about static C runtime libraries, not static Qt libraries.
> Using /MT is discouraged with plugins and DLLs, it's very easy to get
> things wrong:
> http://msdn.microsoft.com/en-us/library/abx4dbyh.aspx
> Because a DLL built by linking to a static CRT will have its own
> CRT state, it is not recommended to link statically to the CRT
> in a DLL unless the consequences of this are specifically desired
> and understood.
>
> --
> Dimitri
>
:) We all here are programmers and i think all understood what i meant. I
know
what is /MT and i know what i want to do. Yes, i want exclude msvcrt80.dll
dynamical linking and i have reasons to do it. My question was about
assistant,
i don't need help in compilation process. But anyway, thanks for your help.
Problem was solved with particular assistant recompilation.
Thanks all
--
[ signature omitted ]
Message 10 in thread
Hi,
> :) We all here are programmers and i think all understood what i meant.
> I know
> what is /MT and i know what i want to do. Yes, i want exclude msvcrt80.dll
I'm sorry, I didn't mean to offend you.
> dynamical linking and i have reasons to do it. My question was about
> assistant,
> i don't need help in compilation process. But anyway, thanks for your help.
> Problem was solved with particular assistant recompilation.
I was just trying to point out that you need to run "configure -static" in
addition to adding /MT to the mkspecs file, so that plugins are static
libraries linked with a build-time, instead of DLLs loaded at run-time - which
will probably fail with static a C run-time.
--
[ signature omitted ]
