Re^4: Updating broken and possibly incomplete SWIG Perl module building tutorial on SWIG web site

How would you use all the goodies of ExtUtils::MakeMaker without starting with a manually written Makefile.PL? I just think having to write a Makefile.PL might be too much unnecessary hassle for the SWIG Perl build process.

Or would this Makefile.PL be the same for every SWIG Perl build and I could send it to them for everyone to use with an updated SWIG Perl build process tutorial?

Comment on Re^4: Updating broken and possibly incomplete SWIG Perl module building tutorial on SWIG web site

Replies are listed 'Best First'.
Re^5: Updating broken and possibly incomplete SWIG Perl module building tutorial on SWIG web site by Corion (Patriarch) on Mar 26, 2011 at 17:41 UTC
Well, `Makefile.PL` is just a Perl program, so you can just incoroporate the relevant parts into your Perl program. Like I already pointed out, `WriteMakefile()`, which, maybe surprinsing to you, writes a `Makefile`. I'm not sure what else I can do other than point you to the documentation or to existing Makefile.PLs? Of course, the Makefile.PL will likely be similar for all modules, but it very much depends on the Perl configuration it will be used with, which can differ between every machine. Which is why it is usually done in the way of asking Perl to produce the appropriate Makefile. Which is what a `Makefile.PL` does once it calls `WriteMakefile`. I presume that including the following lines in your SWIG build process somewhere will produce an appropriate Makefile: `use ExtUtils::MakeMaker; WriteMakefile( # ... appropriate options );` [download] As you will be targetting Perl, it's safe to assume that Perl is available for running code.	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^5: Updating broken and possibly incomplete SWIG Perl module building tutorial on SWIG web site
by Corion (Patriarch) on Mar 26, 2011 at 17:41 UTC

Well, Makefile.PL is just a Perl program, so you can just incoroporate the relevant parts into your Perl program. Like I already pointed out, WriteMakefile(), which, maybe surprinsing to you, writes a Makefile. I'm not sure what else I can do other than point you to the documentation or to existing Makefile.PLs?

Of course, the Makefile.PL will likely be similar for all modules, but it very much depends on the Perl configuration it will be used with, which can differ between every machine. Which is why it is usually done in the way of asking Perl to produce the appropriate Makefile. Which is what a Makefile.PL does once it calls WriteMakefile. I presume that including the following lines in your SWIG build process somewhere will produce an appropriate Makefile:

use ExtUtils::MakeMaker;
WriteMakefile(
    # ... appropriate options
);
[download]

As you will be targetting Perl, it's safe to assume that Perl is available for running code.

[reply]
[d/l]
[select]