On 05/10/00, "Mike Blazer <[EMAIL PROTECTED]>" wrote:
> > It might be helpful to people if someone who has used a non-M$C/C++ cc
> > posted / made available their Config.pm so that those who wish to emulate...
>
> No need. It will not help, to my mind it's quite wrong to edit Config.pm massively -
>it should be created when you (or your vendor) are compiling your Perl.
Well of course, that's why it's called hacking IMO .. <laugh> but it's
overly rigid to say "quite wrong" .. nothing is "wrong" if it works or even
merely teaches you something valuable in the process of trying, people
learn in different ways and anyway I had no other choices but to go the
route I did (AS Perl based on 5.6 didn't exist yet then). I learned some of
the inner secrets of Perl by hand-editing Config.pm -- and it works, sort
of. As I say, I had no other choices excepting to chuck AS Perl entirely,
which I think is an excellent product and performs on the whole very very
well, and try to build a Perl from generic CPAN source, like Joe did. Sure,
I would have had a properly created Config.pm if I had (successfully) done
it that way. But what would I have been forced to give up? How would the
performance have been? And could i have gotten it to build -- maybe my way
wasn't really a shortcut but I find the task of setting up a build of Perl
rather daunting. Even on the minGW List very few people reported to me that
they had built Perl (they are rather heavily into "C" over there ... lol
... not very interested in Perl).
And this compilation also creates lib\CORE\perl.lib that is compartible
[sic] only with the compiler that built Perl. So, whatever you put to
Config.pm will not work.
> The other thing is that module binaries (dlls) are not compiler dependant, sure, -
>they are only compartible with the Perl version. So, the reasonable solution to any
>distributor is what GSAR made in his port of Perl 5.004 - he provided 2 perl.lib's -
>for Borland and for MSVC. Dunno why ActiveState does not go this way.
> In this case you also don't need to edit Config.pm by hands - you can just choose
>one of the prebuilt pairs (it was not like that in GSAR port, that's why you really
>had to edit the Config.pm).
> I mean - what is really needed for any professional Win32 Perl binary distribution
>- a few perl.lib's and a few Config.pm's - for free Borland 5.5, for MSVC, for mingw,
>for cygwin cc.
I would love to get my hands on a Config.pm for minGW.
BTW I use pmake as my Make utility when building from CPAN. Not dmake --
hated it when i tried it. i think people ought to try the pmake mentioned
in another poster's contribution rather than nmake -- which is many years
old and looks like M$ will never update it and (yet also still) give away
for free.
soren andersen
P.S. - "Compatible", Mike. Not "Compartible."
---
You are currently subscribed to perl-win32-users as: [archive@jab.org]
To unsubscribe, forward this message to
[EMAIL PROTECTED]
For non-automated Mailing List support, send email to
[EMAIL PROTECTED]
