PageRenderTime 52ms CodeModel.GetById 24ms RepoModel.GetById 0ms app.codeStats 0ms

/trunk/Examples/perl5/index.html

#
HTML | 79 lines | 61 code | 18 blank | 0 comment | 0 complexity | 7053aa3035ca38593b99ee5cf800c194 MD5 | raw file
Possible License(s): LGPL-2.1, Cube, GPL-3.0, 0BSD, GPL-2.0 
    

  1. <html>
    2. 

  2. <head>
    3. 

  3. <title>SWIG:Examples:perl5</title>
    4. 

  4. </head>
    5. 

  5. 

  6. <body bgcolor="#ffffff">
    7. 

  7. <H1>SWIG Perl Examples</H1>
    8. 

  8. 

  9. <p>
    10. 

  10. The following examples illustrate the use of SWIG with Perl.
    11. 

  11. 

  12. <ul>
    13. 

  13. <li><a href="simple/index.html">simple</a>.  A minimal example showing how SWIG can
    14. 

  14. be used to wrap a C function and a global variable.
    15. 

  15. <li><a href="constants/index.html">constants</a>.  This shows how preprocessor macros and
    16. 

  16. certain C declarations are turned into constants.
    17. 

  17. <li><a href="variables/index.html">variables</a>.  This example shows how to access C global variables from Perl.
    18. 

  18. <li><a href="value/index.html">value</a>. How to pass and return structures by value.
    19. 

  19. <li><a href="class/index.html">class</a>. How to wrap a simple C++ class.
    20. 

  20. <li><a href="reference/index.html">reference</a>. C++ references.
    21. 

  21. <li><a href="pointer/index.html">pointer</a>. Simple pointer handling.
    22. 

  22. <li><a href="funcptr/index.html">funcptr</a>. Pointers to functions.
    23. 

  23. </ul>
    24. 

  24. 

  25. <h2>Compilation Issues</h2>
    26. 

  26. 

  27. <ul>
    28. 

  28. <li>To create a Perl extension, SWIG is run with the following options:
    29. 

  29. 

  30. <blockquote>
    31. 

  31. <pre>
    32. 

  32. % swig -perl5 interface.i
    33. 

  33. </pre>
    34. 

  34. </blockquote>
    35. 

  35. 

  36. <li>The compilation of examples is done using the file <tt>Example/Makefile</tt>.  This
    37. 

  37. makefile performs a manual module compilation which is platform specific.  Typically,
    38. 

  38. the steps look like this (Linux):
    39. 

  39. 

  40. <blockquote>
    41. 

  41. <pre>
    42. 

  42. % swig -perl5 interface.i
    43. 

  43. % gcc -fpic -c -Dbool=char -I/usr/lib/perl5/5.00503/i386-linux/CORE interface_wrap.c
    44. 

  44. % gcc -shared interface_wrap.o $(OBJS) -o interface.so 
    45. 

  45. % perl
    46. 

  46. use interface;
    47. 

  47. ...
    48. 

  48. </pre>
    49. 

  49. </blockquote>
    50. 

  50. 

  51. <li>The politically "correct" way to compile a Perl extension module is to use MakeMaker
    52. 

  52. and related tools (especially if you are considering third-party distribution).  Consult
    53. 

  53. a book such as Advanced Perl Programming for details.
    54. 

  54. 

  55. </ul>
    56. 

  56. 

  57. <h2>Compatibility</h2>
    58. 

  58. 

  59. The examples have been extensively tested on the following platforms:
    60. 

  60. 

  61. <p>
    62. 

  62. <ul>
    63. 

  63. <li>Linux
    64. 

  64. <li>Solaris
    65. 

  65. </ul>
    66. 

  66. 

  67. Please see the <a href="../../Doc/Manual/Windows.html">Windows</a> page in the main manual for information on using the examples on Windows. <p>
    68. 

  68. 

  69. <p>
    70. 

  70. Due to wide variations in the Perl C API and differences between versions such as the ActivePerl release for Windows,
    71. 

  71. the code generated by SWIG is extremely messy.
    72. 

  72. If the code doesn't compile or work with your version of Perl, please let us know by 
    73. 

  73. contacting us on the <a href="http://www.swig.org/mail.html">mailing lists</a>.
    74. 

  74. Better yet, send us a patch.
    75. 

  75. 

  76. </body>
    77. 

  77. </html>
    78. 

  78. 

  79. 

  80.