I dont understand very well the inners of the Makefile, just the
basics. But in gentoo you can do ebuild <path to asterisk ebuild>
compile, then make changes to the application you want, then again
ebuld blah compile, and the compilation time is very fast, so i assume
just a small part of the source is recompiled. Then I just copy the .so
to /usr/lib/asterisk/modules/ and thats all.<br><br><div><span class="gmail_quote">On 12/6/05, <b class="gmail_sendername">Tilghman Lesher</b> <<a href="mailto:tilghman@mail.jeffandtilghman.com">tilghman@mail.jeffandtilghman.com
</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">On Tuesday 06 December 2005 11:46, Tzafrir Cohen wrote:<br>> On Tue, Dec 06, 2005 at 07:45:35AM -0600, Tilghman Lesher wrote:
<br>> > On Tuesday 06 December 2005 02:16, Tzafrir Cohen wrote:<br>> > > On Mon, Dec 05, 2005 at 06:27:10PM -0500, Russell Bryant wrote:<br>> > > > On Dec 5, 2005, at 5:27 PM, Steven Critchfield wrote:
<br>> > > > >>I have complied asterisk from source.<br>> > > > >>I am trying to recompile app_dial.c after made couple of<br>> > > > >> little changes.<br>> > > > >>What I want to do is to recreate app_dial.so without
<br>> > > > >> recompile full asterisk.<br>> > > > >>How can I do it?<br>> > > > ><br>> > > > >First, rebuilding asterisk isn't much of a chore.<br>> > > > >
<br>> > > > >Second, learn how make works. Make shouldn't rebuild all of<br>> > > > > the source unless you have done a make clean.<br>> > > > ><br>> > > > >So finally, you should just issue a make in the base of the
<br>> > > > > asterisk tree.<br>> > > ><br>> > > > There is also a utility that was written by Anthony Minessale<br>> > > > (anthm) that can be used for this. Copy contrib/scripts/astxs
<br>> > > > to somewhere in your PATH. Then, in the base asterisk source<br>> > > > directory, run 'astxs apps/app_dial.c'.<br>> > ><br>> > > If the change is simply in app_dial.c, shouldn't a simple 'make
<br>> > > app_dial.c' from apps do just that?<br>> > ><br>> > > If not: what's the problem?<br>> ><br>> > No, there are additional flags defined in the main Makefile which<br>> > need to be passed to the subdirectory. They are not in the
<br>> > subdirectory to begin with, because they need to be consistently<br>> > applied to each subdirectory, and different build targets require<br>> > different flags.<br>> ><br>> > The astxs script emulates the passing of these flags to a directory
<br>> > which is not even under the asterisk tree.<br>><br>> So basically we have the cons of a recursive make (no really simple<br>> way of building a single target) but not the benefits of it (not<br>> possible to run make from a subdir).
<br>><br>> One common prctice is to split out most of the common code of the<br>> makefile into code that is include-d by make, rather than the current<br>> practice in the Asterisk build system of exporting vars.
<br><br>Under what bug number have you filed your proposed patch? :-)<br><br>--<br>Tilghman<br>_______________________________________________<br>--Bandwidth and Colocation provided by <a href="http://Easynews.com">Easynews.com
</a> --<br><br>Asterisk-Dev mailing list<br>To UNSUBSCRIBE or update options visit:<br> <a href="http://lists.digium.com/mailman/listinfo/asterisk-dev">http://lists.digium.com/mailman/listinfo/asterisk-dev</a><br></blockquote>
</div><br><br clear="all"><br>-- <br>"Su nombre es GNU/Linux, no solamente Linux, mas info en <a href="http://www.gnu.org">http://www.gnu.org</a>"