Hi,<br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
libbsc.a contains all functionality that is in the domain of the BSC. This<br>
includes the vty_interface.c.<br>
<br>
libmsc.a contains all the handling of GSM04.08. In our case even the HLR/VLR<br>
(db.c). In our case this is everything that is not in the BSC.<br>
<br>
bsc_hack links to the libbsc and libmsc and adds vty_interface_layer3. Now the<br>
dependencies don&#39;t really matter as the link will just resolve them.<br>
<br>
For the on-waves/bsc-master branch I&#39;m only using libbsc.a. This means your<br>
commit added a dependency on db.c again. On top of that it will really help us<br>
keeping the BSC/MSC separation in place which is beneficial to stuff like<br>
channel handling..<br>
<br>
does this clear things up?<br></blockquote><div><br>I understand the idea of separation (the naming scheme _layer3 could be better :).<br>But what I don&#39;t see is how that commits restores it. Because it doesn&#39;t remove the<br>
db.c dependency: from vty_interface.c you still access the DB.<br> <br>Sylvain<br></div></div><br>