Maybe you can write multiple Build.PL and MANIFEST files (e.g. Build.PL.p1, MANIFEST.p1, Build.PL.p2, MANIFEST.p2, etc.), one for each package you want to produce, and write a script to copy these to the standard names before building each package. The MANIFEST can include only the files you want in the package.
Update: Here is a very crude script which demonstrates my suggestion.
#!/usr/bin/perl # use strict; use warnings; my $package = shift; my @FILES = ('Build.PL', 'MANIFEST'); # Check that required files are available before making any changes foreach my $file (@FILES) { die "$file.$package not found" unless(-e "$file.$package"); die "$file not a symlink" unless(! -e "$file" or -l "$file"); } # Re-link files foreach my $file (@FILES) { unlink($file) or die "unlink $file: $!" if(-l "$file"); symlink("$file.$package", "$file") or die "link $file: $!"; } system("perl Build.PL");
In reply to Re: How do I configure Module::Build to build multiple packages from the same lib directory?
by ig
in thread How do I configure Module::Build to build multiple packages from the same lib directory?
by ELISHEVA
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |