autoconf and .deb question

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/.

Ruben Undheim ruben.undheim at gmail.com
Tue Mar 14 13:38:44 UTC 2017


Hi Max,

When using two columns for a line in a debian/*.install file, you
actually pick from the source tree - not from the installed files! The
first column specify which files in the source tree to pick, the
second column specify where it will be installed. See
https://www.debian.org/doc/manuals/maint-guide/dother.en.html#install

> Should we be worried that it might break some time in future? Should we move those headers away from noinst_* section?

So this should always work - as long as the files are not moved to
another place in the source tree.. No need to worry.


Cheers
Ruben



2017-03-14 14:20 GMT+01:00 Max <msuraev at sysmocom.de>:
> Hi.
>
> There's strange thing about the way autoconf and debian/rules interact for
> OpenBSC:
> - in openbsc/include/openbsc/Makefile.am gsm_data_shared.h and common_cs.h
> are in noinst_HEADERS
> - in debian/openbsc-dev.install they are marked for installation
>
> And this actually works! If you run "dpkg-buildpackage -uc -us -tc" you'll
> get openbsc-dev*.deb with those headers properly installed.
>
> It's nice but feels a bit too much like magic. Any ideas how dh_install (or
> smth else?) manages to work around it?
> Should we be worried that it might break some time in future? Should we move
> those headers away from noinst_* section?
>
> --
> Max Suraev <msuraev at sysmocom.de> http://www.sysmocom.de/
> =======================================================================
> * sysmocom - systems for mobile communications GmbH
> * Alt-Moabit 93
> * 10559 Berlin, Germany
> * Sitz / Registered office: Berlin, HRB 134158 B
> * Geschaeftsfuehrer / Managing Director: Harald Welte
>



More information about the OpenBSC mailing list