Hi Johannes,
Johannes Kilian schrieb:
My question is probably a beginners question - but
> I cannot figure it out yet.
Not really. :)
I use the following command-line to generate my PAR-File:
pp -B --lib D:\lib -p -o test.par test.pl
My dependencies and lib directory are quite large (about 100
> own modules in D:\lib) - so the resulting PAR File is about
> 5.0MB large.
Unrelated to your other problems which I can't try to debug right now, I
would suggest the following:
- > d:
- > perl -MPAR::Dist -e "generate_blib_stub(name => 'MyLibs', version =>
'1.00')"
- copy D:\lib to D:\blib\lib
- > perl -MPAR::Dist -e "blib_to_par"
- You should have MyLibs-1.00-MSWin32-x86-thread-multi-5.8.8.par or
similar in D:\
- Possibly delete D:\META.yml and D:\blib
Why not pp? Because you seem to want to package all that's in D:\lib. If
that's not the case, use pp. The approach outlined above skips the
dependency scanning which pp normally performs. It's basically just
making a ZIP file (with .par extension) from your lib. The
generate_blib_stub step just generates the META.yml (and creates the
blib dir). Since the .par will contain everything below "blib"
(excluding the "blib" directory itself), you could get away by just
creating a ZIP of the lib directory. But you would lose any meta info.
Does that make sense?
Cheers,
Steffen
