[sr-dev] [kamailio/kamailio] Add kpcre group (#901)

Fabrice Fontaine notifications at github.com
Fri Jan 13 11:07:18 CET 2017


buildroot does not use deb or rpm specs from kamailio tree.
To integrate a package to buildroot, I have to define a .mk that explain how to download the source from github and selects the appropriate modules depending on what packages were selected by the user.
For example, if the package libmemcached is selected then this package must be built before kamailio and kmemcached module can be compiled:

```
ifeq ($(BR2_PACKAGE_LIBMEMCACHED),y)
KAMAILIO_DEPENDENCIES += libmemcached
KAMAILIO_GROUPS += kmemcached
endif
```

Indeed, you're right, I could use the standard group instead of kstandard. That was my first intent but I realised that it didn't give me enough granularity. For example, in the standard module, kamailio compiles the mod_list_devel which are not necessary as one of the goal of buildroot is to make the most tiny and efficient distribution.

But I perfectly understand that you do not want to modify the behavior of the kstandard target as it could impact other users. May I suggest to keep kstandard as it is and define kpcre and kmini targets like this (I think this option is more readable than adding an env variable but this is only my personal opinion)?

```
module_group_kmini=$(mod_list_basic) $(mod_list_extra) \
					  $(mod_list_db) $(mod_list_dbuid)

module_group_kpcre=$(mod_list_pcre)
```					  

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/901#issuecomment-272406856
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-dev/attachments/20170113/0f55b763/attachment.html>


More information about the sr-dev mailing list