7 Feb
2013
7 Feb
'13
11:50 a.m.
I usually do:
make cfg
make
make modules
make utils
make install
The "make utils" takes care of kamcmd...
Peter
On Thu, 2013-02-07 at 10:44 +0100, Daniel-Constantin Mierla wrote:
Hello,
the modules are updated for the symbols and library installation paths.
kamcmd is a dependency of ctl module and compiled if not compiled
before. You can go in its folder and compile it with make if you want to
use it from there.
Cheers,
Daniel
On 2/7/13 10:11 AM, Olle E. Johansson wrote:
--
Peter Dunkley
Technical Director
Crocodile RCS Ltd
Hi!
Got a bit surprised again - but I've always been confused by the build system... ;-)
I ran
make
make modules
and then
make install
At "make install" Kamailio builds the .so modules again but even more
importantly - it seems to build kamcmd from scratch by compiling the source code. I think
this should be done at "make".
I haven't gone through all the output to check for other utilities, but if some
Makefile guru can look at this and there's no opinion about why it should be this way,
I suggest we fix it so that we build everything at "make", all modules are built
and linked at "make modules" and let "make install" just install and
not build.
/O
CC (gcc) [U kamcmd] parse_listen_id.o
CC (gcc) [U kamcmd] sercmd.o
LD (gcc) [U kamcmd] kamcmd
sed -e "s#sercmd#kamcmd#g" \
-e "s#sip-router#kamailio#g" \
< sercmd.8 > /usr/local/share/man//man8/kamcmd.8
chmod 644 /usr/local/share/man//man8/kamcmd.8
touch /usr/local/sbin//kamcmd
_______________________________________________
sr-dev mailing list
sr-dev(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev