Build without this script, as it is being removed from osmo-ci.git in
favor of using ccache. See Id94d6126b476077d57839e4a884621b8c034f0c6
for reasoning.
Related: OS#5848
Change-Id: Ib3272feec76b30412ca60dec204255b64e33831b
There's optional libiu for Iu*S support but it's just a leftover from
pre repo-split times:
* it's not used by any code
* it's not checked by gerrit verification in osmo-ci
* it's disabled by default
* it's not supported in .deb packages
Instead of dragging old code in unknown stage of bit-rotting, let's just
drop it completely.
Change-Id: Id5678a74504b4456aba0438ccc34731770801128
Add new environment variables WITH_MANUALS and PUBLISH to control if
the manuals should be built and uploaded. Describe all environment vars
on top of the file.
Related: OS#3385
Change-Id: I89be11d346d50169282c991235ffc47dacc30b11
See osmo-ci change I2409b2928b4d7ebbd6c005097d4ad7337307dd93 for rationale.
Depends: I2409b2928b4d7ebbd6c005097d4ad7337307dd93
Change-Id: Ibafac7c8a48f46237835e91c80e72543c6841d08
verify_value_string_arrays_are_terminated has recently been moved
from libosmocore.git to osmo-ci.git and the person doing this seems
to have forgotten to update openbsc.git
Change-Id: Ibe4a7f71d2557dfee94803e909dabb00d2ce10af
We are building with libosmo-sccp tag 'old_sua' until the new sigtran has
been applied. Since osmo-iuh commit
e26bc1855326399733ee78ac84c8d33319f36dfb
"move openbsc.git's iu.h, iu.c, iu_vty.c here as iu_client"
osmo-iuh requires libosmo-sccp master. A similar 'old_sua' tag is in place in
osmo-iuh.git, to match libosmo-sccp 'old_sua'. Do that to fix the jenkins
build of --enable-iu.
Change-Id: I7c98b8bb1027fe8b47d8dcc4e0b94c1b42e44c52
Have a bash function to build each dependency with the same commands. There is
a tradeoff: having each dependency build with the same function means you can't
easily tweak one of the dependencies. OTOH having a unified function means a)
more readable script, b) that we're sure not to forget some steps and c) no
need to do the same edit n times.
Set the PKG_CONFIG_PATH globally. Also a tradeoff: if a future addition
wouldn't need the same PKG_CONFIG_PATH, this would make things ugly. But that
is actually quite unlikely, and the readability improvement is substantial.
Use env variables to remember local paths. That means we always are sure to cd
to the same absolute base path, which a 'cd ..' can't guarantee; also, we avoid
possible typos for e.g. "$deps/install".
Change-Id: Ib23f86c6cc1441d882de59bcdde5de87fa4e9fdf