Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:3885 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 79078 invoked from network); 13 Aug 2003 19:19:39 -0000 Received: from unknown (HELO mail.echospace.com) (216.57.208.136) by pb1.pair.com with SMTP; 13 Aug 2003 19:19:39 -0000 Received: (qmail 31386 invoked from network); 13 Aug 2003 19:19:34 -0000 Received: from bdsl.66.14.129.196.gte.net (HELO php.net) (66.14.129.196) by mail.echospace.com with SMTP; 13 Aug 2003 19:19:34 -0000 Message-ID: <3F3A8F45.4090606@php.net> Date: Wed, 13 Aug 2003 12:19:33 -0700 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: en-us, en MIME-Version: 1.0 To: internals@lists.php.net References: <3F398B29.5040206@php.net> In-Reply-To: <3F398B29.5040206@php.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: win32 questions - try 2 From: vlad@php.net (Vlad Krupin) Ok, looks like all win32 experts are on vacation, or have no opinion. I've implemented win32 build to the best of my knowledge, and it works. I committed it, along with the .dsp file. But I still want to figure out how to make sure that php_pspell.dll gets built and included into next PHP release. Somebody who does windows builds, please, could you tell me what I need to do to get pspell into win32 snapshots builds? I imagine, we need: 1) install pspell includes and libraries on a build machine, so we can link to them 2) add pspell to the build 3) add ';extension=php_pspell.dll' to php.ini-* files Thanks in advance, Vlad Vlad Krupin wrote: > Hi, internals, > > I need some help with my attempt to provide win32 port for the > spellchecker (pspell extension). Since I am pretty ignorant as far as > win32 goes, can some kind win32 guru answer this?: > > 1. The spellchecker has dictionaries that are located somewhere on the > system and there is a registry key pointing to that place. PHP needs to > know where they are. We can > a) read it from the registry every time we open a new dictionary > b) create an ini option for that (I know that nobody likes making > php.ini even larger) > c) force the developer provide a path (extra hassle, and the scripts > won't be very portable between windows and other OSes, so I'd rather not > do it) > What is the best way to do it? > > 2. What needs to be done to make sure the new dll gets built and > distributed along with other extensions with the next releae of PHP? I > assume that whoever does those win32 builds needs to know how to install > the spellchecker, where to get the library, etc. > > Thanks, > > Vlad > >