> Nevertheless I've added our "old" makefile, so you can make your suggestions,
> If you have time for that...(I've walked along with another "solution" as
> mentioned above)
> The directory structure is attached as well, to make it "easier" to navigate.
>
First, let me acquaint you with the path-like expressions, to signify
configuration keys and their values: Nesting of configuration keys is
expressed by chaining with "/", as in nested directories on your file
system. So a "config path" like "log/dependencies/dot/radius" actually
means the subkey "radius" of the subkey "dot" of the subkey
"dependencies" of the (job) key "log" (which you can find in the
configuration reference page). To make it easier for you, I will prefix
job keys with the "absolute" path they have in the overall config, e.g.
including the "jobs" top-level key, so the above key would actually be
expressed as:
"jobs/<job_name>/log/dependencies/dot/radius"
where <job_name> would be some valid job name in a config file.
So here are some mappings of your old Makefile variables:
APPLICATION_OPTIMIZE_VARIABLES = false =>
let/OPTIMIZE: ["strings", "basecalls", "privates"]
ie. you leave out the optimization you don't want to have (but I would
delay this until you actually work with the build version; it has no
meaning for the source version).
APPLICATION_ADDITIONAL_SOURCE_OPTIONS = --exclude-without-dependencies
... =>
jobs/<job>/exclude: [...]
this allows you to exclude classes from the build. To differentiate
between the source and the build version of your app, override the
following jobs in your config and provide them with individual "exclude"
keys (this can be applied for many keys, not just for the "exclude" key):
"jobs" : {
"source-script" : { "exclude" : [...], ...},
"build-script" : { "exclude" : [...], ...},
...
}
LINT_ALLOWED_GLOBALS = google Map24 =>
use the #ignore directive [1] in the affected source files (for the
compiler) or the @lin ignore JsDoc comment [2] (for the ecmalint tool)
/*
#ignore(google)
#ignore(Map24)
*/
/*
* @lint ignore(google)
*/
mymember : function() { ... google... }
[1] http://qooxdoo.org/documentation/1.0/code_structure
[2] http://qooxdoo.org/documentation/1.0/tool/source_code_validation
APPLICATION_ADDITIONAL_SOURCE_OPTIONS += --use-setting=... =>
the same applies here what I said about the "exclude" key, now for
the "settings" key.
Concerning treeinfo.txt:
You should move source/html to probably source/resource/html. You can
have the files there copied during creating the build version, we can
get back to that once the source is running fine.
The 'Makefile' is no longer used (but doesn't hurt either). But you need
a config.json and a Manifest.json file. But you probably have both as
otherwise we wouldn't be talking about configuration issues.
Your qooxdoo installation looks very old, certainly not 0.8.3! So this
shouldn't be the qooxdoo installation you are working against right now.
All in all this treeinfo looks pretty outdated, and I doubt it reflects
your current environment.
T.
------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
