On 8/9/07, <b class="gmail_sendername">Tzafrir Cohen</b> <<a href="mailto:tzafrir.cohen@xorcom.com">tzafrir.cohen@xorcom.com</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
> After you run make menuselect, you'll have a file 'menuselect.makeopts' in<br>> your asterisk source dir. Copy that to /etc/asterisk.makeopts (or<br>> ~/.asterisk.makeopts) and it will be used for future builds. Once you've
<br>> copied the file over, do a 'make distclean ; ./configure ; make' to check<br>> that it worked.<br><br>Hmmm.... why "distclean" ?<br></blockquote></div><br>'clean' doesn't remove the generated
menuselect.makeopts:<br><br>clean: $(SUBDIRS_CLEAN)<br> rm -f defaults.h<br> rm -f include/asterisk/build.h<br> rm -f include/asterisk/version.h<br> @$(MAKE) -C menuselect clean<br> cp -f .cleancount .lastclean
<br><br>distclean: clean<br> @$(MAKE) -C menuselect dist-clean<br> @$(MAKE) -C sounds dist-clean<br> rm -f menuselect.makeopts makeopts menuselect-tree menuselect.makedeps<br> rm -f makeopts.embed_rules
<br> rm -f config.log config.status<br> rm -rf autom4te.cache<br> rm -f include/asterisk/autoconfig.h<br> rm -f include/asterisk/buildopts.h<br> rm -rf doc/api<br> rm -f build_tools/menuselect-deps
<br><br>So if you go through this cycle:<br><br>untar<br>./configure<br>make menuselect<br>...make module choices...<br>cp menuselect.makeopts /etc/asterisk.makeopts<br>make clean<br>./configure<br><br>Then the automated run of menuselect is going to have two makeopts files that it might pull from: the generated one left over from the first run of configure, and the one in /etc. But since the files should be identical, you won't be absolutely sure that your file in /etc is the one driving the module choices.
<br><br>If you changed "cp menuselect.makeopts..." to "mv menuselect.makeopts..." in the above snippet, then I suppose 'make clean' would suffice. But 'make distclean' doesn't do any harm - it should return the directory to it's post-untar state, right?
<br clear="all"><br>-- <br>j.