MERGEPEF(1) BSD General Commands Manual MERGEPEF(1)NAME
/usr/bin/MergePef -- Merge multiple PEF containers into one file
/usr/bin/MergePef [-v] [-t type] [-c creator] <input-file> ... -o <output-file>
The /usr/bin/MergePef command reads all input files, interpreting them as PowerPC Executable Format (PEF) container files. It combines the
files into one PEF containter and writes it to the output file. MergePEF does not read Standard Input and will not write Standard Output.
The /usr/bin/MergePef command accepts the following arguments:
-v Produce verbose diagnostics to standard output.
-t type Set the Extended HFS file type of the output file. The default value is 'shlb'.
-c creator Set the Extended HFS file creator of the output file. The default value is 'MACS'.
<input-file> One or more paths to PEF file containers.
Path to the output file.
The PEF container format is supported on Mac OS X by the Carbon runtime libraries, but is not the preferred executable format on Mac OS X.
There are no developer tools to create PEF containers natively on Mac OS X.
SEE ALSO LaunchCFMApp(1)Mac OS X April 12, 2004 Mac OS X
Check Out this Related Man Page
OSACOMPILE(1) BSD General Commands Manual OSACOMPILE(1)NAME
osacompile -- compile AppleScripts and other OSA language scripts
osacompile [-l language] [-e command] [-o name] [-d] [-r type:id] [-t type] [-c creator] [-x] [-s] [-u] [-a arch] [file ...]
osacompile compiles the given files, or standard input if none are listed, into a single output script. Files may be plain text or other
compiled scripts. The options are as follows:
Override the language for any plain text files. Normally, plain text files are compiled as AppleScript.
Enter one line of a script. Script commands given via -e are prepended to the normal source, if any. Multiple -e options may be given
to build up a multi-line script. Because most scripts use characters that are special to many shell programs (e.g., AppleScript uses
single and double quote marks, ``('', ``)'', and ``*''), the command will have to be correctly quoted and escaped to get it past the
Place the output in the file name. If -o is not specified, the resulting script is placed in the file ``a.scpt''. The value of -o
partly determines the output file format; see below.
-x Save the resulting script as execute-only.
The following options are only relevant when creating a new bundled applet or droplet:
-s Stay-open applet.
-u Use startup screen.
Create the applet or droplet for the specified target architecture arch. The allowable values are ``ppc'', ``i386'', and ``x86_64''.
The default is to create a universal binary.
The following options control the packaging of the output file. You should only need them for compatibility with classic Mac OS or for cus-
tom file formats.
-d Place the resulting script in the data fork of the output file. This is the default.
Place the resulting script in the resource fork of the output file, in the specified resource.
Set the output file type to type, where type is a four-character code. If this option is not specified, the creator code will not be
Set the output file creator to creator, where creator is a four-character code. If this option is not specified, the creator code will
not be set.
If no options are specified, osacompile produces a Mac OS X format script file: data fork only, with no type or creator code.
If the -o option is specified and the file does not already exist, osacompile uses the filename extension to determine what type of file to
create. If the filename ends with ``.app'', it creates a bundled applet or droplet. If the filename ends with ``.scptd'', it creates a bun-
dled compiled script. Otherwise, it creates a flat file with the script data placed according to the values of the -d and -r options.
To produce a script compatible with classic Mac OS:
osacompile -r scpt:128 -t osas -c ToyS example.applescript
SEE ALSO osascript(1), osalang(1)Mac OS X November 12, 2008 Mac OS X