Re: Autoconf/Automake patches

Replying to Wilfried Goesgens:
> I've used the kannel source you provided on your website, i didn't find 
> the patch mentioned on the ml last September. 

I admit that current situation with patchset is a complete mess. You
can look at latest patchset I've uploaded yesterday. File "automake"
from it should apply against latest kannel cvs head.

> > 3. what the point in separating smsc/* files into library?
> make and Automake is not able to cope with subdirs, unless you do nasty 
> things. So you do a static lib, which is linked at compiletime. 
> Thats a widely used way to solve this problem.

Hmm. I periodically doing a "make distcheck". It actually - guess what
- it BUILDS everything, in a completely different directory than
source ...

> Allso it's anoying not being able to just do make in Emacs and get your 
> compile errors from the source you just edited.

Did you read
http://www.pcug.org.au/~millerp/rmch/recu-make-cons-harm.html
?

(And yes, recursive make IS harmful, I learned it in the days of
kbuild 2.5 ...)

> Allso you shouldn't use relative paths in the Makefiles, you use ${topsrcdir}
> to make autoconf expand that. This enables foreign or aliend build, 
> i.e. configuring and building in a completely different directory than
> the source.

I've tested the thing using make distcheck ...

-- 
Paul P 'Stingray' Komkoff Jr // http://stingr.net/key <- my pgp key
 This message represents the official view of the voices in my head