2017-03-07 23:06:40 +00:00
|
|
|
BUILT_SOURCES = osmocom/gsm/gsm0503.h
|
|
|
|
|
2012-06-29 20:01:19 +00:00
|
|
|
nobase_include_HEADERS = \
|
2017-12-15 20:42:15 +00:00
|
|
|
osmocom/codec/ecu.h \
|
2012-06-29 20:01:19 +00:00
|
|
|
osmocom/codec/codec.h \
|
2017-12-15 08:35:21 +00:00
|
|
|
osmocom/codec/gsm610_bits.h \
|
2012-06-29 20:01:19 +00:00
|
|
|
osmocom/core/application.h \
|
|
|
|
osmocom/core/backtrace.h \
|
2014-06-04 17:07:41 +00:00
|
|
|
osmocom/core/bit16gen.h \
|
|
|
|
osmocom/core/bit32gen.h \
|
|
|
|
osmocom/core/bit64gen.h \
|
2012-06-29 20:01:19 +00:00
|
|
|
osmocom/core/bits.h \
|
|
|
|
osmocom/core/bitvec.h \
|
2016-02-05 12:55:38 +00:00
|
|
|
osmocom/core/bitcomp.h \
|
2017-05-15 10:07:51 +00:00
|
|
|
osmocom/core/byteswap.h \
|
2012-06-29 20:01:19 +00:00
|
|
|
osmocom/core/conv.h \
|
2017-10-15 17:46:19 +00:00
|
|
|
osmocom/core/counter.h \
|
2012-06-29 20:01:19 +00:00
|
|
|
osmocom/core/crc16.h \
|
|
|
|
osmocom/core/crc16gen.h \
|
|
|
|
osmocom/core/crc32gen.h \
|
|
|
|
osmocom/core/crc64gen.h \
|
|
|
|
osmocom/core/crc8gen.h \
|
|
|
|
osmocom/core/crcgen.h \
|
2015-03-22 08:03:42 +00:00
|
|
|
osmocom/core/endian.h \
|
2013-08-14 10:26:27 +00:00
|
|
|
osmocom/core/defs.h \
|
2019-12-16 22:14:45 +00:00
|
|
|
osmocom/core/exec.h \
|
2016-05-29 01:53:17 +00:00
|
|
|
osmocom/core/fsm.h \
|
2012-06-29 20:01:19 +00:00
|
|
|
osmocom/core/gsmtap.h \
|
|
|
|
osmocom/core/gsmtap_util.h \
|
2018-05-11 15:39:21 +00:00
|
|
|
osmocom/core/isdnhdlc.h \
|
2012-06-29 20:01:19 +00:00
|
|
|
osmocom/core/linuxlist.h \
|
|
|
|
osmocom/core/linuxrbtree.h \
|
|
|
|
osmocom/core/logging.h \
|
2013-02-21 05:16:29 +00:00
|
|
|
osmocom/core/loggingrb.h \
|
2015-10-20 17:05:52 +00:00
|
|
|
osmocom/core/stats.h \
|
2014-08-18 17:03:40 +00:00
|
|
|
osmocom/core/macaddr.h \
|
2012-06-29 20:01:19 +00:00
|
|
|
osmocom/core/msgb.h \
|
|
|
|
osmocom/core/panic.h \
|
2017-06-18 15:16:02 +00:00
|
|
|
osmocom/core/prbs.h \
|
2012-06-29 20:01:19 +00:00
|
|
|
osmocom/core/prim.h \
|
|
|
|
osmocom/core/process.h \
|
|
|
|
osmocom/core/rate_ctr.h \
|
2015-10-01 18:43:53 +00:00
|
|
|
osmocom/core/stat_item.h \
|
2012-06-29 20:01:19 +00:00
|
|
|
osmocom/core/select.h \
|
2017-05-14 19:48:41 +00:00
|
|
|
osmocom/core/sercomm.h \
|
2012-06-29 20:01:19 +00:00
|
|
|
osmocom/core/signal.h \
|
|
|
|
osmocom/core/socket.h \
|
|
|
|
osmocom/core/statistics.h \
|
2013-02-21 05:16:29 +00:00
|
|
|
osmocom/core/strrb.h \
|
2015-11-20 23:41:43 +00:00
|
|
|
osmocom/core/talloc.h \
|
add osmo_tdef API, originally adopted from osmo-bsc T_def
Move T_def from osmo-bsc to libosmocore as osmo_tdef. Adjust naming to be more
consistent. Upgrade to first class API:
- add timer grouping
- add generic vty support
- add mising API doc
- add C test
- add VTY transcript tests, also as examples for using the API
From osmo_fsm_inst_state_chg() API doc, cross reference to osmo_tdef API.
The root reason for moving to libosmocore is that I want to use the
mgw_endpoint_fsm in osmo-msc for inter-MSC handover, and hence want to move the
FSM to libosmo-mgcp-client. This FSM uses the T_def from osmo-bsc. Though the
mgw_endpoint_fsm's use of T_def is minimal, I intend to use the osmo_tdef API
in osmo-msc (and probably elsewhere) as well. libosmocore is the most sensible
place for this.
osmo_tdef provides:
- a list of Tnnnn (GSM) timers with description, unit and default value.
- vty UI to allow users to configure non-default timeouts.
- API to tie T timers to osmo_fsm states and set them on state transitions.
- a few standard units (minute, second, millisecond) as well as a custom unit
(which relies on the timer's human readable description to indicate the
meaning of the value).
- conversion for standard units: for example, some GSM timers are defined in
minutes, while our FSM definitions need timeouts in seconds. Conversion is
for convenience only and can be easily avoided via the custom unit.
By keeping separate osmo_tdef arrays, several groups of timers can be kept
separately. The VTY tests in tests/tdef/ showcase different schemes:
- tests/vty/tdef_vty_test_config_root.c:
Keep several timer definitions in separately named groups: showcase the
osmo_tdef_vty_groups*() API. Each timer group exists exactly once.
- tests/vty/tdef_vty_test_config_subnode.c:
Keep a single list of timers without separate grouping.
Put this list on a specific subnode below the CONFIG_NODE.
There could be several separate subnodes with timers like this, i.e.
continuing from this example, sets timers could be separated by placing
timers in specific config subnodes instead of using the global group name.
- tests/vty/tdef_vty_test_dynamic.c:
Dynamically allocate timer definitions per each new created object.
Thus there can be an arbitrary number of independent timer definitions, one
per allocated object.
T_def was introduced during the recent osmo-bsc refactoring for inter-BSC
handover, and has proven useful:
- without osmo_tdef, each invocation of osmo_fsm_inst_state_chg() needs to be
programmed with the right timeout value, for all code paths that invoke this
state change. It is a likely source of errors to get one of them wrong. By
defining a T timer exactly for an FSM state, the caller can merely invoke the
state change and trust on the original state definition to apply the correct
timeout.
- it is helpful to have a standardized config file UI to provide user
configurable timeouts, instead of inventing new VTY commands for each
separate application of T timer numbers.
Change-Id: Ibd6b1ed7f1bd6e1f2e0fde53352055a4468f23e5
2019-01-26 19:36:12 +00:00
|
|
|
osmocom/core/tdef.h \
|
2012-06-29 20:01:19 +00:00
|
|
|
osmocom/core/timer.h \
|
2018-02-26 17:03:44 +00:00
|
|
|
osmocom/core/timer_compat.h \
|
2012-06-29 20:01:19 +00:00
|
|
|
osmocom/core/utils.h \
|
|
|
|
osmocom/core/write_queue.h \
|
2019-02-25 01:45:06 +00:00
|
|
|
osmocom/core/sockaddr_str.h \
|
2019-02-11 19:32:25 +00:00
|
|
|
osmocom/core/use_count.h \
|
2012-06-29 20:01:19 +00:00
|
|
|
osmocom/crypt/auth.h \
|
|
|
|
osmocom/crypt/gprs_cipher.h \
|
2014-08-20 17:58:40 +00:00
|
|
|
osmocom/ctrl/control_cmd.h \
|
|
|
|
osmocom/ctrl/control_if.h \
|
2014-08-21 10:17:11 +00:00
|
|
|
osmocom/ctrl/ports.h \
|
2012-06-29 20:01:19 +00:00
|
|
|
osmocom/gprs/gprs_bssgp.h \
|
2012-09-10 06:54:35 +00:00
|
|
|
osmocom/gprs/gprs_bssgp_bss.h \
|
2012-06-29 20:01:19 +00:00
|
|
|
osmocom/gprs/gprs_msgb.h \
|
|
|
|
osmocom/gprs/gprs_ns.h \
|
|
|
|
osmocom/gprs/gprs_ns_frgre.h \
|
2016-07-14 22:13:45 +00:00
|
|
|
osmocom/gprs/gprs_rlc.h \
|
2016-07-08 00:06:12 +00:00
|
|
|
osmocom/gprs/protocol/gsm_04_60.h \
|
2012-06-29 20:01:19 +00:00
|
|
|
osmocom/gprs/protocol/gsm_08_16.h \
|
|
|
|
osmocom/gprs/protocol/gsm_08_18.h \
|
|
|
|
osmocom/gsm/a5.h \
|
|
|
|
osmocom/gsm/abis_nm.h \
|
2014-10-01 08:18:11 +00:00
|
|
|
osmocom/gsm/apn.h \
|
2018-03-01 18:13:05 +00:00
|
|
|
osmocom/gsm/bts_features.h \
|
2019-05-03 07:39:10 +00:00
|
|
|
osmocom/gsm/cbsp.h \
|
2012-06-29 20:01:19 +00:00
|
|
|
osmocom/gsm/comp128.h \
|
2013-11-02 17:11:01 +00:00
|
|
|
osmocom/gsm/comp128v23.h \
|
2016-04-22 17:28:09 +00:00
|
|
|
osmocom/gsm/bitvec_gsm.h \
|
2012-06-29 20:01:19 +00:00
|
|
|
osmocom/gsm/gan.h \
|
2014-12-29 16:09:11 +00:00
|
|
|
osmocom/gsm/gsm0341.h \
|
2012-06-29 20:01:19 +00:00
|
|
|
osmocom/gsm/gsm0411_smc.h \
|
|
|
|
osmocom/gsm/gsm0411_smr.h \
|
|
|
|
osmocom/gsm/gsm0411_utils.h \
|
|
|
|
osmocom/gsm/gsm0480.h \
|
|
|
|
osmocom/gsm/gsm0502.h \
|
2016-04-29 11:17:22 +00:00
|
|
|
osmocom/gsm/gsm0503.h \
|
2016-09-22 18:48:59 +00:00
|
|
|
osmocom/coding/gsm0503_tables.h \
|
|
|
|
osmocom/coding/gsm0503_parity.h \
|
|
|
|
osmocom/coding/gsm0503_mapping.h \
|
|
|
|
osmocom/coding/gsm0503_interleaving.h \
|
|
|
|
osmocom/coding/gsm0503_coding.h \
|
2020-02-06 13:25:01 +00:00
|
|
|
osmocom/coding/gsm0503_amr_dtx.h \
|
2012-06-29 20:01:19 +00:00
|
|
|
osmocom/gsm/gsm0808.h \
|
2018-12-10 09:57:59 +00:00
|
|
|
osmocom/gsm/gsm29205.h \
|
2017-03-24 16:59:26 +00:00
|
|
|
osmocom/gsm/gsm0808_utils.h \
|
2016-05-11 07:13:08 +00:00
|
|
|
osmocom/gsm/gsm23003.h \
|
2020-05-11 17:43:20 +00:00
|
|
|
osmocom/gsm/gsm23236.h \
|
2018-12-07 11:31:08 +00:00
|
|
|
osmocom/gsm/gsm29118.h \
|
2012-06-29 20:01:19 +00:00
|
|
|
osmocom/gsm/gsm48.h \
|
2018-07-27 10:19:15 +00:00
|
|
|
osmocom/gsm/gsm48_arfcn_range_encode.h \
|
2012-06-29 20:01:19 +00:00
|
|
|
osmocom/gsm/gsm48_ie.h \
|
2018-07-27 13:17:09 +00:00
|
|
|
osmocom/gsm/gsm48_rest_octets.h \
|
2012-06-29 20:01:19 +00:00
|
|
|
osmocom/gsm/gsm_utils.h \
|
2016-04-25 16:46:22 +00:00
|
|
|
osmocom/gsm/gsup.h \
|
GSUP/SMS: introduce MO-/MT-FORWARD-SM messages
According to 3GPP TS 29.002, there are two services:
- MAP-MO-FORWARD-SHORT-MESSAGE (see 12.2),
- MAP-MT-FORWARD-SHORT-MESSAGE (see 12.9),
which are used to forward MO/MT short messages.
This change replicates both services as GSUP messages:
- OSMO_GSUP_MSGT_MO_FORWARD_SM_*,
- OSMO_GSUP_MSGT_MT_FORWARD_SM_*.
Please note, that only the 'must-have' IEs are introduced
by this change, in particular the following:
- OSMO_GSUP_SM_RP_MR_IE (see note below),
- OSMO_GSUP_SM_RP_DA_IE (see 7.6.8.1),
- OSMO_GSUP_SM_RP_OA_IE (see 7.6.8.2),
- OSMO_GSUP_SM_RP_UI_IE (see 7.6.8.4),
- OSMO_GSUP_SM_RP_MMS_IE (see 7.6.8.7),
- OSMO_GSUP_SM_RP_CAUSE_IE (see GSM TS 04.11, 8.2.5.4),
where both SM_RP_DA and SM_RP_OA IEs basically contain
a single nested TV of the following format:
- T: identity type (see 'osmo_gsup_sms_sm_rp_oda_t'),
- V: encoded identity itself (optional).
According to GSM TS 04.11, every single message on the SM-RL has
an unique message reference (see 8.2.3), that is used to link
an RP-ACK or RP-ERROR message to the associated (preceding)
RP-DATA or RP-SMMA message transfer attempt.
In case of TCAP/MAP, this message reference is being mapped to the
Invoke ID. But since GSUP has no 'Invoke ID' IE, and it is not
required for other applications (other than SMS), this change
introduces a special 'SM_RP_MR' IE that doesn't exist in MAP.
Change-Id: Ibe325c64ae2d6c626b232533bb4cbc65fc2b5d71
Related Change-Id: (docs) Ie0150756c33c1352bc4eb49421824542c711175c
Related Change-Id: (TTCN) Ibf49474a81235096c032ea21f217170f523bd94e
Related: OS#3587
2018-09-25 16:03:13 +00:00
|
|
|
osmocom/gsm/gsup_sms.h \
|
2020-05-14 09:42:53 +00:00
|
|
|
osmocom/gsm/i460_mux.h \
|
2014-08-20 20:28:23 +00:00
|
|
|
osmocom/gsm/ipa.h \
|
2012-06-29 20:01:19 +00:00
|
|
|
osmocom/gsm/lapd_core.h \
|
|
|
|
osmocom/gsm/lapdm.h \
|
2013-03-07 18:36:32 +00:00
|
|
|
osmocom/gsm/meas_rep.h \
|
2012-06-29 20:01:19 +00:00
|
|
|
osmocom/gsm/mncc.h \
|
|
|
|
osmocom/gsm/prim.h \
|
2013-02-07 11:18:37 +00:00
|
|
|
osmocom/gsm/l1sap.h \
|
2016-04-27 16:32:35 +00:00
|
|
|
osmocom/gsm/oap.h \
|
2018-07-30 10:04:21 +00:00
|
|
|
osmocom/gsm/oap_client.h \
|
2013-05-02 20:37:16 +00:00
|
|
|
osmocom/gsm/protocol/gsm_03_40.h \
|
2012-06-29 20:01:19 +00:00
|
|
|
osmocom/gsm/protocol/gsm_03_41.h \
|
|
|
|
osmocom/gsm/protocol/gsm_04_08.h \
|
2016-04-20 15:12:24 +00:00
|
|
|
osmocom/gsm/protocol/gsm_04_08_gprs.h \
|
2012-06-29 20:01:19 +00:00
|
|
|
osmocom/gsm/protocol/gsm_04_11.h \
|
|
|
|
osmocom/gsm/protocol/gsm_04_12.h \
|
2017-05-29 13:58:43 +00:00
|
|
|
osmocom/gsm/protocol/gsm_04_14.h \
|
2012-06-29 20:01:19 +00:00
|
|
|
osmocom/gsm/protocol/gsm_04_80.h \
|
|
|
|
osmocom/gsm/protocol/gsm_08_08.h \
|
|
|
|
osmocom/gsm/protocol/gsm_08_58.h \
|
2012-03-08 12:31:52 +00:00
|
|
|
osmocom/gsm/protocol/gsm_09_02.h \
|
2012-06-29 20:01:19 +00:00
|
|
|
osmocom/gsm/protocol/gsm_12_21.h \
|
2016-04-20 15:28:03 +00:00
|
|
|
osmocom/gsm/protocol/gsm_23_003.h \
|
2019-06-14 17:31:30 +00:00
|
|
|
osmocom/gsm/protocol/gsm_23_041.h \
|
2018-10-07 18:10:57 +00:00
|
|
|
osmocom/gsm/protocol/gsm_29_118.h \
|
2012-06-29 20:01:19 +00:00
|
|
|
osmocom/gsm/protocol/gsm_44_318.h \
|
2019-05-03 07:39:10 +00:00
|
|
|
osmocom/gsm/protocol/gsm_48_049.h \
|
2012-06-29 20:01:19 +00:00
|
|
|
osmocom/gsm/protocol/ipaccess.h \
|
2013-03-13 14:15:50 +00:00
|
|
|
osmocom/gsm/protocol/smpp34_osmocom.h \
|
2012-06-29 20:01:19 +00:00
|
|
|
osmocom/gsm/rsl.h \
|
|
|
|
osmocom/gsm/rxlev_stat.h \
|
|
|
|
osmocom/gsm/sysinfo.h \
|
2012-01-17 17:25:50 +00:00
|
|
|
osmocom/gsm/tlv.h \
|
2016-03-14 14:35:50 +00:00
|
|
|
osmocom/sim/class_tables.h \
|
2012-01-17 17:25:50 +00:00
|
|
|
osmocom/sim/sim.h
|
2012-06-29 20:01:19 +00:00
|
|
|
|
|
|
|
if ENABLE_PLUGIN
|
|
|
|
nobase_include_HEADERS += osmocom/core/plugin.h
|
|
|
|
endif
|
|
|
|
|
|
|
|
if ENABLE_MSGFILE
|
|
|
|
nobase_include_HEADERS += osmocom/core/msgfile.h
|
|
|
|
endif
|
|
|
|
|
|
|
|
if ENABLE_SERIAL
|
|
|
|
nobase_include_HEADERS += osmocom/core/serial.h
|
|
|
|
endif
|
|
|
|
|
|
|
|
|
|
|
|
if ENABLE_VTY
|
|
|
|
nobase_include_HEADERS += \
|
|
|
|
osmocom/vty/buffer.h \
|
|
|
|
osmocom/vty/command.h \
|
|
|
|
osmocom/vty/logging.h \
|
2015-10-19 13:14:13 +00:00
|
|
|
osmocom/vty/stats.h \
|
2012-06-29 20:01:19 +00:00
|
|
|
osmocom/vty/misc.h \
|
|
|
|
osmocom/vty/telnet_interface.h \
|
|
|
|
osmocom/vty/vector.h \
|
2014-08-21 10:15:59 +00:00
|
|
|
osmocom/vty/vty.h \
|
2016-02-23 23:10:41 +00:00
|
|
|
osmocom/vty/ports.h \
|
2020-07-28 09:57:51 +00:00
|
|
|
osmocom/vty/cpu_sched_vty.h \
|
add osmo_tdef API, originally adopted from osmo-bsc T_def
Move T_def from osmo-bsc to libosmocore as osmo_tdef. Adjust naming to be more
consistent. Upgrade to first class API:
- add timer grouping
- add generic vty support
- add mising API doc
- add C test
- add VTY transcript tests, also as examples for using the API
From osmo_fsm_inst_state_chg() API doc, cross reference to osmo_tdef API.
The root reason for moving to libosmocore is that I want to use the
mgw_endpoint_fsm in osmo-msc for inter-MSC handover, and hence want to move the
FSM to libosmo-mgcp-client. This FSM uses the T_def from osmo-bsc. Though the
mgw_endpoint_fsm's use of T_def is minimal, I intend to use the osmo_tdef API
in osmo-msc (and probably elsewhere) as well. libosmocore is the most sensible
place for this.
osmo_tdef provides:
- a list of Tnnnn (GSM) timers with description, unit and default value.
- vty UI to allow users to configure non-default timeouts.
- API to tie T timers to osmo_fsm states and set them on state transitions.
- a few standard units (minute, second, millisecond) as well as a custom unit
(which relies on the timer's human readable description to indicate the
meaning of the value).
- conversion for standard units: for example, some GSM timers are defined in
minutes, while our FSM definitions need timeouts in seconds. Conversion is
for convenience only and can be easily avoided via the custom unit.
By keeping separate osmo_tdef arrays, several groups of timers can be kept
separately. The VTY tests in tests/tdef/ showcase different schemes:
- tests/vty/tdef_vty_test_config_root.c:
Keep several timer definitions in separately named groups: showcase the
osmo_tdef_vty_groups*() API. Each timer group exists exactly once.
- tests/vty/tdef_vty_test_config_subnode.c:
Keep a single list of timers without separate grouping.
Put this list on a specific subnode below the CONFIG_NODE.
There could be several separate subnodes with timers like this, i.e.
continuing from this example, sets timers could be separated by placing
timers in specific config subnodes instead of using the global group name.
- tests/vty/tdef_vty_test_dynamic.c:
Dynamically allocate timer definitions per each new created object.
Thus there can be an arbitrary number of independent timer definitions, one
per allocated object.
T_def was introduced during the recent osmo-bsc refactoring for inter-BSC
handover, and has proven useful:
- without osmo_tdef, each invocation of osmo_fsm_inst_state_chg() needs to be
programmed with the right timeout value, for all code paths that invoke this
state change. It is a likely source of errors to get one of them wrong. By
defining a T timer exactly for an FSM state, the caller can merely invoke the
state change and trust on the original state definition to apply the correct
timeout.
- it is helpful to have a standardized config file UI to provide user
configurable timeouts, instead of inventing new VTY commands for each
separate application of T timer numbers.
Change-Id: Ibd6b1ed7f1bd6e1f2e0fde53352055a4468f23e5
2019-01-26 19:36:12 +00:00
|
|
|
osmocom/vty/tdef_vty.h \
|
2016-02-23 23:10:41 +00:00
|
|
|
osmocom/ctrl/control_vty.h
|
2012-06-29 20:01:19 +00:00
|
|
|
endif
|
|
|
|
|
2019-12-15 18:13:26 +00:00
|
|
|
if ENABLE_LIBUSB
|
|
|
|
nobase_include_HEADERS += \
|
|
|
|
osmocom/usb/libusb.h
|
|
|
|
endif
|
|
|
|
|
2014-06-16 12:59:30 +00:00
|
|
|
noinst_HEADERS = \
|
logging vty: rewrite 'logging level' vty cmd generation
Completely drop the implementations of log_vty_command_{str,description}().
These functions have been public API once, marked as deprecated since
c65c5b4ea075ef6cef11fff9442ae0b15c1d6af7 (March 2017). I considered to keep
them, or reduce them to useless stubs, but it is quite silly, really. These
functions are completely and utterly useless outside of libosmocore. Any
program linking these deserves to fail.
Re-implement vty logging level command gen, in logging_vty.c. logging.c is
simply the wrong place for that.
Introduce logging_internal.h to share logging definitions to logging_vty.c
without publishing as API.
Introduce static gen_logging_level_cmd_strs() to compose a list of category
arguments with their descriptions for VTY commands. Use osmo_talloc_asprintf()
instead of the previous error prone and chaotic strlen() counting method.
Do not dynamically generate log level arguments, just keep static strings. We
are super unlikely to ever change the log levels we have.
No changes in logging_vty_test.vty: proves that there is no functional change.
All of this, besides introducing basic sanity, is cosmetic preparation to be
able to re-use the generic command generation code for arbitrary commands with
category or level args (for deprecated and new keywords).
Rationale: I want to hide 'all' and 'everything' from the VTY command
documentation, by means of deprecating. I first tried to simply define a
deprecated 'logging level CAT everything' command:
logging level (all|rsl|rr|...) (debug|info|notice|error|fatal)
logging level CAT everything # <- deprecated and hidden
But unfortunately, command matching doesn't work as intended when the CAT
argument reflects a valid category; I want it to invoke the deprecated function
as soon as the 'everything' keyword follows, but it stays stuck to the "valid"
command when the category argument matches an explicit keyword in that list,
and will throw an error on the following 'everything' keyword. I.e.:
logging level rsl everything
% Unknown command # <-- leads to config file parse error
logging level unknown_string everything
% Ignoring deprecated 'everything' # <-- works only for invalid categories
So I need to define 'everything' separately, again with a list of each valid
category instead of a generic CAT arg.
Change-Id: I3b083f27e3d751ccec258880ae7676e9af959a63
2018-09-10 11:56:03 +00:00
|
|
|
osmocom/gsm/kasumi.h \
|
|
|
|
osmocom/gsm/gea.h \
|
|
|
|
osmocom/core/logging_internal.h \
|
|
|
|
$(NULL)
|
2012-06-29 20:01:19 +00:00
|
|
|
|
2014-06-04 17:07:41 +00:00
|
|
|
osmocom/core/bit%gen.h: osmocom/core/bitXXgen.h.tpl
|
|
|
|
$(AM_V_GEN)$(MKDIR_P) $(dir $@)
|
|
|
|
$(AM_V_GEN)sed -e's/XX/$*/g' $< > $@
|
|
|
|
|
2012-06-29 20:01:19 +00:00
|
|
|
osmocom/core/crc%gen.h: osmocom/core/crcXXgen.h.tpl
|
2012-09-18 16:07:57 +00:00
|
|
|
$(AM_V_GEN)$(MKDIR_P) $(dir $@)
|
2012-06-29 20:01:20 +00:00
|
|
|
$(AM_V_GEN)sed -e's/XX/$*/g' $< > $@
|
2017-01-13 09:03:40 +00:00
|
|
|
|
2017-03-07 23:06:40 +00:00
|
|
|
osmocom/gsm/gsm0503.h: $(top_srcdir)/utils/conv_gen.py $(top_srcdir)/utils/conv_codes_gsm.py
|
2019-12-11 07:46:41 +00:00
|
|
|
$(AM_V_GEN)python3 $(top_srcdir)/utils/conv_gen.py gen_header gsm \
|
2017-03-07 20:56:55 +00:00
|
|
|
--target-path $(builddir)/osmocom/gsm
|
2017-01-13 09:03:40 +00:00
|
|
|
|
|
|
|
CLEANFILES = osmocom/gsm/gsm0503.h
|