On 03/05/2010 02:51 PM, Peter Schneider wrote:
> Hi Thomas,
>
> I came across the issue again and can give some more information:
>
> a) The generated script works "flawlessly". The generated script only differs
> in the qx.$$translations map (I've expected that ;) )
That's good to know, so I think this is just a minor (if annoying)
glitch of the logging layer.
>
> b) Every "generate source" complains about some 'qx.ui.layout...' or similar
> unknown symbol reference.
> (In this special case it was "qx.ui.layout" and "qx.ui.form")
Ok, I take "or similar" to mean "other packages names" (all-lower-caps
names that do not end in a (capitalized) class name), just as
qx.ui.layout and qx.ui.form.
> c) When I add a line of code that is creating another new instance of a
> qooxdoo-class (which has been used in the module already) the complaining
> stops.
> (Is the re-build of the dependency-tree triggered by the 'new' keyword?)
Well, it is triggered whenever the corresponding class code might have
changed, so a simple 'touch' on the class file will do that for you, you
don't need to actually change the code :).
Once this has been done, the cached information is used until another
change of the time stamp of the class file is detected. This also
explains why the complain is recurring: Once the fake dependency slips
in, it is cached and the information is re-iterated with every build run.
What you could do once the issue re-appears: Without clearing the cache,
or modifying the class file, modify the configuration of the 'source'
job. In your config.json, add a source-script job like this to the
"jobs" section:
"source-script" : {
"log" : { "dependencies" : { "type" : "using" }}
}
Capture the output of the 'generate.py source' run in a file and search
for the application classes that have the warnings, e.g. look for
entries like this:
- Class: infodesk.ui.info.WinAbout
- Uses ...
...
Post these sections for the affected classes here on the list.
Cheers,
T.
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
