|
![](/i/fill.gif) |
On 4/23/2011 9:42, Darren New wrote:
> So I stick in a file with the name "manifest", say "compile
> this with the manifest processor".
Oh, and if there's parameters specific to that compile (like, whether to
compress images or something), they're represented as properties with an
attribute set (basically, in the "javabean" kind of sense), and the build
system looks at the executable after it's built in order to give the GUI a
mechanism to prompt for which parameters need to be changed. It then records
those parameters into the build file again in XML, and passes them to the
processor when it recompiles anything in that dependency chain.
Overall, a very cool system. It just takes a bit of cooperation from the
compiler to make it all work seamlessly.
--
Darren New, San Diego CA, USA (PST)
"Coding without comments is like
driving without turn signals."
Post a reply to this message
|
![](/i/fill.gif) |