From: Gale Andrews <gale@au...> - 2010-04-24 19:31:52
| From Richard Ash <richard@...>
| Sat, 24 Apr 2010 12:07:32 +0100
| Subject: [Audacity-devel] Extended import filtering
> On Sat, 2010-04-24 at 14:48 +0400, LRN wrote:
> > So, the correct way is to
> > configure
> > make dep
> > make
> > ? (i generally don't need to install, running Audacity from builddir)
> Yes, although if configure and the Makefile.in's haven't changed, you
> can skip the configure step.
> Running from the install directory will work, but can catch you out,
> because of files loaded from the environment, which tend to come from
> your installed copy not the SVN copy - I'm trying to look at this at the
> moment, will come back to you.
> For this purpose (where loading files isn't needed), you won't have
I tend to go by your (Richard's) guidance which Martyn dropped in here:
So although it's obvious if files are added/removed, meaning you need
make dep, it's easy to miss that #includes have been changed inside
files (unless we put in the commit logs that this has actually happened).
So doing make dep as well looks a lot safer.
Thanks for tip about running from build dir.
Get latest updates about Open Source Projects, Conferences and News.