Hi all,

Here's a sharing session on my successful experience on the a/m, with lots of excellent support from Sisyphus (thanks dude!).

Problem statement:
Writing a C/C++ extension can be difficult and laborious. Fortunately inline.pm helps to automate much of the work, and keep us developer dudes focused on the coding. Developers should read up on the fairly extensive inline documentation for the reference and tutorial.

Once the libraries are compiled, the C/C++ codes should not be needed during implementation/ distribution. This short article describes the Lazy Man's Way of doing just that. Note that the recommended method is documented in inline-faq. In the following paragraph there are minor references to inline-faq, so be sure to have the documentation ready.

The Solution:
1. Read up on Question 3 on the FAQ. Following steps 1+2+3.
2. Within the 'use Inline' config hash, add the following parameter:
CLEAN_AFTER_BUILD    => 0
This is an important line.
3. Write a simple piece of code that will cause the module to be compiled using inline. 4. Expect a subdirectory called _Inline/, with a huge bunch of subdirectories under it. 5. Follow _Inline/build/ until you see the auto/ subdirectory. Copy this directory and everything under it to your installation of Perl, typically at
C:/Perl/Site/Lib/. There should be an existing auto/ already.
6. Now you need to point your original Perl module to the compiled library. Take out the 'use Inline' line. Add the following lines instead:
require DynaLoader;
our @ISA = qw (DynaLoader);
bootstrap <package name>;

That's it! Have fun!
_______________________________________________
Perl-Win32-Users mailing list
Perl-Win32-Users@listserv.ActiveState.com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs

Reply via email to