[Ardour-Dev] build system, libs, cmdline

John Rigg arddev at sound-man.co.uk
Mon Jan 26 03:03:36 PST 2009

On Mon, Jan 26, 2009 at 10:12:51AM -0000, John Emmas wrote:
> >
> >>working within the source tree was a pain for me
> >>    - I update a file, then scons goes trough the configure process,
> >>      walks the uptodate dirs, 1-2 minutes later gcc tells me
> >>      that i have a semantic error, ... I felt asleep in the mean time
> >>    - is there a way to work with scons that I don't know, except
> >>      writting right code only ...
> >
> >scons has problems, it is true. it is focused on making sure that every
> >build is reliably repeatable and is optimized for always doing complete
> >builds. it is not so good at partial builds.
> >
> The big problem with scons is that it insists on checking for the existence
> of installed libs & utilities every time you use it (even if it's only 30
> seconds since the last time you used it).  Is there a way to make it more
> presumptive?

scons --implicit-deps-unchanged

Don't use it after a CVS update, after unpacking a new tarball or
if you've changed any dependencies though.


More information about the Ardour-Dev mailing list