Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:3889
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <00f101c361e5$7e124f00$0500000a@master>
To: "Vlad Krupin" <vlad@php.net>, <internals@lists.php.net>
References: <3F398B29.5040206@php.net> <3F3A8F45.4090606@php.net>
Date: Wed, 13 Aug 2003 23:54:38 +0200
Organization: Proventum Solutions ApS
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] win32 questions - try 2
From: edink@proventum.net ("Edin Kadribasic")

Hi Vlad,

1. Where can I get includes and libs for MSVC++?
2. Snap builder compiles everything it can automatically :)
3. We'll do that once we get the extension building on the snaps box.

Edin

----- Original Message -----
From: "Vlad Krupin" <vlad@php.net>
To: <internals@lists.php.net>
Sent: Wednesday, August 13, 2003 9:19 PM
Subject: [PHP-DEV] win32 questions - try 2


> 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
> >
> >
>
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
>