Hi,
I am working for creating perl BUILD on windows7 and I am successful in running the build for single module. I followed following steps:
1) I used module-starter to create new module. It has lib/newmodule.pm and few testing .t scripts in t directory.
2) Then I ran perl Build.pl, perl Build, perl Build test and then perl Build dist. Hence I get a archived file in the end as an output. I used Module::Build in Build.pl
3) Here the module-starter gives you sample code with test::more module in t directory.
So this process I have understood but I am not completely clear on the build concept. I have few doubts:
My development environment is like this:
C:/perl ---Activestate perl 5.14.2
C:/development ---main folder for perl code
C:/development/project_name/bin/*.pl ---PL files (single PL or PL which calls functions from PM files in lib directory mentioned below)
C:/development/project_name/lib/*.pm ---PM files (custom PM having functions being called by PL files mentioned above in bin directory)
Q1.) Is this Directory structure fine?
Q2.) Where should I keep the build scripts in above structure (if above structure is fine)?
Q3.) Will there be a single build script for a complete development folder OR there should be multiple build scripts for each PL/PM file.
Q4.) Is Module::Build sufficient to create the Build for the whole structure including PL,PM files?
Q5.) What should be the structure of Build code? Should it be the same which Module-starter gives you. If yes, then what should be the structure of "t" directory in it? Please guide me explicitly how should be the build directory and which files should be there
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|