SDP(1) | General Commands Manual | SDP(1) |
sdp
— scripting
definition (sdef) processor
sdp |
-f {ahst}
[-o directory | file]
[options...] [file] |
sdp
transforms a scripting definition
(“sdef”) file, or standard input if none is specified, into a
variety of other formats for use with a scriptable application. The options
are as follows:
-f
formath
You do not need to create a corresponding implementation file; Scripting Bridge will create the class implementations at runtime.
Use these when you want to create a scriptable application:
a
s
t
These formats are only necessary when creating a scriptable application that will run on Mac OS X 10.4 (Tiger) or earlier; as of 10.5 (Leopard),an application may use only an sdef.
-o
directory | filesdp
may
generate several files.-
” writes all the output to
standard output. If multiple files are generated, all of them will be
written to the same file; this is usually not a good idea.The default is ‘-o
.
’, that is, generate automatically named
files in the current directory.
-A
,
--hidden
-V
version-V 10.10
. The default is to set the compatibility
version based on the environment variable
SDK_NAME
, which Xcode sets based on the
“Base SDK” build setting, or if that is not defined, to
assume the current system version.
-fs
) output for certain
features unsupported in Cocoa Scripting at that time.-N
name, --basename
name--basename iTunes
would result
in a header file “iTunes.h” defining a
iTunesApplication
class.-i
includefilesdp
's error reporting leaves much to be
desired. It does not provide line numbers for errors, though it will
describe the element. It will not warn you of certain types of mistakes,
such as using two different names with the same code (or vice versa), and
will return a zero status even for erroneous input.
July 12, 2007 | Mac OS X |