asterisk users - Mar 2014 - Skip ./configure when source directory has not changed

Hi,

A silly question bouncing in my head for a long time :
when I'm installing-configuring a new Asterisk system, I'm using a
script
that issue the usual ./configure, make and make install commands to install
Asterisk from source.

When installation fails for any reason, I would re-run my installation
script which in turn, among many things, would launch the above ./configure
command.

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 ?

Regards
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20140324/799782a8/attachment.html>

>
> A silly question bouncing in my head for a long time :
> when I'm installing-configuring a new Asterisk system, I'm using a
script that issue the usual
> ./configure, make and make install commands to install Asterisk from
source.
>
> When installation fails for any reason, I would re-run my installation
script which in turn,
> among many things, would launch the above ./configure command.
>
> 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 ?
>
> Regards
>
>
>
You do not need to call ./configure when building the package fails. Just call
"make", maybe
"make --jobs=4".

If your build fails because of a missing library, then you may (need) to call
configure again.

jg
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20140324/68de2a22/attachment.html>

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.

-- 
AJS

Answers come *after* questions.

On Mon, 24 Mar 2014 21:20:45 +0100
Olivier <oza.4h07 at gmail.com> wrote:
> A silly question bouncing in my head for a long time :
> when I'm installing-configuring a new Asterisk system, I'm using a
> script that issue the usual ./configure, make and make install
> commands to install Asterisk from source.
> 
> When installation fails for any reason, I would re-run my installation
> script which in turn, among many things, would launch the
> above ./configure command.
> 
> 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 ?
You kind of have it backwards there.  You would only be able to
skip ./configure if you changed the source files but didn't change
anything else on the system (e.g., libraries or utilities).  But
there's no way for a build script to know if anything on the system
changed without running ./configure.  That's what ./configure does.  So
the only sensible thing to do is to run it every time.


-- 

C. Chad Wallace, B.Sc.
The Lodging Company
http://www.lodgingcompany.com/
OpenPGP Public Key ID: 0x262208A0