Hmm. Neither OPTIMIZE, nor "format: true" show any effect. 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?
{
"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
}
}
},
...
}
On 27.06.2013 15:17, thron7 wrote:
>
> On 06/27/2013 02:04 PM, Cajus Pollmeier wrote:
>> On 27.06.2013 12:38, thron7 wrote:
>>> Cajus,
>>>
>>> - What is the commit that you pulled? (The issue might have been fixed
>>> meanwhile)
>> I don't know, but I tried again using
>> d6b28021dc9dd527a4604cb37acb220f2079a118 which seems to be the latest one
>> available on github. Same error.
>>
>> Chrome:
>>
>> Uncaught SyntaxError: Unexpected token && /test/script/bj-webkit.js:210
>>
>> Firefox:
>>
>> SyntaxError: missing ; before statement @
>> https://bj.gonicus.de/test/script/bj-gecko.js:210
>>
>>
>>
>>> - Which code caused the exception? A minimal example to trigger it would
>>> be helpful.
>> Well. Since this in "build" only and the code complained about is sitting on
>> one line filling ~16 printable pages of compressed javascript, containing
>> dozends of "&&" or ";", I'm not sure what to do
>> in this case.
>>
>> Just tried to disable the optimization, but it still generates compressed
>> code. What do I need to do besides setting OPTIMIZE = []?
>
> This weird. I could reproduce this issue, and now I can't! Please open a
> bug for it anyway.
>
> To work around it, try running 'generate.py distclean' and then re-run
> build with OPTIMIZE=[]. This should provide you with a version that is
> fully readable.
>
> Alternatively, you could set format:true, to at least get some line
> breaks. Still not so easy to relate that back to the original code. But
> it has the advantage that the usual optimziations are in if the issue is
> actually caused by one of them:
>
> "build-script" : {
> "compile-options" : {
> "code" : {
> "format" : true
> }
> }
>
>
> 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
