[asterisk-bugs] [JIRA] (ASTERISK-28837) pjproject_bundled: Honor --without-pjproject.

[Asterisk Team (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-28837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=251002#comment-251002 ] 

Asterisk Team commented on ASTERISK-28837:
------------------------------------------

This issue has been reopened as a result of your commenting on it as the reporter. It will be triaged once again as applicable.

> pjproject_bundled: Honor --without-pjproject.
> ---------------------------------------------
>
>                 Key: ASTERISK-28837
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28837
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/BuildSystem, pjproject/pjsip
>    Affects Versions: 16.9.0, 17.3.0
>            Reporter: Alexander Traud
>            Assignee: Alexander Traud
>              Labels: patch
>      Target Release: 13.33.0, 16.10.0, 17.4.0
>
>         Attachments: without_pjproject.patch
>
>
> Let us assume, you do not want any PJProject in your Asterisk. For example, I have given up with the PJProject completely. I do not want it. In that case, you go for {{./configure --without-pjproject-bundled}} normally. That is the internal PJProject. However, let us assume your system offers a PJProject already, why ever. That is an external PJProject. To cover that case, you go for {{./configure --without-pjproject --without-pjproject-bundled}}. However, that is not allowed by the Asterisk team and the scripts errors. OK, let us go for {{./configure --without-pjproject}}. With that, the script succeeds but still downloads the internal PJProject …
> This issue affects only Asterisk 16 LTS and newer because only since then the bundled PJProject is downloaded on default. However, to keep the code in-line and to avoid different patches (merge conflicts) with the different branches, I apply this to Asterisk 13 LTS as well. Although there, this change has not effect.
> By the way, the same does not apply for the bundled Jansson, even if that changes its default one day: Jansson is a required library and cannot be disabled.



--
This message was sent by Atlassian JIRA
(v6.2#6252)