[PROPOSED PATCH] Add Parrot::Embed to Repository

[Chromatic]

Here's a proposed patch that seems to work okay for me on Linux. It's not
great or beautiful, mostly because of the Makefile hackery. It's a starting
point though. I suspect Windows might complain.

I don't have any particular attachment to any approach here, only that this
get in the repository somehow.

-- c

[Jerry Gay]

On 8/15/06, chromatic <chro...@wgz.org> wrote:
> Here's a proposed patch that seems to work okay for me on Linux. It's not
> great or beautiful, mostly because of the Makefile hackery. It's a starting
> point though. I suspect Windows might complain.
>

i'll happily test, but i can't apply it, as it seems not to be in the
format my patch util expects. did you use C<diff -u>? i don't see the
familiar "Index: <filename>" headers.
~jerry

[Chromatic]

On Wednesday 16 August 2006 08:57, jerry gay wrote:

> i'll happily test, but i can't apply it, as it seems not to be in the
> format my patch util expects. did you use C<diff -u>? i don't see the
> familiar "Index: <filename>" headers.

It's a standard svk diff. That's really weird. Is this any better?

-- c

[Jerry Gay]

my tortoisesvn patch command doesn't like it, either. so i downloaded
gnu patch for windows, and that seems to like it better. applied, and
rebuilding now. however, i'm currently also recovering from the stm
merge, which has uncovered some threading failures on windows.
hopefully those will be either hidden from view or resolved shortly,
and i'll be able to provide you with some useful feedback.
~jerry

[Jerry Gay]

On 8/15/06, chromatic <chro...@wgz.org> wrote:

> Here's a proposed patch that seems to work okay for me on Linux. It's not
> great or beautiful, mostly because of the Makefile hackery. It's a starting
> point though. I suspect Windows might complain.
>

windows indeed complains. not only about missing prereq
(ExtUtils::PkgConfig,) but ...and you've got to see this coming...
missing pkg-config. i don't know anything about pkg-config, and i
don't know anything about Module::Build, so i can't take this beyond
the small makefile fix i needed on the last line of the
config/gen/makefiles/ext.in (s<ext/><>.)

~jerry

[Francois PERRAD]

At 15:48 15/08/2006 -0700, chromatic wrote:
>Here's a proposed patch that seems to work okay for me on Linux. It's not
>great or beautiful, mostly because of the Makefile hackery. It's a starting
>point though. I suspect Windows might complain.

I try it on Win2000 with MinGW.
1) ExtUtils::PkgConfig is a wrapper over pkg-config, and pkg-config is not
available on Windows
2) Module::Build is not installed in the distribution ActiveState Perl
5.8.8 Build 817, and this module has a lot of dependence
3) I think the best way is to use an old fashion Makefile.PL and not a Build.PL

François Perrad.

[Chromatic]

On Thursday 17 August 2006 00:28, Francois PERRAD wrote:

> I try it on Win2000 with MinGW.
> 1) ExtUtils::PkgConfig is a wrapper over pkg-config, and pkg-config is not
> available on Windows

Okay, that's a problem. It's actually a big problem, for two reasons.

First, linking against libparrot requires knowing its location and the
compiler flags. When building this within the parrot/ directory, I could
just parse parrot.rc. However, when building outside of parrot/, such as
when downloading from the CPAN, pkg_config is the way to go, if possible.

I'll add some logic to improve this situation.

> 2) Module::Build is not installed in the distribution ActiveState Perl
> 5.8.8 Build 817, and this module has a lot of dependence

It can go in Bundle::Parrot.

> 3) I think the best way is to use an old fashion Makefile.PL and not a
> Build.PL

EU::MM is, hands-down, the biggest bucket of suck in the entire Perl 5 core.
(Yes, the interface is worse than File::Find and yes the implementation is
worse than B::Bytecode, which at least you can count on always failing to
work.) When the great old ones arrive from the dark spaces between
dimensions, I plan to throw its source code at them to distract them from
eating the earth. It'll work too; it's not really good for anything else.[1]

-- c

[1] Disclaimer: if all you're doing is installing a pure-Perl module, not
compiling anything or doing any sort of customization, you don't have to
realize that what you're really doing is using Perl to write cross-platform
shell scripts, if at all possible, and I still don't know how to phrase the
horror that is MY, it's not quite so bad.

[Francois Perrad]

For installing Module::Build over ActivePerl 5.8.7 Build 815, I need to
install from CPAN:
Pod-Escapes 1.04
Pod-Single 3.04
Pod-Readme 0.081
podlators 2.04
PAR-Dist 0.16
ExtUtils-CBuilder 0.18
ExtUtils-ParseXS 2.15
Module-Signature 0.44 (not the latest 0.55)
Module-Build 0.2805

François

>~jerry
>
>