[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Discuss-gnuradio] autoconf tricks (Was:...Building usrp module and
From: |
Prateek Dayal |
Subject: |
Re: [Discuss-gnuradio] autoconf tricks (Was:...Building usrp module and firmware |
Date: |
Tue, 9 Nov 2004 13:50:19 +0530 |
Hi,
is there a difference between make clean and make distclean ???
Regards,
Prateek
On Tue, 9 Nov 2004 19:39:45 +1030, Berndt Josef Wulf <address@hidden> wrote:
> On Tuesday 09 November 2004 09:59, Tom Huppi wrote:
> > Hi All,
> >
> [...]
> > Knowing this, it is handy to simply edit the config.status script
> > and re-execute it (as opposed to editing the Makefiles.)
> > Obviously, this is a testing only technique, but it saves the
> > hasssle of re-running the configure script, and also tells you
> > what you want the configure script to find, or at least it tells
> > that if the configure script were to find -I/path/to/foo on your
> > system, the build wouldn't fail.
>
> Good to know, thanks your enlightment.
>
>
>
> > Going further, Eric is unhappily correct that writing a new M4
> > macro or finding an existing one which does the right thing is the
> > correct course of action. When hacking the configure.in, don't
> > forget to trash the config.cache file regularly, and do note that
> > the aclocal.m4 can become a consideration when adding or changing
> > macros.
> >
> > Conceptually, fooling with the configure system is (or should be)
> > a small-ish part of the development process. For this reason,
> > autoconf optimizes certain things at the expense of others. In
> > the case of config.cache, the speed of execution is thought more
> > important than the ease of config system maintanance, thus, the
> > hassle of remembering to remove it or worse, trying to understand
> > when it's removal is necessary. I've seen it burn and turn off a
> > lot of developers which is a shame. That's my take on things at
> > least.
>
> "make distclean" will take care of this. All I do is run "make distclean",
> "bootstrap", "configure" after modifying any of the fundamental autoconf
> files.
>
> cheerio Berndt
>
>
> _______________________________________________
> Discuss-gnuradio mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
>
>
>
--
Prateek Dayal
B.Tech 4th Year
ECE
IIT Guwahati
www.geocities.com/pmd_iitgw
- [Discuss-gnuradio] Connect one source to multiple sinks?, David Carr, 2004/11/02
- Re: [Discuss-gnuradio] Connect one source to multiple sinks?, Berndt Josef Wulf, 2004/11/02
- Re: [Discuss-gnuradio] SIGSTKFLT, Eric Blossom, 2004/11/02
- Re: [Discuss-gnuradio] SIGSTKFLT, Prateek Dayal, 2004/11/02
- [Discuss-gnuradio] Building usrp module and firmware, Berndt Josef Wulf, 2004/11/08
- Re: [Discuss-gnuradio] Building usrp module and firmware, Eric Blossom, 2004/11/08
- [Discuss-gnuradio] autoconf tricks (Was:...Building usrp module and firmware, Tom Huppi, 2004/11/08
- Re: [Discuss-gnuradio] autoconf tricks (Was:...Building usrp module and firmware, Eric Blossom, 2004/11/08
- Re: [Discuss-gnuradio] autoconf tricks (Was:...Building usrp module and firmware, Berndt Josef Wulf, 2004/11/09
- Re: [Discuss-gnuradio] autoconf tricks (Was:...Building usrp module and firmware,
Prateek Dayal <=
- Re: [Discuss-gnuradio] autoconf tricks (Was:...Building usrp module and firmware, Dave Dodge, 2004/11/09
- [Discuss-gnuradio] Correction: Use CXXFLAGS not CCFLAGS, Eric Blossom, 2004/11/08
- Re: [Discuss-gnuradio] SIGSTKFLT, Stephane Fillod, 2004/11/20
Re: [Discuss-gnuradio] Connect one source to multiple sinks?, Eric Blossom, 2004/11/02