Echelon Neuron C - Manual (Page 226)

214 Neuron C Tools Stand-Alone Use
--basename=23305
Most tools require additional arguments to be given; these arguments can appear
at any location within the command line or in a separate line within a script.
Example of argument at end of command line:
C:\>NCC - -define=MYMACRO mycode.nc
Common Set of Basic Commands
In addition to the shared syntactical aspects introduced in the previous section,
the stand-alone tools also share a common set of basic commands. Some of these
common commands are listed below. To obtain a complete list of all available
commands, you can type in the name of any of the stand-alone tools without
specifying any command.
-@ file-pathname (Include a command file)
The -@ (or: - -file) command specifies a command file (script). The commands are
read from this script and used as if they were given at the command line and in
the location of the @ command. Scripts themselves can refer to other scripts.
- -defloc dir (Location of an optional default command file)
The command line tools also search for a default script; a file that is read in
addition to and after all other commands from the command line have been
processed. These default script files need not be specified with the -@ command,
because they have a predefined name shown in Table 16. The command line tool
assumes that the default script is located in the current working directory (and it
is no error if there is none); the - -defloc
command can be used to specify the
location ( not name) of the default script. The NodeBuilder Development Tool
uses the location of the NodeBuilder device template file (.nbdt extension) as the
location of the default script.
Table 16. Default Script Names for the Stand-Alone Tools
Build Tool Command Name Default Script Name
Neuron C Compiler NCC LonNCC32.def
Neuron Assembler NAS LonNAS32.def
Neuron Linker NLD LonNLD32.def
Neuron Exporter NEX LonNEX32.def
Neuron Librarian NLIB LonLIB32.def
- -mkscript scriptfile (Generate command script in scriptfile )
The - -mkscript command produces a trace file that contains all commands the
build tool received, no matter where these commands came from. When used
within a default script, this feature can be used to capture the command
sequence used by the project manager; a simple way to obtain machine-generated
build scripts.