aboutsummaryrefslogtreecommitdiffstats
path: root/configure.ac
AgeCommit message (Collapse)AuthorFilesLines
2019-01-20Bump version: 0.10.0.39-b723 → 1.0.01.0.0Harald Welte1-4/+4
Change-Id: I9b9d9331bdd1d9cdebdef5c3e0c49a1b18972abd
2018-11-27build manuals moved here from osmo-gsm-manuals.gitOliver Smith1-0/+43
Moved to doc/manuals/, with full commit history, in preceding merge commit. Now incorporate in the build system. Build with: $ autoreconf -fi $ ./configure --enable-manuals $ make Shared files from osmo-gsm-manuals.git are found automatically if - the repository is checked out in ../osmo-gsm-manuals; or - if it osmo-gsm-manuals was installed with "make install"; or - OSMO_GSM_MANUALS_DIR is set. Related: OS#3385 Change-Id: Ib5a22c2ea81fdde036bf9efb47d785a830b88c93
2018-10-21build: move include/{mtp,sccp} to include/osmocom/Neels Hofmeyr1-2/+2
Anywhere else in the Osmocom code base, we arrange headers in include/osmocom/foo/ and pass -I ${root_srcdir}/include/. This way including an osmocom header always has the format #include <osmocom/foo/bar.h> whether we are including from the local source tree or from $prefix. For some reason not clear to me, the mtp and sccp folders, even though they are being installed to $prefix/include/osmocom/, were kept *next* to the osmocom/ dir, instead of inside it. Fix that weird situation. The motivation is that I wanted to use a definition from sccp_types.h in a public-API header. That is impossible if it requires #include <sccp/sccp_types.h> in a local build, but #include <osmocom/sccp/sccp_types.h> for any other source tree using libosmo-sccp. After this patch, both are identical and including works without quirks. (The other patch that needed this has changed in the meantime on and no longer needs this, but this still makes sense for future hacking.) The installed result does not change, since both mtp/*.h and sccp/*.h have always been installed to $prefix/include/osmocom/{mtp,sccp}/. This merely changes their position in the source tree. The most curious situation before this is that any patch #including <osmocom/sccp/sccp_types.h> might not get a notice that the header didn't exist, but might instead include an older system-installed file. Change-Id: I1209a4ecf9f692a8030b5c93cd281fc9dd58d105
2018-09-27add tests/vty: VTY UI transcript testingNeels Hofmeyr1-0/+16
Add ss7_asp_vty_test, a shim test program with the sole purpose of exposing the cs7 VTY nodes. Add ss7_asp_test.vty, transcript for verifying VTY nodes using above program. Add --enable-external-tests to configure. Run jenkins.sh with --enable-external-tests. Change-Id: I6a28684fa24d6e7de568623444297028eba2ab8c
2018-09-10Install systemd services with autotoolsPau Espin Pedrol1-0/+17
This commit re-adds ba3da6d72564bb2c60f4f4a8d641b8a7b86d1f59, plus fixes two typos (sytemd->systemd) in that commit. The commit is fine, we just need to add some extra configure flags in osmo-ci.git. Depends: https://gerrit.osmocom.org/#/c/osmo-ci/+/10857/ Change-Id: Ifc11d97c0c5fe1f7872b59147b1548b56951921b
2018-09-09Revert "Install systemd services with autotools"Harald Welte1-17/+0
This reverts commit ba3da6d72564bb2c60f4f4a8d641b8a7b86d1f59. That commit broke master-{osmo-iuh,osmo-msc,osmo-sgsn,openbsc,osmo-bsc} build jobs with make[4]: Nothing to be done for 'install-exec-am'. /bin/mkdir -p '/lib/systemd/system' /usr/bin/install -c -m 644 osmo-stp.service '/lib/systemd/system' /usr/bin/install: cannot create regular file '/lib/systemd/system/osmo-stp.service': Permission denied make[4]: *** [install-systemdsystemunitDATA] Error 1 Change-Id: I009825d293e7e7a6c48d10452c10b3bb6da3e684
2018-09-07Install systemd services with autotoolsPau Espin Pedrol1-0/+17
Change-Id: Ie77ee4b32a75e2d207030ddc78d39fb664103d33
2018-07-27Bump version: 0.9.0.20-6265-dirty → 0.10.00.10.0Pau Espin Pedrol1-4/+4
Change-Id: Ia087b9f03a73a08f0eaa461f61c6244aaf13e3d4
2018-07-02build: Install example cfg filesPau Espin Pedrol1-0/+2
Change-Id: I93b73032b9a01a1e121ecf7c0cfcf3d5558efc7f
2018-05-03Bump version: 0.8.1.43-7e34-dirty → 0.9.00.9.0Pau Espin Pedrol1-4/+4
Change-Id: Ie3d11408f35509138475e7edde285e1bf5bef8e0
2018-03-05configure: add --enable-werrorNeels Hofmeyr1-0/+21
Provide a sane means of adding the -Werror compiler flag. Currently, some of our jenkins.sh add -Werror by passing 'CFLAGS="-Werror"', but that actually *overwrites* all the other CFLAGS we might want to have set. Maintain these exceptions from -Werror: a) deprecation (allow upstream to mark deprecation without breaking builds); b) "#warning" pragmas (allow to remind ourselves of errors without breaking builds) As a last configure step before generating the output files, print the complete CFLAGS and CPPFLAGS by means of AC_MSG_RESULT. Change-Id: Idb579d546d6f228e86bd49ca15aa87b86978205a
2018-02-10build: AC_PROG_LIBTOOL is the same as LT_INITMartin Hauke1-1/+0
Change-Id: I30f8d289d9dca892e40cd7ed787029fbcafa2dff
2017-11-18add --enable-sanitize config optionNeels Hofmeyr1-0/+12
Change-Id: Ie9bf734cb6cdee24e776cd64f9f1b800a7a9277c
2017-10-27update libosmocore/libosmo-netif dependency to current versionsHarald Welte1-4/+4
Change-Id: I084b5968dec97b0bba0344425f880077ddada440
2017-10-18Add doxygen docsMax1-0/+10
Make sure doxygen generates library documentation by default (can be disabled at compile time). Change-Id: I2bf7438bcdde19dc88b9bc14c8ad9c8f49099f8a Related: OS#2572
2017-08-29Use release helper from libosmocoreMax1-0/+4
See https://osmocom.org/projects/cellular-infrastructure/wiki/Make_a_new_release for details. Change-Id: I39b3bfa8a1ccf376215a3ce220cb3cf7a85471cb Related: OS#1861
2017-07-08contrib: Enable -Werror by defaultPau Espin Pedrol1-1/+1
Change-Id: I16a8ca7f0bfabeed6a9b58cda5e60bd58889f74d
2017-07-08configure.ac: Fix C(PP)FLAGS for BSD buildPau Espin Pedrol1-2/+2
Issue first found in libosmocore. It seems the BSD build doesn't use bash which means using += to append to a variable doesn't work correctly. Change-Id: I33f6b9de4990de0c4d3a6fc0bd7df632094e79ac
2017-06-22Revert "configure.ac: Use -Werror in C(PP)FLAGS"Neels Hofmeyr1-2/+2
As discussed in chat, -Werror should not be enabled by default. Instead it should be added in our jenkins build scripts. This reverts commit fc252ca38427bf77e55fd272a954dfe24f03a719. Change-Id: I92955c2f74f9a5c40e80028459100cf5e79a537b
2017-06-22configure.ac: Use -Werror in C(PP)FLAGSPau Espin Pedrol1-2/+2
Change-Id: Ia753a3080ef54ac248dacce5cd692fdd38f7649a
2017-06-22configure.ac: Use -Wall in C(PP)FLAGSPau Espin Pedrol1-1/+3
Change-Id: I1e49427b8267bbdb05d0121971a56359dbecd690
2017-04-25Fix debian buildsMax1-0/+1
Add missing libosmogsm dependency. Change-Id: I6e5cf393ffe81c582966ca0e9479e6deeffa9280 Fixes: OS#2182
2017-04-13Add osmo-stp executable as new "Osmocom Signaling Transfer Point"Harald Welte1-0/+1
osmo-stp is able to define multiple M3UA and/or SUA application servers (AS) as well as application server processes (ASPs). Clients can then connect via M3UA or SUA, perform the respective ASPSM / ASPTM state changes and finally exchange MTP signaling such as ISUP or SCCP on top of it. Routing is currently only based on point codes (PC). Routing table is fully configurable with Destination PC and mask. Shortcomings: * xUA: only "override" traffic mode supported, no load-balance or broadcast * xUA: no SNM supported, i.e. DAVA/DUNA/... messages are neither parsed nor generated * SCCP: no Global Title based Routing (GTR) yet * SCCP: no Global Title Translation (GTT) yet * no M2PA / M2UA sigtran dialects * no classic CS7 based signaling links(E1/T1 TDM) Change-Id: If32227b8d3127c6178e4ee45527ce65f69bc7b1e
2017-04-10Add example program how to use M3UA+SCCP client and serverHarald Welte1-0/+2
This is an example tool that can be run either as server (SG) or as client (ASP) with a SCCP+M3UA stacking, and communicate via connectionless and connection-oriented primitives over it Change-Id: Id698ce2da5726e304dfa1773b794671dc80d853c
2017-04-10remove tests/sigtran: it's not a test caseHarald Welte1-1/+0
in tests/* we have unit tests that are run as part of the autotest suite during 'make check'. The code in tests/sigtran is an example, but not a test. As the API is changing anyway, let's remove it for now and re-introduce actual tests and examples after the changes in API required by the upcoming new SCCP core. Change-Id: Ie471a197856c875eb4987bf9858d757312de24fb
2017-04-10Add tests for xUA code + SCCP/SUA transcodingHarald Welte1-0/+1
Change-Id: I7ce038d72dca18fb83d5a12519c9a48267e52ab8
2017-04-10Add new 'osmo_ss7' SS7 core code with M3UA, ASP/AS FSM, ...Harald Welte1-0/+12
This is what aims to be a rather complete/proper implementation of the SIGTRAN + SS7 protocol suite. It has proper abstraction between the layers with primitives, finite state machines for things like the AS and ASP state machines, support for point code routing, etc. What's not implemented at this point: * re-integration of pre-existing SUA (pending) * actual MTP2 and physical E1/T1 link support * different trafic modes like broadcast/fail-over/load-balance Change-Id: I375eb80f01acc013094851d91d1d3333ebc12bc7
2016-11-03Add missing xua.pc fileArran Cudbard-Bell1-0/+1
Change-Id: I5081799e1d7c7f5f3206e5f38060540bb4e3289b Signed-off-by: Arran Cudbard-Bell <a.cudbardb@freeradius.org>
2016-10-01configure: check for pkg-config presenceNeels Hofmeyr1-0/+7
Change-Id: I0066b33ce59d1e107ca8e7389599b232a033ba2e
2016-10-01build: be robust against install-sh files above the root dirNeels Hofmeyr1-0/+3
Explicitly set AC_CONFIG_AUX_DIR. To reproduce the error avoided by this patch: rm install-sh # in case it was already generated. touch ../install-sh # yes, outside this source tree autoreconf -fi This will produce an error like ... configure.ac:16: error: required file '../ltmain.sh' not found configure.ac:5: installing '../missing' src/Makefile.am: installing '../depcomp' autoreconf: automake failed with exit status: 1 See also automake (vim `which automake`) and look for 'sub locate_aux_dir'. Change-Id: Iec88e41c1fe80b436d6d08005871bead540e387d
2016-01-06Fix required version of libosmo-netifMax1-1/+1
Sponsored-by: On-Waves ehf Signed-off-by: Max <msuraev@sysmocom.de>
2015-12-22Add some SUA client and server example codeHarald Welte1-0/+1
2015-12-22libosmo-sigtran: Add pkg-config integrationHarald Welte1-0/+1
2015-12-22Import SUA (SCCP User Adaptation) and SCCP User SAPHarald Welte1-2/+5
... this code originates from the osmo-iuh repository, but is now part of a new shared libosmo-sigtran.so library generated in this repository.
2015-03-23XUA: Move m2ua headers to sigtran, create xua_types.h and m3ua_types.hHolger Hans Peter Freyther1-1/+1
Begin with type definitions for m3ua
2012-03-26misc: Fix the email address in the configure.acHolger Hans Peter Freyther1-1/+1
2011-11-20tests: Run the existing tests with GNU AutotestHolger Hans Peter Freyther1-0/+1
SCCP: Use DST/SRC Ref instead of the pointer value to create stable releases.
2011-05-24libosmo-sccp: add missing AC_LANG_SOURCE for current autoconfAlexander Huemer1-1/+1
autoconf >=2.68 demands the body of an AC_COMPILE_IFELSE to be wrapped in an AC_LANG_SOURCE macro, otherwise outputs annoying warnings on the invocation of `autoreconf -i`. this patch follows that demand.
2011-05-08namespace: use osmo_static_assert() instead of static_assert()Harald Welte1-1/+1
2011-03-23Update include paths with libosmocore 0.2.00.0.5Harald Welte1-1/+1
2011-01-12m2ua: Add parsing and creation of m2ua packagesHolger Hans Peter Freyther1-0/+1
2011-01-12m2ua: Add basic header file for the common structure of a M2UA msgHolger Hans Peter Freyther1-0/+1
2010-08-01mtp: Add the MTP Level3 code to the SCCP repoistoryHolger Hans Peter Freyther1-0/+3
SCCP can be wrapped inside the MTP Level3, and one can use it for link testing as well. This repository should be renamed to libosmo-itu or libosmo-ss7 and be a host to SS7 related encapsulation... The code is coming from the cellmgr-ng code.
2010-07-30sccp: Rename the pkg-config file to osmo-sccp0.0.1Holger Hans Peter Freyther1-1/+1
2010-07-30sccp: Add a new buildsystem for the OSMO SCCP libraryHolger Hans Peter Freyther1-0/+38
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-03 03:53:32 +0000