Bigtop::Backend::Init::Std Bigtop::Backend::Init::Std is a Bigtop backend which works sort of like h2xs.
Download

Bigtop::Backend::Init::Std Ranking & Summary

Bigtop::Backend::Init::Std Tags

Perl module backend Bigtop Bigtop backend h2xs backend

Bigtop::Backend::Init::Std Description

Bigtop::Backend::Init::Std is a Bigtop backend which works sort of like h2xs. Bigtop::Backend::Init::Std is a Bigtop backend which works sort of like h2xs.SYNOPSISIf your bigtop file looks like this: config { build_dir `/home/yourname`; app_dir `appsubdir`; Init Std {} } app App::Name { }when you type bigtop --create your.bigtop Initor bigtop --create your.bigtop allthis module will generate the build directory as /home/yourname/appsubdirThen it will make subdirectories: t, lib, and docs. Then it will make files: Changes, MANIFEST, MANIFEST.SKIP, README, and Build.PL. Finally, it will copy your.bigtop into the docs dir of under appsubdir.As with any backend, you can include no_gen 1; in its config block: config { Init Std { no_gen 1; } }Then, no files will be generated. But, you can also exclude indiviual files it would build. Simply list the file name as a keyword and give the value no_gen: config { Init Std { MANIFEST no_gen; Changes no_gen; } }If you are in create mode and your config does not include app_dir, one will be formed from the app name, in the manner of h2xs. So, in the above example it would be /home/yourname/App-NameOutside of create mode, the current directory is used for building, if it looks like a plausible build directory (it has a Build.PL, etc). In that case, having a base_dir and/or app_dir in your config will result in warning(s) that they are being ignored. Requirements: · Perl

Bigtop::Backend::Init::Std Related Software