<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
In the library descriptor you must specify paths to shared objects, not
to symbolic links. <br>
The tool checks only interfaces that have been found in the specified
shared objects. In your example any shared objects have not been found
and therefore you got empty reports. In the next version (beta4) we
will add ability to specify symbolic links along with paths to shared
objects.<br>
<br>
Thiago Macieira wrote:
<blockquote cite="mid:200907291252.18961.thiago@kde.org" type="cite">
<pre wrap="">Em Quarta-feira 29 Julho 2009, às 09:31:36, Thiago Macieira escreveu:
</pre>
<blockquote type="cite">
<pre wrap="">Andrey Ponomarenko wrote:
</pre>
<blockquote type="cite">
<pre wrap=""> Colleagues, I'm a lead developer from Institute for System
</pre>
</blockquote>
</blockquote>
<pre wrap=""><!---->[snip]
</pre>
<blockquote type="cite">
<pre wrap="">I've now got the tool to run. I'll let you know what the results are.
</pre>
</blockquote>
<pre wrap=""><!---->
After running for a 10 minutes, the tool reported:
cheched headers: 18/18 (100%) )
warning: compilation errors in following headers:
QtCore QtOpenGL QtXml QtNetwork QtXmlPatterns QtAssistant QtHelp QtWebKit
QtTest QtDBus QtScript QtSql QtGui QtScriptTools QtUiTools QtDesigner QtSvg
Qt3Support
(I think you meant "checked headers", please run a spell checker in your
tools)
So 18 out of 18 headers failed to compile. Here's why:
$ head -n3 header_compile_errors/Qt/errors_v1
cc_tmp/Qt1.h:1:46: error: /* This section is not necessary */: Arquivo ou
diretório não encontrado
cc_tmp/Qt1.h:2:85: error: /* For example, it is a tree.h for libxml2 and
ft2build.h for freetype2 */: Arquivo ou diretório não encontrado
cc_tmp/Qt1.h:3:67: error: /* This section is useless when -fast option
selected */: Arquivo ou diretório não encontrado
So apparently I cannot leave the comments in the sections of the descriptor
file. Since the descriptor example the tool generates leaves them, it's
misleading. Please fix that.
And why didn't it bail out after the first one failed to compile? I didn't have
to wait 10 minutes to find out that the process would fail.
Also, the tool could say that the results are in the subdirectory.
After fixing all those errors, the tool ran for 12 minutes and generated the
empty report attached. I've also attached the two descriptor files.
What did I do wrong? I doubt that it needed 12 minutes to generate a listing
of files I had given it as input.
</pre>
</blockquote>
</body>
</html>