I forgot something. When using a complex application namespace, the generated
script will not have the .js file extension, but only consist of the full
application namespace, e.g. "net.sf.custom" instead of "net.sf.custom.js". Okay,
that one is a minor problem because it can be avoided using the
APPLICATION_SCRIPT_FILENAME directive, but I think it should be fixed.
Thanks,
Fabio
[EMAIL PROTECTED] wrote:
> Hi,
>
> I am using the latest 0.7.1 release of qooxdoo. Building runs under Windows XP
> with the latest cygwin release. I encountered some building problems:
>
> Internationalization
> When using internationalization with an APPLICATION_SOURCE_PATH containing
> spaces (which are correctly escaped, like "/cygdrive/d/my\ dir" - without
> quotes!), xgettext failes with the following error, thus only producing empty
> .po-files, no messages.pot and no .js files:
>
> PREPARING APPLICATION TRANSLATION
> ----------------------------------------------------------------------------
> * Processing source code...
> xgettext: error while opening "/cygdrive/d/my" for reading: No such file or
> directory
> * Processing translations...
> - Translation: C
> - Merging translation file...
> - Generating catalog...
> - Translation: en
> - Merging translation file...
> - Generating catalog...
> - Translation: de
> - Merging translation file...
> - Generating catalog...
>
> I am now using 8.3 filenames, like "/cygdrive/d/MYDIR~1".
>
>
>
> Application namespace
> Though the documentation of APPLICATION_NAMESPACE declares "Even complexer
> stuff
> is possible like: net.sf.custom", it does not work. Loading an Application
> using
> such a complex namespace causes the following exception:
>
> Malformed settings key "net.sf.custom.resourceUri". Must be following the
> schema
> "namespace.key". in Setting.js (line 153)
>
>
>
> Additional resources
> Using the APPLICATION_FILES option, all files and directories supplied are
> correctly copied into the "build" directory. However, cygwin sets "chmod 0"
> for
> every single resource so that files cannot be read, and directories not be
> traversed.
> My workaround is to perform the following commands to build:
> make build && chmod -R 755 build/ && find build/ -type f -exec chmod 644 '{}'
>
>
> Regards
> Fabio
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> qooxdoo-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
