Age | Commit message (Collapse) | Author | Files | Lines |
|
libosmo-sccp master is moving ahead, openbsc --enable-iu needs an older
version.
Change-Id: Id74a802fd2ca65f4b6c2079550fbb6b0af3e8340
|
|
The iu specific branches of libosmo-sccp and libosmo-netif have recently
been merged to master.
Change-Id: I9465d7b956c3bd65d6e8a387e6710235672352e8
|
|
Depends: libosmocore change-id I2bc93ab4781487e7685cfb63091a489cd126b1a8
Change-Id: I4183415cd1ead9d46ae3a556e94243325ef5a844
|
|
Like in libosmo-abis' jenkins.sh
Change-Id: I4d6ffd5b230dd095650cc2231678b66056a8e4b5
|
|
We do not want to see doxygen warnings when building the
libosmocore dependency.
Change-Id: I4640cb5b91d54641e8e5b2f096c3bca49bfff60e
|
|
Change-Id: Ida76f24d0b801fa609f3a128b3b912572cad4297
|
|
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
|
|
This can be used to replicate a build issue more easily.
|