[asterisk-users] Skip ./configure when source directory has not changed

A J Stiles asterisk_list at earthshod.co.uk
Tue Mar 25 04:18:58 CDT 2014

On Monday 24 Mar 2014, Olivier wrote:
> Is there a smart way to accelerate things a bit and skip ./configure when
> source files have not changed since last configure command was previously
> run ?

That probably isn't what you really want to do.

The most common reason why a build fails is because a -dev package is missing.  
Alternatively, some required component might be present, but located somewhere 
away from the usual search path.

Once either of these situations is resolved, you are going to need to re-run 
the configure script anyway.


Answers come *after* questions.

More information about the asterisk-users mailing list