[asterisk-dev] Asterisk now available with bundled pjproject!

Ross Beer ross.beer at outlook.com
Wed Mar 16 06:41:14 CDT 2016

I just attempted to install with the bundled pjproject however the following error stopped the build:
Generating embedded module rules ...
   [CC] astdb2sqlite3.c -> astdb2sqlite3.o
   [LD] astdb2sqlite3.o db1-ast/libdb1.a -> astdb2sqlite3
   [CC] astdb2bdb.c -> astdb2bdb.o
   [LD] astdb2bdb.o db1-ast/libdb1.a -> astdb2bdb
[pjproject]  Making dependencies
[pjproject]  Compiling libs
[pjproject]  Generating symbols
[pjproject]  Compiling apps
[pjproject]  Compiling python bindings
make[2]: *** [source/pjsip-apps/src/python/build/_pjsua.so] Error 1
make[1]: *** [pjproject] Error 2
make: *** [third-party] Error 2

Kind regards,
From: george.joseph at fairview5.com
Date: Mon, 7 Mar 2016 12:28:23 -0700
To: asterisk-dev at lists.digium.com; asterisk-users at lists.digium.com
Subject: [asterisk-dev] Asterisk now available with bundled pjproject!

The current Asterisk 13 and master git branches have a new feature that will be included in 13.8.0:  The ability to compile and run Asterisk with a bundled version of pjproject.
Why would you want to do this?  Several reasons:
Predictability:  When built with the ​bundled pjproject, you're always certain of the version you're running against, no matter where it's installed.
Scalability:  The default pjproject configuration is optimized for client applications. The bundled version's configuration is optimized for server use.
Usability:  Several feature patches, which have been submitted upstream to pjproject but not yet released, have been included in the bundled version.
Safety:  If a security or critical issue is identified in pjproject, it can be patched and made available with a new release of Asterisk instead of ​having to ​waiting for a new release of pjproject​​.Maintainability:  You don't need to build and install separate packages.
Supportability:  When asking others for help, there's no question about which version of pjproject you're using and what options it was compiled with.
Compatibility:  This is especially important from a development perspective because it means we can be sure that new pjproject APIs that have been introduced​,​ or old ones that have been deprecated​,​ are handled and tested appropriately in Asterisk.
Reliability:  You can be sure that Asterisk was tested against the bundled version.

So now that you're sold, here's how you use it:

All you have to do is add the "--with-pjproject-bundled" option to your ./configure command line and remove any other "--with-pjproject" option you may have specified.  The configure and make processes will download the correct version of pjproject, patch it, configure it, build it and finally link Asterisk to it statically.  No changes in runtime configuration are required.

Still not sold?  The default behavior hasn't changed so as long as you haven't specified "--with-pjproject-bundled", your build and deploy process remains as is.

PLEASE TRY THIS!!  I'd love some feedback BEFORE 13.8.0 is released.

-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20160316/a27317dc/attachment.html>

More information about the asterisk-dev mailing list