diff options
author | Pau Espin Pedrol <pespin@sysmocom.de> | 2024-04-26 18:04:20 +0200 |
---|---|---|
committer | Pau Espin Pedrol <pespin@sysmocom.de> | 2024-04-26 18:13:13 +0200 |
commit | fdef271404312ed08c4d0d95c328bbab51fc39fa (patch) | |
tree | bc66ab7e6d7b4c3dd82cc7e417952d9f7e291639 /ttcn3-mgw-test/osmo-mgw.cfg | |
parent | 3b535cbafaf4845147fe1babd64f455b746e3dd4 (diff) |
By default, asterisk.git build system will fetch pjproject tarball from
https://raw.githubusercontent.com/asterisk/third-party/master/pjproject/$(PJPROJECT_VERSION),
where PJPROJECT_VERSION is defined in asterisk/third-party/versions.mak:
PJPROJECT_VERSION=2.14
On top of that, it applies some patches adapting build system, found in
asterisk/third-party/pjproject/patches/.
The build system also allows to use an out-of-tree pjproject (eg from a
git repo) by symlinking the directory to
asterisk/third-party/pjprojec/source/.
This is all documented in asterisk/third-party/pjproject/README-hacking.md.
Since we want to develop on pjproject too, fetch our own pjproject.git
repo, where we can push changes, and build asterisk using that repo.
Bear in mind that, when asterisk.git builds with out-of-tree pjproject,
it wont apply pjproject patches under asterisk.git/third-party/pjproject/patches.
Hence, I created an "asterisk/2.14" branch in our pjproject.git repo which points
to tag "2.14" (the one used by asterisk 20.7.0, which we use), and has the 2 patches
applied on top.
Then, we have our own "sysmocom/2.14" branch on top of that "asterisk/2.14"
branch, where we put our development. WIP development can also be done in whatever
branch on top of "asterisk/2.14" branch.
Change-Id: I73f3323db1b6897fc43215578b0a011fdb6909c5
Diffstat (limited to 'ttcn3-mgw-test/osmo-mgw.cfg')
0 files changed, 0 insertions, 0 deletions