Bug#415280: zaptel-source: does not compile - cwain.cc missing?

[Tzafrir Cohen]

On Tue, Mar 20, 2007 at 09:47:34PM +0000, Mark Purcell wrote:
> On Saturday 17 March 2007 20:35, Cybaer wrote:
> > I used m-a then but - of course - the cwain.c error is still there.
> > There is no cwain.c and e.g. zaphfc.c in the dfsg-2 tarball (which
> > existed in dfsg-1)
> 
> Tzafrir,
> 
> Your commit r3216 on svn.debian.org:
> 
> Seems to add the lines to debian/rules
> 
> GENERATED_SOURCES+=$(BRISTUFF_MODULES:%=%.c) $(BRISTUFF_MODULES:%=%.h)
> [...]
> rm -f $(GENERATED_SOURCES)
> 
> Which seems to be deleting cwain.c and others.
> 
> # Add here commands to clean up after the build process.
> rm -rf modexamples
> rm -f tonezones.txt
> rm -f version.h radfw.h tor2fw.h tones.h  cwain.c qozap.c zaphfc.c ztgsm.c cwain.h qozap.h zaphfc.h ztgsm.h
> 
> 
> What were you trying to archive with the GENERATED SOURCES line?

The zaptel makefile is really bad and has no good way to run stuff on
the host processor. I gave up on trying to get the modules builder to
build radfw.h, tor2fw.h and tones.h . So I decided to do this in the
build of the zaptel package.

As for the bristuff modules: the simplest way to build them is to copy
them to the main zaptel directory and add them to the MODULES list. This
removes the need to provide 4 extra copies of all the makefiles. However
copying them means that they are generated as well.

How can I tell that the clean-unpatched is run from a modules building
process rather than from the main package building?

-- 
               Tzafrir Cohen       
icq#16849755                    jabber:tzafrir at jabber.org
+972-50-7952406           mailto:tzafrir.cohen at xorcom.com       
http://www.xorcom.com  iax:guest at local.xorcom.com/tzafrir