On 10/03/2011 05:08 PM, John Spackman wrote:
> Hi Thomas,
>
> That's done: http://bugs.qooxdoo.org/show_bug.cgi?id=5671
yep, got it.
> About the config though - do you mean that if an inherited or included job
> sets a specific range of values (i.e. by using '=' prefix) then derived
> jobs must
Hi Thomas,
That's done: http://bugs.qooxdoo.org/show_bug.cgi?id=5671
About the config though - do you mean that if an inherited or included job
sets a specific range of values (i.e. by using '=' prefix) then derived
jobs must also know to use that range and use the '=' prefix?
John
On 01/10/201
> Hi
>
> I've got an odd problem with the source-hybrid job in 1.5; if you specify
> compile-options/code/except then every source file from every library is
> loaded one by one (i.e. it's the same as the "source" job). Using
> generate.py w, it appears that "*" is added to the "except" key.
>
>
Hi John,
sorry, I can't help you. Thomas is our generator expert and he is at the
moment not at the office. I forward you question and he will answer your
question as soon as possible.
Cheers,
Chris
Am 30.09.2011 13:12, schrieb John Spackman:
Hi
I've got an odd problem with the source-hybr
Hi
I've got an odd problem with the source-hybrid job in 1.5; if you specify
compile-options/code/except then every source file from every library is
loaded one by one (i.e. it's the same as the "source" job). Using
generate.py w, it appears that "*" is added to the "except" key.
For example, c
