Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:49926
Return-Path: <rquadling@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 31400 invoked from network); 19 Oct 2010 12:42:49 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 19 Oct 2010 12:42:49 -0000
Authentication-Results: pb1.pair.com smtp.mail=rquadling@gmail.com; spf=pass; sender-id=pass
Authentication-Results: pb1.pair.com header.from=rquadling@gmail.com; sender-id=pass; domainkeys=bad
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.42 as permitted sender)
DomainKey-Status: bad
X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01
X-PHP-List-Original-Sender: rquadling@gmail.com
X-Host-Fingerprint: 209.85.212.42 mail-vw0-f42.google.com  
Received: from [209.85.212.42] ([209.85.212.42:59697] helo=mail-vw0-f42.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 67/88-21220-8429DBC4 for <internals@lists.php.net>; Tue, 19 Oct 2010 08:42:49 -0400
Received: by vws9 with SMTP id 9so780096vws.29
        for <internals@lists.php.net>; Tue, 19 Oct 2010 05:42:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:received:mime-version:received:reply-to:from
         :date:message-id:subject:to:content-type;
        bh=/oshhN1KMbL1uugcmBnbKwt5feXXsR8GF/4QqQ7mALA=;
        b=u35Ybwad5d99YhXkoqC3Uaz+okvMzRj6i+kd4EMKL1C7SIKW9G/ShORgkAy9nVYfHv
         1ZUrQD142CykauQbvR0uyOO4t0zHnVW8f87ShOBsjkNultmVgrMXNAMsgrdFmPMFydsn
         4euUmlQn8MPUW6sX9E40ZOfZ/1H6GKnOLJm+E=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:reply-to:from:date:message-id:subject:to:content-type;
        b=V3ZsqLbKJIHfuiEhfUz6SGb7w9dSFl+UImlrg3Jf/fAY5iMwj9HM+MLYK9BTbgf6II
         g3GGn+yMtOQH2SPT1dn34zLVplJzAtffBVEhc2RI2vb1WerabjfX8qlDk8EDUxAmYQvW
         rvSzWOcLj0T8nx2XSc/DrmVEACHi7ljkHsJ3A=
Received: by 10.224.15.83 with SMTP id j19mr2971373qaa.319.1287492166168; Tue,
 19 Oct 2010 05:42:46 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.20.1 with HTTP; Tue, 19 Oct 2010 05:42:25 -0700 (PDT)
Reply-To: RQuadling@googlemail.com
Date: Tue, 19 Oct 2010 13:42:25 +0100
Message-ID: <AANLkTinhiHESbRoV4cN0zhPCzGVM4DkM4EDi3TNO7Y=X@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Continuing the build process after a failed build of an extension.
From: rquadling@gmail.com (Richard Quadling)

Hi.

Is there a way to continue the build process (on Windows) if a shared
extension fails to build.

Currently, if an extension fails, then it halts the entire build.
Which is probably fine in production, but for my own builds, I'd like
it to just ignore the failed extension.

I know I can exclude it from the configure, but that won't help me
when the extension is fixed.

Regards,

Richard.

-- 
Richard Quadling
Twitter : EE : Zend
@RQuadling : e-e.com/M_248814.html : bit.ly/9O8vFY