Re: More on Actions, routes and builders in general

Lars Ivar Igesund wrote:

> In the d.aap module, the only difference between the object,libobject 
> and dllobject out types were their build attribute. What I did there, 
> was to have an action d_compile that did the main work, and three 
> compiles; one for each out type that only added the buildaction 
> attribute before executing d_compile. Do I still have to do it this way, 
> or can I find out what the outtype of action should be ($OUTTYPE) so I 
> can add the correct buildaction based on that variable?
> 
> Something like:
> 
> @if OUTTYPE == "libobject":
> 	:attr {buildaction = buildlib} $target

We don't have $OUTTYPE.  I think this is just a small optimization, not
really worth changing.

Looking at the d module I notice that the d_compile, d_build, d_builddll
and d_buildlib actions use ":do" to redirect the work to another action.
Those should be rewritten to use define_action().

It's strange that d_buildlib doesn't do anything when D_BUILDLIB_ACTION
is not set.  Not even an error.

-- 
hundred-and-one symptoms of being an internet addict:
122. You ask if the Netaholics Anonymous t-shirt you ordered can be
     sent to you via e-mail.

 /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net   \\\
///        Sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\              Project leader for A-A-P -- http://www.A-A-P.org        ///
 \\\  Buy at Amazon and help AIDS victims -- http://ICCF.nl/click1.html ///


-------------------------------------------------------
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND