2017-08-25 15:53:00 +00:00
|
|
|
#!/bin/sh
|
2016-04-27 20:06:46 +00:00
|
|
|
|
|
|
|
|
set -ex
|
|
|
|
|
|
jenkins.sh: fix, remove code dup
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".
Build sysmocom/sctp branch of libosmo-netif, as needed for libosmo-sccp's
sysmocom/iu branch.
Build aper-prefix branch of asn1c, as needed by 'regen'.
'make regen' first, to generate the .c from asn1, needed by the build.
Change-Id: Ia7b4b9788b9c951f8be00cc5ae72a9c0a776fe64
2016-07-11 15:10:49 +00:00
|
|
|
base="$PWD"
|
|
|
|
|
deps="$base/deps"
|
|
|
|
|
inst="$deps/install"
|
2016-10-06 23:17:20 +00:00
|
|
|
export deps inst
|
jenkins.sh: fix, remove code dup
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".
Build sysmocom/sctp branch of libosmo-netif, as needed for libosmo-sccp's
sysmocom/iu branch.
Build aper-prefix branch of asn1c, as needed by 'regen'.
'make regen' first, to generate the .c from asn1, needed by the build.
Change-Id: Ia7b4b9788b9c951f8be00cc5ae72a9c0a776fe64
2016-07-11 15:10:49 +00:00
|
|
|
|
2017-10-27 20:54:35 +00:00
|
|
|
osmo-clean-workspace.sh
|
|
|
|
|
|
jenkins.sh: fix, remove code dup
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".
Build sysmocom/sctp branch of libosmo-netif, as needed for libosmo-sccp's
sysmocom/iu branch.
Build aper-prefix branch of asn1c, as needed by 'regen'.
'make regen' first, to generate the .c from asn1, needed by the build.
Change-Id: Ia7b4b9788b9c951f8be00cc5ae72a9c0a776fe64
2016-07-11 15:10:49 +00:00
|
|
|
mkdir "$deps" || true
|
|
|
|
|
|
2017-08-25 15:53:00 +00:00
|
|
|
verify_value_string_arrays_are_terminated.py $(find . -name "*.[hc]")
|
2017-03-01 14:44:57 +00:00
|
|
|
|
jenkins.sh: fix, remove code dup
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".
Build sysmocom/sctp branch of libosmo-netif, as needed for libosmo-sccp's
sysmocom/iu branch.
Build aper-prefix branch of asn1c, as needed by 'regen'.
'make regen' first, to generate the .c from asn1, needed by the build.
Change-Id: Ia7b4b9788b9c951f8be00cc5ae72a9c0a776fe64
2016-07-11 15:10:49 +00:00
|
|
|
export PKG_CONFIG_PATH="$inst/lib/pkgconfig:$PKG_CONFIG_PATH"
|
2016-10-06 23:17:20 +00:00
|
|
|
export LD_LIBRARY_PATH="$inst/lib"
|
2019-07-30 07:24:04 +00:00
|
|
|
export PATH="$inst/bin:$PATH"
|
jenkins.sh: fix, remove code dup
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".
Build sysmocom/sctp branch of libosmo-netif, as needed for libosmo-sccp's
sysmocom/iu branch.
Build aper-prefix branch of asn1c, as needed by 'regen'.
'make regen' first, to generate the .c from asn1, needed by the build.
Change-Id: Ia7b4b9788b9c951f8be00cc5ae72a9c0a776fe64
2016-07-11 15:10:49 +00:00
|
|
|
|
2018-02-20 19:22:24 +00:00
|
|
|
osmo-build-dep.sh libosmocore "" --disable-doxygen
|
2016-10-06 23:17:20 +00:00
|
|
|
osmo-build-dep.sh libosmo-abis
|
2017-07-05 10:52:01 +00:00
|
|
|
osmo-build-dep.sh libosmo-netif
|
migrate osmo-hnbgw to libosmo-sigtran's SCCP/M3UA
libosmo-sigtran now has a "proper" SCCP/M3UA stack, so we can make our hnb-gw
3GPP compliant by switching from the old SUA code to the new universal SCCP
user API with support for (currently) M3UA and SUA.
Main changes:
Use one cn_link to STP: We will connect to the core network using an (Osmo)STP
instance that routes to MSC and SGSN, so we want one SCCP link instead of two.
The only difference between IuCS and IuPS is a different remote osmo_sccp_addr.
This has various effects through the messaging code; the patch is a bit larger
than I would like, but it is hard to separate out truly independent smaller
changes.
CS or PS domain was previously flagged in the separate cn_link, as ctx pointer
for two separate sccp_sap_up()s. Now there's just one such ctx, so determine
is_ps from the RANAP Domain Indicator, or from the conn's hnbgw_context_map:
- Add is_ps to context_map_alloc_by_hnb().
- To find a matching context, the RUA ID alone is no longer sufficient, also
match is_ps (possible optimization todo: separate lists).
We would send separate CS or PS Reset messages based on the cn_link, instead
send both CS and PS Reset at the same time for the single cn_link. This could
be adjusted to detect presence of MSC or SGSN instead.
Pending: adjust the VTY config to reflect that there is only one remote
address. Place a TODO comment for that.
Smaller changes:
rua_to_scu(): populate called and calling addresses for N_CONNECT and
N_UNITDATA.
Remove DSUA.
Don't build dummy_cn, which is still implemented on SUA. Mark todo to maybe
re-include it based on M3UA later.
In hnbgw_cnlink, place sccp related items in a separate sub-struct.
Do not keep an llist of cn_links, just have the one. Remove iteration and list
management.
Change jenkins script to build libosmo-sccp master.
Patch-by: hwelte, nhofmeyr
Change-Id: I8ac15fa2fd25bedb26297177e416976a5389b573
2017-07-03 14:49:43 +00:00
|
|
|
osmo-build-dep.sh libosmo-sccp
|
2016-10-06 23:17:20 +00:00
|
|
|
osmo-build-dep.sh libasn1c
|
jenkins.sh: fix, remove code dup
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".
Build sysmocom/sctp branch of libosmo-netif, as needed for libosmo-sccp's
sysmocom/iu branch.
Build aper-prefix branch of asn1c, as needed by 'regen'.
'make regen' first, to generate the .c from asn1, needed by the build.
Change-Id: Ia7b4b9788b9c951f8be00cc5ae72a9c0a776fe64
2016-07-11 15:10:49 +00:00
|
|
|
|
|
|
|
|
# the asn1c binary is used by the 'regen' target below
|
2016-10-06 23:17:20 +00:00
|
|
|
osmo-build-dep.sh asn1c aper-prefix
|
jenkins.sh: fix, remove code dup
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".
Build sysmocom/sctp branch of libosmo-netif, as needed for libosmo-sccp's
sysmocom/iu branch.
Build aper-prefix branch of asn1c, as needed by 'regen'.
'make regen' first, to generate the .c from asn1, needed by the build.
Change-Id: Ia7b4b9788b9c951f8be00cc5ae72a9c0a776fe64
2016-07-11 15:10:49 +00:00
|
|
|
|
2019-07-30 07:24:04 +00:00
|
|
|
CONFIG=""
|
|
|
|
|
if [ "$WITH_MANUALS" = "1" ]; then
|
|
|
|
|
CONFIG="--enable-manuals"
|
|
|
|
|
fi
|
|
|
|
|
|
2016-10-06 23:17:20 +00:00
|
|
|
set +x
|
|
|
|
|
echo
|
|
|
|
|
echo
|
|
|
|
|
echo
|
|
|
|
|
echo " =============================== osmo-iuh ==============================="
|
|
|
|
|
echo
|
|
|
|
|
set -x
|
2016-07-11 19:56:15 +00:00
|
|
|
|
2016-04-27 20:06:46 +00:00
|
|
|
autoreconf --install --force
|
2019-07-30 07:24:04 +00:00
|
|
|
./configure --enable-sanitize $CONFIG
|
2016-08-29 13:50:14 +00:00
|
|
|
|
|
|
|
|
# Verify that checked-in asn1 code is identical to regenerated asn1 code
|
jenkins.sh: fix, remove code dup
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".
Build sysmocom/sctp branch of libosmo-netif, as needed for libosmo-sccp's
sysmocom/iu branch.
Build aper-prefix branch of asn1c, as needed by 'regen'.
'make regen' first, to generate the .c from asn1, needed by the build.
Change-Id: Ia7b4b9788b9c951f8be00cc5ae72a9c0a776fe64
2016-07-11 15:10:49 +00:00
|
|
|
PATH="$inst/bin:$PATH" $MAKE $PARALLEL_MAKE -C src regen
|
2016-08-29 13:50:14 +00:00
|
|
|
|
|
|
|
|
# attempt to settle the file system
|
|
|
|
|
sleep 1
|
|
|
|
|
|
|
|
|
|
git status
|
|
|
|
|
git diff | cat
|
|
|
|
|
|
|
|
|
|
if ! git diff-files --quiet ; then
|
|
|
|
|
echo "ERROR: 'make -C src regen' does not match committed asn1 code"
|
|
|
|
|
exit 1
|
|
|
|
|
fi
|
|
|
|
|
|
jenkins.sh: fix, remove code dup
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".
Build sysmocom/sctp branch of libosmo-netif, as needed for libosmo-sccp's
sysmocom/iu branch.
Build aper-prefix branch of asn1c, as needed by 'regen'.
'make regen' first, to generate the .c from asn1, needed by the build.
Change-Id: Ia7b4b9788b9c951f8be00cc5ae72a9c0a776fe64
2016-07-11 15:10:49 +00:00
|
|
|
$MAKE $PARALLEL_MAKE
|
2016-10-06 23:17:20 +00:00
|
|
|
$MAKE check \
|
2016-09-21 22:33:50 +00:00
|
|
|
|| cat-testlogs.sh
|
2020-10-12 17:26:08 +00:00
|
|
|
$MAKE $PARALLEL_MAKE distcheck \
|
2016-09-21 22:33:50 +00:00
|
|
|
|| cat-testlogs.sh
|
2017-10-27 20:54:35 +00:00
|
|
|
|
2020-10-12 17:26:08 +00:00
|
|
|
$MAKE $PARALLEL_MAKE maintainer-clean
|
2017-10-27 20:54:35 +00:00
|
|
|
osmo-clean-workspace.sh
|
