I have a fairly large Perl-Tk applications (30,000 lines) that uses XS to
call C subroutines quite extensively.  This application contains several
modules that call other other modules in the application, and the source
files for each module are each located in their own directory. 

To test Inline, I changed the XS calls in one module to use Inline instead. 
When I try the "perl *.PL", "make", "make test", "make install" dance, I get
an error saying that it can't load the extension for the module that uses
Inline.

Okay, that's the background for my real application.  Attached to this email
is a simplified set of modules that duplicates my problem.  The directory
structure looks like this:

Inline_test/Fruit/Apple/Apple.pm
Inline_test/Fruit/Apple/Makefile.PL
Inline_test/Fruit/Apple/test.pl
Inline_test/Fruit/Banana/Banana.pm
Inline_test/Fruit/Banana/Makefile.PL
Inline_test/Fruit/Banana/test.pl
Inline_test/Fruit/Fruit.pm
Inline_test/Fruit/Makefile.PL
Inline_test/Fruit/test.pl
Inline_test/Makefile.PL
Inline_test/test.pl

When I run "perl *.PL", "make", and "make test", I get the following output:

Can't load installed extension 'Fruit::Apple'
from relative path '../../blib/lib'.
 at test.pl line 0
INIT failed--call queue aborted, <DATA> line 1.

Can anyone look at these (very short) files and tell me if I'm doing
something wrong, or if Inline can't handle multple modules like this?

Thanks,

Brett Denner

Inline_test.tar.gz

Reply via email to