Here's a patch for Build.PL that should avoid most of the pkg_config troubles
on platforms that don't have it. I still don't quite know what to do on
Windows when installing from outside of the Parrot tree.
-- c
You could always query parrot itself for it's configuration variables, see
e.g.: tools/dev/src-t.sh. That is: the user would have to specify the
location of the parrot executable.
2 further notes:
- parrot.pc seems not to have all necessary Cflags
- parrot-config should have some macro-ish queries that retrieve all necessary
compile / link setting with one --option [1]
I'd just ci and let it evolve.
leo
[1] http://rt.perl.org/rt3/Public/Bug/Display.html?id=32365
http://rt.perl.org/rt3/Public/Bug/Display.html?id=34356
1) in get_parrot_path_external(), the split of PATH is not portable,
File::Spec gives a solution :
for my $path ( File::Spec->path() )
2) consider the use of File::Which instead of get_parrot_path_external
use File::Which;
...
return which('parrot');
François.
>-- c