> From: Peter Donald > > Request 3: > ---------- > > Could taskdefs be specified immediately. ie. move the main > chunk of it from > init to execute. This would allow a single build file to compile the > taskdefs it needs and then use those in turn to do further > processing. I > have to run build twice to get this solved and it bugs the > hell out of me :P.
We have exactly the same situation (some custom tasks that need to be built to make the main build work), so you can count this as a second vote ;) Tom Newton > > Request 4: > ---------- > > A standardised set of taskdefs for invoking standard C/C++ > tools (ie tasks > like make, cpp, cc, link etc). I keep writing hacky ones for whatever > particular compiler I am using at the time that are basically > execs. Most > of my compilations have relatively standard parameters so > maybe it would be > an idea to amalgamate them all into one task that then delegates to > appropriate lower-level driver ???? > > > ---------------------- > > I got a whole bunch of other requests but gotta eat now and > besides they > are even more ludicrous than the ones I said above. So > thoughts on it ? > Good/bad idea ? Improvements ? volunteers ? If people think > it is a good > idea and no one volunteers I can can do it but it wont be a while > unfortunately :< > > > Cheers, > > Pete > > *------------------------------------------------------* > | "Nearly all men can stand adversity, but if you want | > | to test a man's character, give him power." | > | -Abraham Lincoln | > *------------------------------------------------------* >
