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.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.