What am I missing??
A good reason to use "src" instead of "lib"
A good reason you're avoiding PMLIBDIRS or PM option?
Seriously, do you have me on ignore? Allergic to manuals documented solutions?
:P
symlink or copying files yourself misses the point of having a toolkit like MakeMaker with conventions
A try
$ module-starter --module Goner --email email --author author --verbo +se --eumm Created Goner Created Goner\lib Created Goner\lib\Goner.pm Created Goner\t Created Goner\t\pod-coverage.t Created Goner\t\pod.t Created Goner\t\manifest.t Created Goner\t\boilerplate.t Created Goner\t\00-load.t Created Goner\ignore.txt Created Goner\Makefile.PL Created Goner\Changes Created Goner\README Added to MANIFEST: Changes Added to MANIFEST: ignore.txt Added to MANIFEST: lib/Goner.pm Added to MANIFEST: Makefile.PL Added to MANIFEST: MANIFEST Added to MANIFEST: README Added to MANIFEST: t/00-load.t Added to MANIFEST: t/boilerplate.t Added to MANIFEST: t/manifest.t Added to MANIFEST: t/pod-coverage.t Added to MANIFEST: t/pod.t Created Goner\MANIFEST Created starter directories and files $ cd Goner $ md SAUCE $ move lib SAUCE $ tree -f -a . . |-- ./Changes |-- ./MANIFEST |-- ./Makefile.PL |-- ./README |-- ./ignore.txt |-- ./sauce | `-- ./sauce/lib | `-- ./sauce/lib/Goner.pm `-- ./t |-- ./t/00-load.t |-- ./t/boilerplate.t |-- ./t/manifest.t |-- ./t/pod-coverage.t `-- ./t/pod.t 3 directories, 11 files $ perl -i.bak -pe " s{lib/}{SAUCE/lib/}g; s{^(\s*NAME.*)$}{$1, PMLIBDI +RS => [ q{SAUCE} ], }mi ;" Makefile.PL $ perl Makefile.PL INSTALL_BASE=thebase Checking if your kit is complete... Warning: the following files are missing in your kit: lib/Goner.pm Please inform the author. Generating a dmake-style Makefile Writing Makefile for Goner Writing MYMETA.yml and MYMETA.json $ dmake install cp SAUCE/lib/Goner.pm blib\lib\SAUCE\lib\Goner.pm Installing thebase\lib\perl5\SAUCE\lib\Goner.pm Appending installation info to thebase\lib\perl5\MSWin32-x86-multi-thr +ead/perllocal.pod
Gee, flaunting convention isn't the smartest idea, I end up with SAUCE in the module tree
Luckily i've read PMLIBDIRS docs and I know what to do, append to Makefile.PL and I get
sub MY::libscan { my( $mm, $path ) = @_; ## FIX SAUCE if( $path =~ m{\$\(INST_LIB\)} ){ warn "BEFORE $path\n"; $path =~ s{.SAUCE.lib}{}; warn "AFTER $path\n"; } ## allow any directory (usually . is most important ) return $path if -d $path; ## ignore perl4-style .pl files return $path if $path =~ /\.pm$/; return $path if $path =~ /^blib/; return ''; ## ignore by default } __END__ $ perl Makefile.PL INSTALL_BASE=thebase Checking if your kit is complete... Warning: the following files are missing in your kit: lib/Goner.pm Please inform the author. BEFORE $(INST_LIB)\SAUCE\lib\Goner.pm AFTER $(INST_LIB)\Goner.pm Generating a dmake-style Makefile Writing Makefile for Goner Writing MYMETA.yml and MYMETA.json $ dmake install cp SAUCE/lib/Goner.pm blib\lib\Goner.pm Installing thebase\lib\perl5\Goner.pm Appending installation info to thebase\lib\perl5\MSWin32-x86-multi-thr +ead/perllocal.pod
convention is convention for a reason, its convenient:D
In reply to Re^2: Makefile.PL Question ( ExtUtils::MakeMaker PMLIBDIRS sub MY::libscan )
by Anonymous Monk
in thread Makefile.PL Question
by baxy77bax
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |