Rules - Main Options
Main Options Tab
- Include Sub Modules
- You can choose to force the inclusion of sub modules. For example, if this rule is for module My::Module, you may wish to include My::Module::First and perhaps My::Module::First::Second or any other sub modules. You can use this option to include modules at sub levels 1 to 5 or select all levels.
- Code Package Method
- The default Code Package Method is determined as follows. The system default is 'Masked Text'. This may be overriden at the overall project level if the project default is set to 'Plain Text'. Setting this value at the module rule level is only effective if you are setting it to 'Plain Text'. A default setting of 'Masked Text' within a module rule is ignored.
- Module Package Location
- The default Module Package Location is determined as follows. The system default is 'Virtual @INC'. This may be overriden at the overall project level if the project default is set to 'Standard @INC'. Setting this value at the module rule level is only effective if you are setting it to 'Standard @INC'. A default setting of 'Virtual @INC' within a module rule is ignored.
- Preserve Module Tree
- Some modules search for their dependencies by traversing the @INC path from which they were loaded. This cannot work if the @INC structure has been flattenedina Virtual @INC. Selecting this option ensures that this module and all its sub modules are packaged in a traversable tree.
- Modules Tab
- You can specify additional modules and Perl scripts to be included when this module is included. The @INC array and any extra search paths will be searched for the modules at scan time.
- Libraries Tab
- You can specify any shared libraries that should be included when this module is included in your package. This identifies the libraries by absolute paths. A more portable rule method that will work across all machines is to use the Custom Script. However, this rule is much simpler to set up.
- On Mac OS X you will also need to specify appropriate Mac OS X Frameworks so that the libraries can be made portable.
- See Also :
- Shared Library Dependencies
- Project Tree Shared Libraries
- Directory Slurp Tab
- You can specify additional sub directories (relative to entries in the @INC array) that will be 'slurped' for modules and perl files or data. Note that this is not the same as including sub directories of THIS module which are handled by the 'Include Sub Modules' option above.
- Additional Files Tab
- You can specify additional data files to include. You specify relative paths and the @INC array and any additional search paths will be searched at scan time.
Cava Packager Copyright © 2006-2012 Mark Dootson