[Asterisk-Users] Compiling Asterisk-addons

[Armin Schindler]

On Wed, 31 May 2006, Joshua Colp wrote:
> On 5/31/06 3:03 PM, "Armin Schindler" <armin at melware.de> wrote:
> >> 
> >> You can't be serious.  I can't believe you just said that.
> > 
> > Why not? It was just a question, because I don't understand why everyone
> > (from digium) is saying that the addons must be fixed, but I see the problem
> > in the asterisk trunk. That's all I'm saying... for the third time now.
> > 
> >> We're working
> >> really hard to get trunk ready for 1.4, there are other things that are more
> >> pressing to work on right now.
> > 
> > Yes, sure. I don't doubt that. And I personally thank you for all that work.
> > I would like to join development if I wouldn't need to disclaim.
> > 
> >> This is an open source project, so if you wish
> >> to provide any patches to fix -addons, that is certainly welcome.  Otherwise,
> >> sit back and enjoy the ride. :-)
> > 
> > I work for 'addons' too. chan-capi.org in my case. So I'm not just sitting
> > back.
> > And again, I just wanted to point out, that the current trunk is the
> > problem which prevents other modules from build. But this seems to be
> > ignored, because the respond is always: the addons must be fixed.
> > That's all.
> > 
> > Armin
> > _______________________________________________
> > --Bandwidth and Colocation provided by Easynews.com --
> > 
> > Asterisk-Users mailing list
> > To UNSUBSCRIBE or update options visit:
> >    http://lists.digium.com/mailman/listinfo/asterisk-users
> 
> I'd like to explain why we keep saying addons must be fixed. The way that
> modules are loaded in trunk is different then the way they were previously
> loaded in all other Asterisk versions. This change requires modifications to
> bring the module up to code with the loader. You can't just build and load
> any old module, it HAS to be updated. Trunk itself is not broken, all
> modules in the official source tree have been updated to the new loader
> standards. It does not generate incomplete/misconfigured headers - it
> generates headers for the new loader. Everyone understand?

Is there a documentation for that new loader?
>From what I see right now, all modules needs the inclusion of 
  include/autoconfig.h
but this file is not present when asterisk has been installed together with
all other header files. This file is available in the asterisk configured
source tree only.
Will that be changed? I assume yes, because otherwise the installation of
all asterisk header files would be useless.

I want to adapt chan-capi then as well (as soon as possible), so what would 
you suggest to do? Wait more time? Or is there something I already can 
use/do?

Armin