Automake and literate programming

[Ralf Hemmecke]

Hello,

I would like to use Automake for the creation of a library. I am not so 
sure whether this is the right place to ask since I also wanted to 
consider LibTools, but I am not so far, yet.

All my source files are Noweb files 
(http://www.eecs.harvard.edu/nr/noweb/). Additionally, these files 
contain Aldor (http://www.aldor.org) source code.

Now, the way to compile a library is as follows.

notangle foo.as.nw > foo.as
aldor -fao foo.as
  # This generates the file foo.ao.
ar rv mylib.al foo.ao
aldor -fo -l mylib foo.ao
  # This generates the file foo.o.
  # If needed, the compiler could produce a .c file from
  # an .ao file. 'aldor -fc -lmylib foo.ao'
  # The .c file is intermediately really produced anyway and
  # compiled with a C compiler.
ar rv mylib.a foo.o
ranlib mylib.a

Of course, the library would contain foo1, foo2, etc.

As you can see, there are, in fact, two libraries, namely, mylib.al (a 
library of machine independent object code) and mylib.a (machine 
dependent code). The two libraries have to be distributed.

Can I somehow use the standard primaries to tackle this case?

Further, documentation 'make dvi' should also take the .nw files as sources.

noweave foo.as.nw > foo.as.nw.tex
latex foo.as.nw.tex

(Yes, I want those triple extensions, since the foo* files are actually 
concatenated or rather included in a main .tex file.)

Until now I have the impression, that I have to do everything by hand, 
ie. that Automake doesn't give me much help in the build process.
OK, I get all the standard targets and also VPATH compilation (which I 
really appreciate), but otherwise I am quite unsure if Automake could 
make my Makefile.am shorter.

It also seems that Libtool cannot help me at all. Any ideas?

Thank you in advance for any hints.

Ralf Hemmecke