Henrik, > Ahhhh, I see. Thanks! > > Now, I'm not sure, but that didn't quite come through from reading the > docs. Maybe it's just me — maybe there's indeed a need for clarification.
Maybe the most important document to take in once you get into changing the config is [1]. After giving a basic overview over Jason and how we use it, the larger part of the document is a longish listing of the existing config keys and their context (towards the end, "Listing of Keys in Context"). As your error was related to context I wonder whether this was apparent to you. Maybe, as there are only two contexts (top-level and job-level), this fundamental information is not standing out enough, and is overlooked. If you have any suggestions on how to improve on that I'm interested to hear them. [1] http://manual.qooxdoo.org/current/pages/tool/generator_config.html > And yeah, I want the cache itself totally outside my tree, which is why > I specified a different place for the CACHE macro; but I just couldn't > get cache/downloads to behave :) The "cache" key has two sub-keys, "compile" and "downloads". Tristan's hint was right, but you want to change the "download" path, so this is the sub-key you want to be using. If you set this in your config, the compile cache should be in the default path, and the downloads in the path you specify. The CACHE macro, on the other hand, only influences the path to the compile cache, and the download cache is then a subdirectory of that, so they both go together. If you want to separate the two, it is better to set "cache/downloads" in your jobs. If you find yourself struggling with getting the "cache" key working in the right jobs (source, ..., build), you can alternatively try to use the (yet undocumented) CACHE_KEY, which takes an entire map as you would assign to the "cache" config key. Again, specifying the "downloads" sub-key should suffice (tool/data/config/base.json holds a general sample of using this macro). HTH, T. > > On 02/11/11 17:02, Tristan Koch wrote: >> Hi Henrik, >> >> "cache" is not top-level. Try to nest it in a job, something along the >> lines: >> >> "jobs" : >> { >> "common": { >> "cache": { >> "compile": "foo" >> } >> }, >> ... >> } >> >> "common" is used by both "source" and "build" job. >> >> You could also change the CACHE macro if you don't mind your compile >> cache to be somewhere else. >> >> Tristan >> >> Am 02.11.2011 um 15:49 schrieb Henrik Pauli: >> >>> According to the documentation online at [1], there should be a key in >>> config.json called "cache", to be able to control — among other things >>> — >>> the location of downloads. >>> >>> generator.py, however, tells me the following: >>> >>> >>> $ ./generate.py info >>> >>> ---------------------------------------------------------------------------- >>> Initializing: dbmgr >>> ---------------------------------------------------------------------------- >>>>>> Processing configuration >>> - Warning: ! Shadowing job "libraries" with local one >>>>>> Warning: ! Unknown top-level config key "cache" - ignored. >>> >>> >>> Framework version is 1.5 according to info, so I'm reading the correct >>> doc. Download cache path remains unchanged, to my initial >>> /tmp/qx1.5/cache/downloads, which I set in "let": { "CACHE": ... } >>> >>> I'd like to move my downloads closer to my source tree, which is why I >>> needed this config key. >>> >>> >>> [1] >>> <http://manual.qooxdoo.org/1.5/pages/tool/generator_config_ref.html#pages-tool-generator-config-ref-cache> >>> > > ------------------------------------------------------------------------------ > RSA® Conference 2012 > Save $700 by Nov 18 > Register now! > http://p.sf.net/sfu/rsa-sfdev2dev1 > _______________________________________________ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > > > ------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
