Beefy Boxes and Bandwidth Generously Provided by pair Networks
more useful options

Re^4: how to create a makefile using PAR::Packer

by gepebril69 (Scribe)
on Dec 12, 2012 at 19:10 UTC ( #1008572=note: print w/replies, xml ) Need Help??

in reply to Re^3: how to create a makefile using PAR::Packer
in thread how to create a makefile using PAR::Packer

<quote>In my simple example 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

Replies are listed 'Best First'.
Re^5: how to create a makefile using PAR::Packer
by karlgoethebier (Monsignor) on Dec 12, 2012 at 21:10 UTC

    nroff and groff are typesetting systems on Unix systems.

    With the following two commands you can create a printable file and send it to your printer:

    Karls-Mac-mini:~ karl$ groff -mm ch01 > ch01.fmt Karls-Mac-mini:~ karl$ lp ch01.fmt

    Update:...ch01 is formated file...

    The very basic blueprint to include code in your perl program(s) is:


    package Foo; use strict; use warnings our $VERSION = '1.00'; use base 'Exporter'; our @EXPORT = qw( foo ); sub foo { return "bar\n"; } 1; # later, in your main program you say: use strict; use warnings use lib q(/path/to/Foo); use Foo; print foo();

    See perlmod

    pp for creating executables is OK (and cool) but keep in mind that this just are self extracting archives - you can unzip them.

    Regards, Karl

    «The Crux of the Biscuit is the Apostrophe»

      Hi Karl

      I will use your examples and maybe it will become clearer to me what you try to explain. And how to use this info in my solutions.

      I've changed the extension of one file from .exe -> .zip and you are 100% right. I'm completely shocked! Besides the advantage of not to create a Perl environment on systems I don't see the benefit of using pp (PAR::Packer). Is there a way to prevent this and use a module that doesn't make retrieving the source code that easy!!! And produce real machine code.

        As I previously suggested, read and understand the documentation, this is all explained there. If you don't understand the benifit of pp, why are you using it?

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1008572]
and all is quiet...

How do I use this? | Other CB clients
Other Users?
Others pondering the Monastery: (4)
As of 2018-03-24 22:42 GMT
Find Nodes?
    Voting Booth?
    When I think of a mole I think of:

    Results (299 votes). Check out past polls.