FAQ

help in creating the makefile non-interactively

Manish Marathe
Sep 6, 2005 at 7:18 pm
Hello,

I am planning to automate the build process for the 100 phalanx CPAN
components and the first one I picked was CPANPLUS. I manually built the
component and while doing that, the first step was executing "perl
Makefile.PL". I had to interactively go through 29 questions and then
the makefile was created. If I want to automate this process, I would
want to force the creation of makefile and that no human intervention
should be needed.

Is there a way to do that. Any help would be appreciated. Thank you

-Manish
reply

Search Discussions

9 responses

  • H.Merijn Brand at Sep 6, 2005 at 11:02 pm

    On Tue, 06 Sep 2005 12:18:08 -0700, Manish Marathe wrote:

    Hello,

    I am planning to automate the build process for the 100 phalanx CPAN
    components and the first one I picked was CPANPLUS. I manually built the
    component and while doing that, the first step was executing "perl
    Makefile.PL". I had to interactively go through 29 questions and then
    the makefile was created. If I want to automate this process, I would
    want to force the creation of makefile and that no human intervention
    should be needed.

    Is there a way to do that. Any help would be appreciated. Thank you
    # perl Makefile.PL JFDI=1
    -Manish
    --
    H.Merijn Brand Amsterdam Perl Mongers (http://amsterdam.pm.org/)
    using Perl 5.6.2, 5.8.0, 5.8.5, & 5.9.2 on HP-UX 10.20, 11.00 & 11.11,
    AIX 4.3 & 5.2, SuSE 9.2 & 9.3, and Cygwin. http://www.cmve.net/~merijn
    Smoking perl: http://www.test-smoke.org, perl QA: http://qa.perl.org
    reports to: smokers-reports@perl.org, perl-qa@perl.org
  • Abe Timmerman at Sep 8, 2005 at 4:39 pm
    Op een mooie zomerdag (Wednesday 07 September 2005 01:02),schreef H.Merijn
    Brand:
    On Tue, 06 Sep 2005 12:18:08 -0700, Manish Marathe
    <mmarathe@spikesource.com>

    wrote:
    Hello,

    I am planning to automate the build process for the 100 phalanx CPAN
    components and the first one I picked was CPANPLUS. I manually built the
    ...
    Is there a way to do that. Any help would be appreciated. Thank you
    # perl Makefile.PL JFDI=1
    There is also the more generic way to indicate automated installs by setting
    the environment variable PERL_MM_USE_DEFAULT to something like 'y'
    That might work on more modules that use ExtUtils::MakeMaker for their
    interactive stuff.

    Good luck,

    Abe
    --
    Nick> > Over to you, Jarkko ???
    Jarkko> Urque.
    Hmm... I can't seem to find a patch in there anywhere.
    -- Nicholas Clark on p5p @ 2004-01-23
  • Manish Marathe at Sep 8, 2005 at 11:41 pm
    I see, thanks, at least I could automate the build of CPANPLUS.

    Is there any code-coverage tool for perl modules, which will give the
    code coverage report against the tests it ran for that module?

    I know of Devel-Coverage-0.2, to be used something like

    perl -d:coverage <script_name> args..

    But I am not sure how to tool could be used to get the code coverage,
    for example of CPANPLUS module against the CPANPLUS tests that came with
    it.
    On Thu, 2005-09-08 at 00:23 +0200, Abe Timmerman wrote:
    Op een mooie zomerdag (Wednesday 07 September 2005 01:02),schreef H.Merijn
    Brand:
    On Tue, 06 Sep 2005 12:18:08 -0700, Manish Marathe
    <mmarathe@spikesource.com>

    wrote:
    Hello,

    I am planning to automate the build process for the 100 phalanx CPAN
    components and the first one I picked was CPANPLUS. I manually built the
    ...
    Is there a way to do that. Any help would be appreciated. Thank you
    # perl Makefile.PL JFDI=1
    There is also the more generic way to indicate automated installs by setting
    the environment variable PERL_MM_USE_DEFAULT to something like 'y'
    That might work on more modules that use ExtUtils::MakeMaker for their
    interactive stuff.

    Good luck,

    Abe
  • Abe Timmerman at Sep 9, 2005 at 12:38 am
    Op een mooie zomerdag (Friday 09 September 2005 01:40),schreef Manish
    Marathe:
    I see, thanks, at least I could automate the build of CPANPLUS.

    Is there any code-coverage tool for perl modules, which will give the
    code coverage report against the tests it ran for that module?

    I know of Devel-Coverage-0.2, to be used something like

    perl -d:coverage <script_name> args..
    You mean Devel::Cover I guess, that's at 0.53 now
    But I am not sure how to tool could be used to get the code coverage,
    for example of CPANPLUS module against the CPANPLUS tests that came with
    it.
    Like the man-page suggests:

    $ PERL_HARNESS_SWITCHES=-MDevel::Cover make test
    $ cover

    That will generate nice HTLM reports (if you have Template Toolkit installed)

    HTH +
    Good luck,

    Abe
    --
    "Jarkko Hietaniemi" is actually the code name for a whole team of Finnish
    super-programmers, capable of working continuously 25 hours a day without
    tripping each other up, and running solely only on intravenous caffeine.
    -- Nicholas Clark on p5p @ 2002-03-04
  • Paul Johnson at Sep 9, 2005 at 11:09 am

    On Fri, Sep 09, 2005 at 02:38:14AM +0200, Abe Timmerman wrote:

    Like the man-page suggests:

    $ PERL_HARNESS_SWITCHES=-MDevel::Cover make test
    $ cover

    That will generate nice HTLM reports (if you have Template Toolkit installed)
    TT is required for some of the reports, but not for the standard html
    report produced by default.

    And to bring us full circle, I'm very interested in being able to
    automatically build *loads* of modules in order to automate coverage
    testing for cpancover. http://pjcj.sytes.net/cpancover/

    --
    Paul Johnson - paul@pjcj.net
    http://www.pjcj.net
  • Manish Marathe at Sep 9, 2005 at 4:07 pm

    Paul Johnson wrote:
    On Fri, Sep 09, 2005 at 02:38:14AM +0200, Abe Timmerman wrote:


    Like the man-page suggests:

    $ PERL_HARNESS_SWITCHES=-MDevel::Cover make test
    $ cover

    That will generate nice HTLM reports (if you have Template Toolkit installed)
    TT is required for some of the reports, but not for the standard html
    report produced by default.
    Hey guys thanks that worked, ya I am almost there in having it
    completely automatic build, the process would be

    --> downloading from the module's repository --> perl Makefile.PL -->
    make --> make test --> code coverage --> posting test results and code
    coverage results executed on different platforms

    I believe I can do the make test and code coverage in one part as code
    coverage actually covers code against the tests which are run.

    And to bring us full circle, I'm very interested in being able to
    automatically build *loads* of modules in order to automate coverage
    testing for cpancover. http://pjcj.sytes.net/cpancover/

  • Orton, Yves at Sep 7, 2005 at 10:40 am

    Is there a way to do that. Any help would be appreciated. Thank you
    # perl Makefile.PL JFDI=1
    -Manish
    Wow, where is that documented?

    Yves
  • H.Merijn Brand at Sep 7, 2005 at 10:53 am

    On Wed, 7 Sep 2005 11:40:05 +0100 , "Orton, Yves" wrote:

    Is there a way to do that. Any help would be appreciated. Thank you
    # perl Makefile.PL JFDI=1
    -Manish
    Wow, where is that documented?
    I don't think it is, the author told me
    I also think that the acronym is VERY wrong

    JFDI is the acronym for Just Fucking Do It
    which is far to rude for a module that is supposed to be utterly friendly

    --
    H.Merijn Brand Amsterdam Perl Mongers (http://amsterdam.pm.org/)
    using Perl 5.6.2, 5.8.0, 5.8.5, & 5.9.2 on HP-UX 10.20, 11.00 & 11.11,
    AIX 4.3 & 5.2, SuSE 9.2 & 9.3, and Cygwin. http://www.cmve.net/~merijn
    Smoking perl: http://www.test-smoke.org, perl QA: http://qa.perl.org
    reports to: smokers-reports@perl.org, perl-qa@perl.org
  • Orton, Yves at Sep 7, 2005 at 10:56 am
    H.Merijn Brand wrote on Wednesday, September 07, 2005 12:53 PM
    On Wed, 7 Sep 2005 11:40:05 +0100 , "Orton, Yves"
    wrote:
    Is there a way to do that. Any help would be
    appreciated. Thank you
    # perl Makefile.PL JFDI=1
    -Manish
    Wow, where is that documented?
    I don't think it is, the author told me
    I also think that the acronym is VERY wrong

    JFDI is the acronym for Just Fucking Do It
    which is far to rude for a module that is supposed to be
    utterly friendly
    Heh. I thought it was kinda cute. :-)

    Yves

Related Discussions

Discussion Navigation
viewthread | post