in reply to how to create a makefile using PAR::Packer

I read this: pp only to create executable when source has changed

Update: Perhaps this helps:

Makefile

hello: hello.pl Foo.pm
    pp hello.pl -o hello.exe

[download]

Foo.pm

package Foo;
# test1
1;

[download]

hello.pl

#!/c:/perl/bin/perl
use lib q(.);
use Foo;
print "Hello!\n";

[download]

First call of dmake builds hello.exe. Next call shows `hello' is up to date. Change Foo.pm and run dmake.

Search

Update: Another weird use of make ;-) 28.13 make Isn't Just for Programmers! in "Unix Power Tools"

OK, i've bought the book and i hope Tim doesn't blame...

manual: ch01.fmt ch02.fmt ch03.fmt
        lp ch0[1-3].fmt
ch01.fmt: ch01
        nroff -mm ch01 > ch01.fmt
ch02.fmt: ch02
        tbl ch02 | nroff -mm > ch02.fmt
ch03.fmt: ch03a ch03b ch03c
        nroff -mm ch03[abc] > ch03.fmt

[download]

Best Regards, Karl

«The Crux of the Biscuit is the Apostrophe»

Replies are listed 'Best First'.
Re^2: how to create a makefile using PAR::Packer
by gepebril69 (Scribe) on Dec 12, 2012 at 15:27 UTC

    Thx for the replay

    What is the use of the Foo.pm in this story and why do you need it?

    In the last example you are using Visual Fox pro examples, why is this?, I thought this was a Perl forum and for me it makes it more confusing?

[reply]
      Thx for the replay

      My pleasure.

      At pp only to create executable when source has changed you wrote:

      As the projects get bigger it takes longer before executables are created, what I would like and not have found yet is that executables are only created when the source (pl) has been changed. So executables are not recreated when no changes to sources have been made.

      In my simple example Foo.pm is a source file - and only when it is changed, pp is run.

      In the last example you are using Visual Fox pro examples, why is this?

      I can't see any Visual Fox Pro example for the moment, sorry. So i can't answer why this is. Please correct my if i'm wrong.

      I thought this was a Perl forum and for me it makes it more confusing?

      Nothing but the truth, this is a Perl forum - but it doesn't confuse you.

      I hope that helps.

      Best regards, Karl

      Update: P.S.: I'm about loosing my faith...please correct my if i'm wrong.

      «The Crux of the Biscuit is the Apostrophe»

[reply]

        <quote>In my simple example Foo.pm is a source file - and only when it is changed, pp is run.</quote> Thank you for explaining what it is, my questions were 'what is the use?' and 'why do you need them?'

        I found out that .pm files are perl modules, and from what I understand you can compare them with object files in C(++). Is that right? If so, I could speed up things if I first created .pm of my functions file and constant declaration files before compiling the executables, as I call them as require basic_func.plin all .pl files. That is the way I was thought to do.

        The extension .fmt, used in your examples is according to Google the extension for Visual Fox pro file and not .pl like perl

        I'm using PAR:Packer, as this was the way within Perl, I found out on Google to create .exe files in a free way. Maybe I'm wrong on this and I should take another turn in creating .exe files in a faster in more reliable way

[reply]
[d/l]

In Section Seekers of Perl Wisdom