Ok. That worked. Finally ;-)

Looks like qx.ui.container.Composite is missing a ";" in the very end.

Cheers,
Cajus

Am 27.06.13 17:00, schrieb thron7:
> On 06/27/2013 04:17 PM, Cajus Pollmeier wrote:
>> Hmm. Neither OPTIMIZE, nor "format: true" show any effect.
> Did you run 'distclean' in between?!
>
>>   Maybe because I'm building a separate version for every engine? Or - is 
>> there a place where these options can be inserted so that it works in
>> every case?
> No, they should take effect right away. You can check with which job 
> definition a job is run by adding the '-w' flag to the generator. Before 
> the actual work starts, a fully expanded job definition is printed to 
> the terminal. There you can check e.g. the "compile-options".
>
>
>> {
>>    "let" :
>>    {
>>      ...
>>      "OPTIMIZE"     : []
>>    },
>>
>>    "build" :
>>    {
>>        "desc"   : "create build version of current application",
>>
>>        "environment" :
>>        {
>>          "qx.globalErrorHandling" : true
>>        },
>>
>>        "run" :
>>        [
>>          "image-svg-convert",
>>          "image-optimize",
>>          "online-help",
>>          "build-resources",
>>          "build-script",
>>          "build-files",
>>          "build-customize"
>>        ]
>>      },
>>
>>      "build-script":
>>      {
>>        "environment" :
>>        {
>>          "engine.name" : [ "gecko", "mshtml", "webkit", "opera" ]
>>        },
>>
>>        "compile-options" :
>>        {
>>          "paths"  :
>>          {
>>            "file" : "${BUILD_PATH}/script/${APPLICATION}-{engine.name}.js"
>>          },
>>
>>          "code" :
>>          {
>>            "optimize" : [],
>>            "format" : true
>>          }
>>        }
>>      },
> This is actually a combination that cannot work :). Either use OPTIMIZE 
> or compile-options/code/optimize, but not both. If you set code/optimize 
> directly, there is no longer a reference to the makro, so its value 
> becomes irrelevant for this job. (In the default job definition is 
> code/optimize:"${OPTIMIZE}", hence you can influence it by override the 
> macro).
>
> But if you want to go with code/optimize directly, you have to give it as
>
>    ...
>    "code" : {
>      "=optimize" : []
>    ...
>
> (mind the leading '='). Otherwise this key will *merge* with the default 
> setting, so you end up having all optimizations on again.
>
> T.
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> qooxdoo-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel


------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to