Build the ttcn3 testsuites inside docker, so there is no mismatch of
libraries between the host system and the docker container when
attempting to run the testsuite inside docker later (like jenkins does
Allow calling gen_makefile.py with --jobs without any argument, and
behave the same as if --jobs was not passed. This fixes calling
gen_makefile.py initially without --jobs, and then running "make regen"
which will cause gen_makefile.py to get called with --jobs with no
The testsuite is running in bullseye for some time, so build the Osmocom
programs in bullseye as well.
Depends: docker-playground I4cd05ef2c164dfb765ee365ab38b8dfd4f955ac6
Renamming the make_to_src_proj variable to src_proj in commit
93bd52300e leads to the build_to_src variable
being the result of a double call to os.path.relpath(), breaking builds when using
non absolute path for make_dir
For some reason, on Arch Linux:
$ file /bin/sh
/bin/sh: symbolic link to bash
$ sh --version
GNU bash, version 5.1.16(1)-release (x86_64-pc-linux-gnu)
the '--trx' arguments are getting passed incorrectly:
$ ./fake_trx.py TRX1@127.0.0.1:5700/1
fake_trx: error: unrecognized arguments: TRX1@127.0.0.1:5700/1
Let's send each argument separately.
With most recent OsmoBSCNAT patches, the addresses from the connecting
BSCs get used, no need to hardcode them in the config anymore.
Depends: osmo-bsc-nat I1556aa665fbb0a97507f98794e74820731fa6935
Instead of hardcoding wrappers such as gdb for various commands in
run.sh, put all commands into a config file so the user can add
gdb/valgrind/strace/udtrace/... to the program they are currently
interested in debugging in their own config.
Make it easier for the user to follow a consistent naming scheme for the
log files if they want do do so, by displaying the last log name.
enter name to save log (last: 2022-03-07_04-test-log-name):
Prepare to add another MGW for the BSCNAT. Use only one variable for the
mgw, always append the -c configfile parameter further below in the
script where it gets used.
osmo-gbproxy is not part of any of the convenience make targets in
gen_makefile.py (cn, cn-bsc, usrp). When using the typical workflow of
building one of these convenience targets first, then attempting to run
the network, the osmo-gbproxy window just says command not found.
With the default config_2g3g, it is not needed when only using one BTS,
so add a new config variable GBPROXY_RUN_IN_OSMO_DEV=0 and use it in