-a
option.
The syntax is like this:
wic arc -a {pckno [-r] [-cdir] filemask...}... [-uexe | -U[+]]
This is slightly complex, but flexible. The parameters are:
arc
.WPI
,
unless -u
or -U
are also used -- see below).
pckno
{...}
in the above
syntax). This must be specified as a
decimal number and match the INDEX
attribute of the respective
PCK
tag in the script.
Whenever WIC encounters a standalone decimal number in the
command line, it assumes that the following parameters affect the package
with that number (starting a new package block). There must be at least
one package block in the command line, but you can specify several to have
several packages created at once.
-r
filemask
).
This can only appear after a pckno
has been specified and will
only affect that package block, that is, for the next pckno
, recursion
will be disabled again.
-cdir
dir
for the current package block
before collecting the files according to filemask
.
This directory can either be a subdirectory or an absolute path
specification (anything that would be valid with the CD
command).
This is useful for creating archives with several packages from several subdirectories.
This can only appear after a pckno
has been specified and will
only affect that package block. For each package block, WIC
will start from the current directory (which WIC was started from) again.
So for each package, dir is considered to be relative to the current directory.
See Examples for more.
filemask
?
and *
wildcards and thus works just
like with the DIR
command.
This can only appear after a pckno
has been specified.
There must be at least one filemask
per package block, but you
can specify several per package, e.g. *.exe *.dll
.
-uexe
-U[+]
-u
nor -U
are specified, a plain
WPI archive is created.
-uexe
is specified, WIC will use exe
as the executable stub for the archive and thus turn the WPI file into a
self-installing executable. Unless you know how to write your own proper executable
stub for self-installing archives, you should always specify
the full path to STUB.EXE
from your WarpIN installation directory.
This produces the first self-installing executable type described on the "Self-installing archives" page.
-U
parameter can be used alternatively as a shortcut.
WIC will then automatically use
STUB.EXE
from your WarpIN installation directory and automatically
add a minimum set of WarpIN's own files to the special package index 30000
to allow for installation of the archive even on systems where WarpIN is not
installed. This will not include a full WarpIN installation though.
This produces the "minimal WarpIN" type described on the "Self-installing archives" page.
-U+
is specified instead, in addition to the
package 30000 described above, the remaining WarpIN files will be added
to the special package index 30001.
This produces the "full WarpIN installation" type described on the "Self-installing archives" page.
Note that for a full WarpIN installation to actually install itself,
you will need to add corresponding PCK
tags
to the archive's install script.