Hi!
Short presentation: I'm new on the list, just started using Inline a few
days ago (I like it a lot!). I do Perl on a few platforms, mostly Windows
and Solaris.
>Well, Inline-0.32 is *finally* on CPAN. It has 2 known bugs on Windows
>platforms. Autographed copies of Inline to those who can find them first. ;)
Is this one of the bugs? When I use Inline::CPP (Inline 0.31) on a Windows
machine and put the source deep down in the directory tree, I can't get it
to link properly. It seems like something (the linker?) can't handle the
long file names that is the result.
My workaround for this was:
a) to put the source closer to the root dir (this is not a real-life option
though); or
b) to add a line in the Inline::check_module subroutine:
$o->{module} = "mod" . md5_hex($o->{module});
after the line:
$o->{module} = "${pkg}_$o->{language}_$id" . md5_hex($o->{code});
to make the module name a little bit shorter. This makes if difficult to
see which directory contains which module, but are there any other bad
things about this solution? It's a quick hack and I don't have the entire
structure figured yet so there are probably much better ways.
Another thing, I would really need somehting like the 'CCFLAGS' option in
Inline::CPP for adding another include directory. Or have I just missed
that feature?
The workaround for this was to patch the Config.pm file's CC flags value. A
non-elegant solution I would say :)
/J
------ ---- --- -- -- -- - - - - -
Johan Lindström Boss Casinos
Sourcerer [EMAIL PROTECTED]
http://www.bahnhof.se/~johanl/
If the only tool you have is a hammer,
everything tends to look
like a nail
