Re: dllobject/libobject

----- Original Message ----- 
From: "Bram Moolenaar" <[email protected]>


> Did you try:
> 
> :action compile object,dllobject,libobject,default d
> etc.

I had, but something went wrong on the way, see below.

> 
> 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.

It seems like my test example wasn't minimal enough. At the same time
it might have revealed a problem with subdirs.

Now; I created a dir foo with a file bar.d and a main.aap. The main.aap
contained this line:

:dll foo : bar.d

which gave the attached log file. The action it complains about is this:

:action compile object,libobject,dllobject,default d
    @if not _no.get("target"):
 target = `src2obj(fname)`
    @if _no.get("D_COMPILE_ACTION"):
 :do $D_COMPILE_ACTION {target = $target} $source
    @else:
 :buildcheck $OPTIMIZE $?DEBUG
 :sys $DC $DFLAGS $?DEFINE $?INCLUDE -c -of$target $source

:rule {default} %$OBJSUF : {buildcheck = $DC $DFLAGS $?DEFINE $?INCLUDE 
                                            $OPTIMIZE $?DEBUG } %.d
    :do compile {target = $target} $source

> 
> 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 already do this.

> 
> 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.

I didn't quite understand that, but then I don't think I need this yet/that
this is the problem.

Lars Ivar Igesund