Have a coffe/tea/water break, then read Behind the GUI lives the Shell and the docs again

I usually use something like this 

#!/usr/bin/perl --
use strict; use warnings;
system
'pp', '-x',
'satin.pl',
'-o', 'satin.exe',
'-N', 'LegalTrademarks=dLegalTrademarks',
'-N', 'Comments=dComments',
'-N', 'FileVersion=0.6.6.6',
'-N', 'ProductVersion=0.6.6.6',
'-N', 'OriginalFilename=satin.pl',
'-N', 'InternalName=satin.exe',
'-N', 'FileDescription=dFileDescription',
'-N', 'LegalCopyright=dLegalCopyright',
'-N', 'CompanyName=Satin',
'-N', 'ProductName=Satin',
;

[download]

Though there are WinXP problems Bug #69570 for Win32-Exe: create_resource_section() fails

I don't know if http://www.cavapackager.com/ has the same problem, oh well

In reply to Re^3: How to add file version to a executable made from Perl script ? by Anonymous Monk
in thread How to add file version to a executable made from Perl script ? by samta

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.