Thanks for the link almut. I think I got some understanding of the .al files. I'm not sure how/why my perl script is looking for it though. I didnt see any reference to using AutoLoader in the SWIG instructions. I'm not sure the easiest way forward. For now, my goal is to get my C APIs running from Perl. I can live with slower performance if necessary in short term.
Steps till I ran into this problem
- I ran swig and generated a .pm file
- Modified my existing C API's build (Makefile) to compile the sources + the _wrap.c file generated by swig into a shared lib.
- Created a simple perl script with "use <mymodule>" and then invoked one API.
I did not use MakeMaker or ModuleMaker etc.
After I read about AutoLoader, AutoSplit, I wentahead and ran autosplit_list_modules on my module's .pm file. I see the lib/auto directories created, but no .al files are until the auto/ directory. Still debugging..any pointers will be helpful. |