Re: Building a Mojolicious app with PAR::Packer

pp comes with options

check these logs

use autodie qw' system ';
for my $opts ( "", "-n -x", "-x", "-c" ){
    my $out = "use-mojo$opts.exe";
    $out =~ s/\s/_/g;
    my $log = "log-$out.txt";
    my $cmd = "pp -v 99 -o $out  use-mojo.pl  $opts   >$log  2>&1 ";
    print "$cmd\n";
    system $cmd;
}
__END__

pp -v 99 -o use-mojo.exe  use-mojo.pl     >log-use-mojo.exe.txt  2>&1
pp -v 99 -o use-mojo-n_-x.exe  use-mojo.pl  -n -x   >log-use-mojo-n_-x
+.exe.txt  2>&1
pp -v 99 -o use-mojo-x.exe  use-mojo.pl  -x   >log-use-mojo-x.exe.txt 
+ 2>&1
pp -v 99 -o use-mojo-c.exe  use-mojo.pl  -c   >log-use-mojo-c.exe.txt 
+ 2>&1
[download]

Now regarding error script: No such file or directory at Mojo/Home.pm line 25 This is line 25 of Mojo/Home.pm

  # Environment variable
  if ($ENV{MOJO_HOME}) {
    my @parts = File::Spec->splitdir(abs_path $ENV{MOJO_HOME});
    $self->{_parts} = \@parts;
    return $self;
  }
[download]

So there is line number confusion.

Using

require Mojolicious::Lite;
[download]

seems to remedy this situation. Oddly BEGIN { eval "use Mojolicious::Lite;" } also works.

Thats bizzare, you should submit a bug report :)

Comment on Re: Building a Mojolicious app with PAR::Packer Select or Download Code

Replies are listed 'Best First'.
Re^2: Building a Mojolicious app with PAR::Packer by Hue-Bond (Priest) on Feb 25, 2011 at 16:31 UTC
All of `-n -x`, `-x` and `-c` do the trick and take me to the `Mojo/Home.pm line 25` error. I hadn't noticed that the error was precisely in that file: as soon as you pointed it out I remembered that the test `t/mojo/home.t` had failed before the (forced) installation. Thankfully, Google has something to say about it so I'll now concentrate on that. Thank you! -- David Serrano (Please treat my english text just like Perl code, i.e. feel free to notify me of any syntax, grammar, style and/or spelling errors. Thank you!).	[reply] [d/l] [select]
Re^3: Building a Mojolicious app with PAR::Packer by Hue-Bond (Priest) on Feb 26, 2011 at 23:12 UTC
No line number confusion: `abs_path` was dying. Turns out that the failing test had nothing to do with it - the problem is caused due to an interference with PAR's runtime environment. Prepending a bit of code to the main script works around the problem: `use File::Spec; BEGIN { if ($ENV{'PAR_TEMP'}) { my $dir = File::Spec->catfile ($ENV{'PAR_TEMP'}, 'inc'); chdir $dir or die "chdir: '$dir': $!"; } }` [download] We go to the parent directory of `script` so now it's properly detected. -- David Serrano (Please treat my english text just like Perl code, i.e. feel free to notify me of any syntax, grammar, style and/or spelling errors. Thank you!).	[reply] [d/l] [select]
Re^4: Building a Mojolicious app with PAR::Packer by Anonymous Monk on Mar 02, 2012 at 13:30 UTC
Hello all. Did you alors experienced this kind of error messages with Mojo ? (Did'nt get rid of even while including or creating by hand the epl files) `Can't open file "Mojolicious\templates\exception.html.ep": No such fil +e or directory at Mojo/Home.pm line 119. Compilation failed in require at Mojolicious.pm line 6. BEGIN failed--compilation aborted at Mojolicious.pm line 6. Compilation failed in require at Mojo/Base.pm line 32.` [download]	[reply] [d/l]
Re^4: Building a Mojolicious app with PAR::Packer by Anonymous Monk on Mar 02, 2012 at 13:53 UTC
Hello all. Did you also experience this kind of error messages with Mojo ? (Did'nt get rid of even while including or creating by hand the epl files) `Can't open file "Mojolicious\templates\exception.html.ep": No such fil +e or directory at Mojo/Home.pm line 119. Compilation failed in require at Mojolicious.pm line 6. BEGIN failed--compilation aborted at Mojolicious.pm line 6. Compilation failed in require at Mojo/Base.pm line 32.` [download]	[reply] [d/l]
Re^5: Building a Mojolicious app with PAR::Packer by jfbaillette (Initiate) on Mar 03, 2012 at 19:46 UTC


Your skill will accomplish what the force of many cannot
	PerlMonks