On Fri, Jan 8, 2010 at 15:14, Ron Mayer <rm_pg@cheapcomplexdevices.com> wrote:
> Magnus Hagander wrote:
>> On Fri, Jan 8, 2010 at 05:22, Ron Mayer <rm_pg@cheapcomplexdevices.com> wrote:
>>> David E. Wheeler wrote:
>>>> On Jan 7, 2010, at 1:31 PM, Dave Page wrote:
>>>>> No, I'm suggesting the mechanism needs to support source and binary
>>>>> distribution. For most *nix users, source will be fine. For Windows
>>>>> binaries are required.
>>>> I would love to follow what Strawberry Perl has done to solve this problem. In 2.0.
>>> +1. They did a nice job.
>>
>> For those of us who have no idea what Strawberry Perl did (other than
>> not shipping Microsoft compatible libraries, and is thus useless for
>> PostgreSQL), could someone explain it?
>>
>
> As far as I can tell they shipped the minimal set of tools that they needed
> to build extensions rather than distribute binaries.
> http://en.wikipedia.org/wiki/Strawberry_Perl
> I don't know the details, but it works smoothly for them.
Right. They are msys compatible, not Microsoft compatible. And msys
uses non-Windows-standard format of the import libraries. and the
import libraries are needed for people to link to the interpreter,
like pl/perl.
Also a quick re-check shows that there appears to be no 64-bit version
available.
-- Magnus HaganderMe: http://www.hagander.net/Work: http://www.redpill-linpro.com/
