[PATCH] src: use new libosmogsm and include/osmocom/[gsm|core] path to headers
laforge at gnumonks.org
Wed Apr 27 08:34:09 UTC 2011
On Tue, Apr 26, 2011 at 05:43:14PM +0200, Pablo Neira Ayuso wrote:
> BTW, I'll start with the patches that fix the namespace pollution
> (adding osmo_* to all functions and such). In order to reduce the
> clashes with other ongoing patches, I'll send this change in several
> series that include small chucks (ie. first all select.c functions and
> structures start by osmo_*, then signal.c, and so on). Let me know if
> you think this is excessive.
I think especially for the generic stuff like select.c and signal.c it is
important to change.
Nonetheless, as you indicate, it is likely to create many clashes. What
do the other developers on this list say? Should we first try to get rid
of some of our branches in the various projects in order to reduce the
fall-out from "osmo_" prefixing some of our core functions?
- Harald Welte <laforge at gnumonks.org> http://laforge.gnumonks.org/
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
More information about the baseband-devel