This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.
Vadim Yanitskiy axilirator at gmail.com> We generate "conv.h" and put it into the source directory? Actually, no. We aren't generate the "conv.h". It's written manually and contains the conv_test_vector structure definition and the do_check() function definition. One was introduced by: https://gerrit.osmocom.org/#/c/1627/ so now the same test logic is used in two different tests (both conv and conv_gsm0503) without code duplication. Don't you confuse it with the "gsm0503.h", which is exactly generated by the "utils/conv_gen.py"? With best regards, Vadim Yanitskiy. 2017-05-01 2:56 GMT+07:00 Holger Freyther <holger at freyther.de>: > > > On 30. Apr 2017, at 10:02, Vadim Yanitskiy <axilirator at gmail.com> wrote: > > > > It seems, I already found one solution. You're right, "build dir != src > dir" > > was the problem, so I added this: > > > > conv_conv_gsm0503_test_CPPFLAGS = \ > > $(AM_CPPFLAGS) \ > > -I$(top_srcdir)/tests/conv > > > > And now everything is fine! > > We generate "conv.h" and put it into the source directory? From 10.000 > miles aways it sounds a bit odd (at least for checkout from git, make dist > would be a different topic). > > holger -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20170501/18a71e5f/attachment.htm>