Re: dllobject/libobject

Lars Ivar Igesund wrote:

> > > Must I do anything special to get compileactions
> > > for dll and libobject to work compared with 'normal'
> > > objects?
> >
> > Currently there is no special compile action for "libobject".  Thus it
> > is expected that the normal compiling works for creating an object file
> > that is to be linked into a library.
> 
> For the time being, the difference between dllobjects/libobjects and objects
> with the D compiler, must be handled by the programmer, no extra flags are
> needed when compiling/linking. Thus I want to alias dllobject/libobject to
> object. But aap keep telling me that it don't know how to create libobject/
> dllobject from foo.d. I have created a route:
> :route {default} d object,dllobject,libobject
>     compile

That is OK.  It means that Aap will know how to turn "d" source files
used with ":program", ":lib" and ":dll" into object files using the
"compile action".

> I've tried with actions:
> :action compile dllobject d
>     etc
> 
> and
> 
> :action compile object,default,dllobject d
>     etc
> 
> It works fine to compile objects for a program, but not libs or dlls.
> I guess I need to support i through the tool file.

Did you try:

	:action compile object,dllobject,libobject,default d
		etc.

If it still doesn't work you can see in AAPDIR/log what dependencies
were generated for the ":program", ":lib" and ":dll" commands.  I can't
say much else without seeing the error you get.

> > The existing tools "bcc", "icc" and "msvc" could probably be extended to
> > handle "dllobject" (and perhaps "libobject").  This should be done by
> > someone who can try it out.  Ideas can be obtained from looking at the
> > SCons stuff.
> 
> If I were to do it through tools, I would have to add
> D_DLL_COMPILE_ACTION, etc, right? I want all possibilities to
> be available, after all.

Currently there is no default compile action for "d".  If you do add
one, you can use D_COMPILE_ACTION to allow tools to specify an alternate
action.

I have not included "LIB" or "DLL" in this variable name.  The reason is
that when you change the action for normal compiling, it is very likely
that the action for compiling to dllobject and libobject changes as well.
Sometimes the commands to be executed are identical.  The action that
the tool defines may check the filetype of the target to find out if the
compiler needs specific flags.  The Python function get_attr() is
provided for this.

-- 
Two cows are standing together in a field.  One asks the other:
"So what do you think about this Mad Cow Diesease?"
The other replies: "That doesn't concern me. I'm a helicopter."

 /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net   \\\
///          Creator of Vim - Vi IMproved -- http://www.Vim.org          \\\
\\\              Project leader for A-A-P -- http://www.A-A-P.org        ///
 \\\  Help AIDS victims, buy here: http://ICCF-Holland.org/click1.html  ///


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf