Re: dllobject/libobject

"Lars Ivar Igesund" <[email protected]>
Newsgroups gmane.comp.tools.aap.devel
Message-ID <06fd01c377dc$894cfb60$0200000a@mesmer>
----- Original Message ----- 
From: "Bram Moolenaar" <[email protected]>


> It appears indents are messed up.  Does your mailer replace tabs with a
> space?

Since it's Outlook Express, I expect it to mess up as much as possible.

>
> From the tail of the log:
>
> > depend: 3 - Updating "build-nt\bar.sob" from "bar.d{filetype=3Dd}": no =
> > old signature for "bar.d"
> > extra: Do compile d -> dllobject
> > error: Error in recipe "c:/documents and settings/lars =
> > ivar/aap/startup/dmodule.aap" line 85: Error executing commands for =
> > compile d: Error in recipe "c:/documents and settings/lars =
> > ivar/aap/startup/dmodule.aap" line 32: No commands defined for =
> > compile_dmd dllobject from d
>
> Where did that "compile_dmd" come from?  There must be a
> ":do compile_dmd <file>" somewhere, and there apparently is no
> compile_dmd action defined for a 'dllobject" filetype.

It came from the tool file.

>
> If you can't figure it out, please send the whole dmodule.aap to me,
> otherwise we keep doing it bit by bit.

I have figured it out now. I specified
compile_dmd object,dllobject,libobject d
in the dmd tool file. In the case where these objects would need to
be compiled in different ways or at least with different flags, would
I then need to define D_COMPILE_ACTION,
D_DLL_COMPILE_ACTION, etc?

Also, another problem, dmd don't get the sob DLLOBJSUF, it need
.obj. How/where should this be set up?

A child recipe problem I forgot to mention in my last mail; If the objects
are kept in a subdir and pointed to through :child, there aren't created
any dependency log in the subdirs.

Lars Ivar Igesund



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.