I'm building a
Perl distribution, and having some trouble with building Perl modules that link to C libraries.
Different modules seem to use a variety of different methods to build/define the include path that will ultimately be provided to gcc.
For example "$ENV{INCLUDE}", "perl Makefile.PL INC=-I..." and "$Config{libpth}". And some Makefile.PL do their own stuff to locate include paths beyond these.
Unfortunately, many of them use one method and ignore the others, some overwrite one with the other, and I can't find one way of providing the include path to the modules in a way that all modules can handle correctly.
Now, I'm ok with talking to authors or taking over modules and converting them to support the correct way, but I have no idea what that is.
What is the "correct" way to provide the include paths via CPAN.pm such that all modules in a recursive install will receive and understand the include path to use for finding libs?
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.