Re: Extra dependencies for libtool objects?

Adriaan de Groot wrote:

> When using libtool to build things, a .lo file is created (that's
> $OBJEXT for ltobjects), while the real .o file lives hidden in a
> .libs/ directory. AAP sees only the .lo file, which rarely changes
> (it's just text describing the compile flags and where the .o file
> is). This in turn means that when the .o file changes, AAP _doesn't_
> see it, doesn't re-link anything, and generally makes a mess of
> updating things. How can I make, say, a ltlibrary also depend on the
> .o files which are generated in an automatic manner?

I haven't tried it, but something like this should work:

	:rule %.lo : %.o

The different directory might be a problem, you'll have to figure that
out.

A more advanced method would be to read the .lo file to find out where
the .o file is and take that into account in the checksum.  I think that
would have to be done in the Aap source code, I can't recall a way to
define a different checksum based on the file type.  You could define a
different checksum on a dependency though.

--=20
Momento mori, ergo carpe diem

 /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net   \=
\\
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ =
\\\
\\\        download, build and distribute -- http://www.A-A-P.org        =
///
 \\\            help me help AIDS victims -- http://www.ICCF.nl         /=
//


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log fi=
les
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D103432&bid=3D230486&dat=3D=
121642