thron7 wrote: > > > This is stark, Dan! I'm glad it works for you, but I don't recommend > this as a general strategy. > > For one thing you defined a "run" job, which is fine. But you have to be > aware that every run job is (recursively) replaced by it's subjobs (the > jobs in the run list). But: Whatever you specify in the initial "run" > job becomes part of the replacing jobs (The "run" job is replaced by as > many copies of itself as there are subjobs, and each copy "extend"s the > corresponding subjob). That means that every job that "my-source" is > eventually replaced by will have a "compile-source" key and will run the > compile task! This is normally not what you want. > > In this particular case it didn't matter since the "source" job from > base.json just runs "source-script", which is a "compile-source" job > itself, so you are effectively shaddowing one "compile-source" key with > another, which is fine. But imagine applying the same technique to the > "build" job... >
The only reason I ended up writing the config.json file this way was that this was the only way I found that got the "compile-source" key to affect the build process. I tried putting that same "compile-source" key in several different places in my config.json file, and the result was either that it was ignored (thus default values were used for the generate source command) or a fatal error. When I tried to define my own job named "source" and put the key there, I get this: KeyError: u'Job already exists: "source"'. (I was trying to follow the example config file listed here: http://qooxdoo.org/documentation/0.8/generator_config ) So my question boils down to, if I want to provide "compile-source" arguments to the "source" job, how do you recommend I put them in the config.json file I posted earlier? I've tried putting that key in the top level of the JSON object, in the "jobs" key, and in an individual "job" key. None of those places worked for me unless I defined my own job, which you don't recommend doing. (Also, it doesn't work when I try a build version.) thron7 wrote: > > Here's a little quiz for everybody: > How many times would the compiler generate the build/script/<name>.js > file if you applied the same strategy to the "build" job? How could you > overcome this problem? > > Cheers, > Thomas > No idea, which is why I'm posting here. ;) Thanks for the reply. -Dan -- View this message in context: http://www.nabble.com/Makefile-Migration-from-0.7-to-0.8-questions-and-suggestions-tp19873177p20219462.html Sent from the qooxdoo-devel mailing list archive at Nabble.com. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
