Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:37584 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 54352 invoked from network); 11 May 2008 10:09:01 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 11 May 2008 10:09:01 -0000 Authentication-Results: pb1.pair.com smtp.mail=hsantos@isdg.net; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=hsantos@isdg.net; sender-id=pass Received-SPF: pass (pb1.pair.com: domain isdg.net designates 208.247.131.9 as permitted sender) X-PHP-List-Original-Sender: hsantos@isdg.net X-Host-Fingerprint: 208.247.131.9 ntbbs.winserver.com Windows NT 4.0 (older) Received: from [208.247.131.9] ([208.247.131.9:3917] helo=winserver.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 06/6A-34108-CB5C6284 for ; Sun, 11 May 2008 06:09:01 -0400 Received: from mail.winserver.com ([208.247.131.9]) by winserver.com (Wildcat! SMTP Router v6.3.452.5) for internals@lists.php.net; Sun, 11 May 2008 06:07:41 -0400 Received: from hdev1 ([72.144.198.133]) by winserver.com (Wildcat! SMTP v6.3.452.5) with ESMTP id 941806468; Sun, 11 May 2008 06:07:40 -0400 Message-ID: <4826C582.4050705@isdg.net> Date: Sun, 11 May 2008 06:08:02 -0400 Organization: Santronics Software, Inc. User-Agent: Thunderbird 2.0.0.0 (Windows/20070326) MIME-Version: 1.0 To: Pierre Joye CC: internals@lists.php.net References: <48268C66.5090501@isdg.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Creating one extension version: how? From: hsantos@isdg.net (Hector Santos) Pierre Joye wrote: > Hi, > > On Sun, May 11, 2008 at 8:04 AM, Hector Santos wrote: >> How can you prepare my new extension source code and/or links so that the >> DLL can support all the PHP 5.x.x versions? > > You can't. But you can have one source version which can be built > against all PHP versions. > >> I have been trying to figure this out, reading/googling, etc, but in the >> mean time what I had to do was recompile the extension for all PHP releases, >> 5.04, 5.10, 5.12, 5.25 and now 5.26 and provide each one for users to select >> during installation of the extension. > > The rules are relatively simple, each minor (5.1.x, 5.2.x, 5.3.x) > upgrade breaks binary compatibility. That means you will have to > rebuild your extension to get it work with a given version. So the way > you choosed now is the right one. Please note that you aslo need one > for debug and non debug version. Ok, but I would swear I was able to use older 5.x.x 3rd party extensions that still work with each 5.x.x revision. Was that just Luck? For one package, I spoke with the author because of a bug I found and he indicated he had to plans to update his package but I was welcome to do it. I got the source and noticed no real difference in the extension basic framework. But nonetheless, the older extension did worked with newer v5.x.x installations I have so I figure it was possible. No PHP version mismatch loading error which is what I get. -- Hector Santos