Hi Peter,
I'm no expert on the Generator's caching logic, but from what I can see,
only the ".cache_check_file" should be stored in the "cache" directory
next to the config.json file. If you create a custom compile job, the
actual cache entries should be created in TMPDIR/cache, with TMPDIR
defaulting to whatever tmpdir.gettempdir() returns for your system.
Regards,
Daniel
Peter Schneider schrieb:
> Hi again,
>
> the issue I posted lately[1] seems to be much more severe.
> It seems that _every_ custom job will create a "cache" directory...
>
> As an example (for reproduction purposes) I have added a job "ls", that does
> nothing more than issuing the "dir" command (I'm working on windows).
>
> <code src="config.json">
> {
> //...
> "export" :
> [
> //...
> "ls",
> //...
> ],
> "let" :
> {
> "APPLICATION" : "application",
> "QOOXDOO_PATH" : "../qooxdoo",
> "QXTHEME" : "application.theme.Theme",
> "QXICONTHEME" : ["Tango"],
> "API_EXCLUDE" : ["qx.test.*", "${APPLICATION}.theme.*",
> "${APPLICATION}.test.*"],
> "LOCALES" : ["de", "en"],
> "CACHE" : "${TMPDIR}/cache",
> "ROOT" : "."
> },
> "jobs" :
> {
> //...
> "ls" :
> {
> "desc" : "ls command",
> "shell" : {
> "command" : "dir"
> }
> },
> //...
> }
> }
> </code>
>
> Each time I issue "generate ls", the generation process creates a directory
> called "cache" in the directory where config.json exists.
> Even extending the job definition with a "cache" config-key doesn't change the
> behavior:
> <code>
> //...
> "ls" : {
> "desc" : "ls command",
> "cache" : "${CACHE}",
> "shell" : {
> "command" : "dir"
> }
> },
> //...
> </code>
>
> I think this is an error, but I'll not file an error yet. Maybe the problem is
> on my side.
>
> Regards,
> Peter
>
>
> -----
> [1]
> http://n2.nabble.com/info-job-creates-uses-new-cache-tp4823453p4823453.html
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> qooxdoo-devel mailing list
> qooxdoo-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
>
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
