If I can just get 'make install' to install into INSTALLSITEARCH (which is mentioned in the table), then that will be fine.make install make alone puts all relevant files into directories that are named + by the macros INST_LIB, INST_ARCHLIB, INST_SCRIPT, INST_MAN1DIR and INST_MAN3DIR. All these default to something below ./blib if you a +re *not* building below the perl source directory. If you *are* build +ing below the perl source, INST_LIB and INST_ARCHLIB default to ../../ +lib, and INST_SCRIPT is not defined. The *install* target of the generated Makefile copies the files fo +und below each of the INST_* directories to their INSTALL* counterpart +s. Which counterparts are chosen depends on the setting of INSTALLDIR +S according to the following table: INSTALLDIRS set to perl site vendor PERLPREFIX SITEPREFIX VENDORPREFIX INST_ARCHLIB INSTALLARCHLIB INSTALLSITEARCH INSTALLVENDOR +ARCH INST_LIB INSTALLPRIVLIB INSTALLSITELIB INSTALLVENDOR +LIB INST_BIN INSTALLBIN INSTALLSITEBIN INSTALLVENDOR +BIN INST_SCRIPT INSTALLSCRIPT INSTALLSITESCRIPT INSTALLVENDOR +SCRIPT INST_MAN1DIR INSTALLMAN1DIR INSTALLSITEMAN1DIR INSTALLVENDOR +MAN1DIR INST_MAN3DIR INSTALLMAN3DIR INSTALLSITEMAN3DIR INSTALLVENDOR +MAN3DIR The INSTALL... macros in turn default to their %Config ($Config{installprivlib}, $Config{installarchlib}, etc.) counterpa +rts. You can check the values of these variables on your system with perl '-V:install.*'
In reply to Re^2: How to tell EU::MM to install a pure-perl module into an architecture-specific location
by syphilis
in thread How to tell EU::MM to install a pure-perl module into an architecture-specific location
by syphilis
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |