>> File "/Users/jbb/Dev/Projects/novlog2/qooxdoo/qooxdoo-0.8.3-sdk/
>> tool/bin/generator.py", line 165, in <module>
>> main()
>> File "/Users/jbb/Dev/Projects/novlog2/qooxdoo/qooxdoo-0.8.3-sdk/
>> tool/bin/generator.py", line 160, in main
>> generatorObj.run()
>> File "/Users/jbb/Dev/Projects/novlog2/qooxdoo/qooxdoo-0.8.3-sdk/
>> tool/pylib/generator/Generator.py", line 459, in run
>> smartInclude, explicitInclude =
>> getIncludes(self._job.get("include", []))
>> File "/Users/jbb/Dev/Projects/novlog2/qooxdoo/qooxdoo-0.8.3-sdk/
>> tool/pylib/generator/Generator.py", line 344, in getIncludes
>> smartInclude = self._expandRegExps(smartInclude)
>> File "/Users/jbb/Dev/Projects/novlog2/qooxdoo/qooxdoo-0.8.3-sdk/
>> tool/pylib/generator/Generator.py", line 1310, in _expandRegExps
>> raise RuntimeError, "Expression gives no results. Malformed
>> entry: %s" % entry
>> RuntimeError: Expression gives no results. Malformed entry:
>> novlog.composer.theme.Theme
>>
In general, this is to inform you that the generator tried to include a
class (or classes), which it couldn't find. The class has to exist, and
has to be part of a configured library.
> I retry my yesterday's test but I did a generate.py clean before ...
> and it is not the same message at all now ...
> So, BTW, when should I play clean and when could I avoid it ? DO I
> have to clean before any generate build or source ?
>
No, normally you should never have to run 'clean' or 'distclean' at all
- unless, of course, you want to clean up your environment, e.g. for
packaging, backup, etc. Admittedly, there are some cases where wiping
the cache directory is necessary, to overcome issues based on stale
cache objects. But this should be really rare for normal app development.
> I still have that one that confirm the job library look like OK (am I
> correct ?) :
> >>> Resolving config includes...
> - ! Shadowing job "libraries" with local one
>
As I explained in another posting to Jean-Noel yesterday, this is just a
hint to inform you that you are defining a job ("libraries" in this
case) in your local config that is of the same name as a pre-defined
job, which will be shadowed by the local one. This is just to prevent
accidental shadowing; if you do it on purpose (as in your case I
suppose), it's fine.
> Then, that one, that also look like encouraging :
> >>> Scanning libraries...
> - Scanning /Users/jbb/Dev/Projects/novlog2/qxfwk/qxfwk...
>
Yep, it shows that the generator is looking into your qxfwk library. The
second line of the message will disappear in subsequent generator runs,
until something in that library changes and the library is re-scanned.
> after that a long serie of dependency error :
> >>> Resolving dependencies...
> - ! Unknown class referenced: novlog.fwk.ui.AbstractWindow (in:
> novlog.composer.ui.ApplicationWindow)
>
It says that the class novlog.fwk.ui.AbstractWindow is used in
novlog.composer.ui.ApplicationWindow, but was not found during library
scanning. Do you have a class of that name? Is it in one of the
configured libraries for this app?
> again, remember that for qxfwk, the root package is novlog.qxfwk and
> for composer app, it is novlog.composer
>
Yes, but as you can see from the above generator message, you are *not*
referencing novlog.qxfwk.ui.AbstractWindow in your code, but
novlog.fwk.ui.AbstractWindow - so which one is right?!
> I now remember that in comments on generated material (by create-
> application) I've seen : #asset(novlog.composer/*) for example.
> Is that mandatory to include dependency ?
>
asset declarations are only necessary for resources (like images), not
for classes. But be aware that the argument to #asset is a *file glob*,
so in your example it should probably read #asset(novlog/composer/*).
> I then added in all previous errors that 2 assets :
> #asset(novlog.composer/*)
> #asset(novlog.fwk/*)
>
See my previous comment. And again, here you have "novlog.fwk", rather
than "novlog.qxfwk" - which one is right?!
> I guess this is only for build target : all fwk will be included with
> composer. If yes, I don't care snce I'm not using (yet) parts and in
> fact, all fwk is usefull, so in fine, it has to be all included. Am I
> correct ?
>
Again, I can only guess what you mean. But as I said before (multiple
times, I think), when you run a 'generate.py source' or 'generate.py
build', only the *necessary* classes will be included. You can configure
as many libraries in your config.json as you like. If the classes of
those libraries are never used in your app code, then the classes will
not be included. (The only exception being when you run 'generate.py
source-all', which tries to incorporate all classes of all known
libraries; or if you force inclusion of classes with the "include"
config key, which shouldn't be necessary except in specific cases.).
T.
------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
