start_erl

19982016 Ericsson AB. All Rights Reserved. Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. start_erl Patrik Nyblom 1998-08-05 start_erl.xml

start_erl Start Erlang for embedded systems on Windows systems.

The program is specific to Windows NT/2000/XP (and later versions of Windows). Although there are programs with the same name on other platforms, their functionality is different.

This program is distributed both in compiled form (under <Erlang root>\\erts-<version>\\bin) and in source form (under <Erlang root>\\erts-<version>\\src). The purpose of the source code is to ease customization of the program for local needs, such as cyclic restart detection. There is also a "make"-file, written for the program distributed with Microsoft Visual C++. This program can, however, be compiled with any Win32 C compiler (possibly with minor modifications).

This program aids release handling on Windows systems. The program is to be called by the program, read up the release data file start_erl.data, and start Erlang. Some options to start_erl are added and removed by the release handler during upgrade with emulator restart (more specifically option ).

start_erl [<erl options>] ++ [<start_erl options>] Start the Erlang emulator with the correct release data.

The program in its original form recognizes the following options:

Mandatory. Delimits start_erl options from normal Erlang options. Everything on the command line before is interpreted as options to be sent to the program. Everything after is interpreted as options to itself.

-reldir <release root>

Mandatory if environment variable is not specified and no -rootdir option is specified. Tells start_erl where the root of the release tree is located in the file system (typically <Erlang root>\\releases). The file is expected to be located in this directory (unless otherwise specified). If only option -rootdir is specified, the directory is assumed to be <Erlang root>\\releases.

-rootdir <Erlang root directory>

Mandatory if -reldir is not specified and no exists in the environment. This specifies the Erlang installation root directory (under which the lib, releases, and erts-<Version> directories are located). If only -reldir (or environment variable ) is specified, the Erlang root is assumed to be the directory exactly one level above the release directory.

-data <data file name>

Optional. Specifies another data file than start_erl.data in the <release root>. It is specified relative to the <release root> or absolute (including drive letter, and so on). This option is used by the release handler during upgrade and is not to be used during normal operation. Normally the release data file is not to be named differently.

-bootflags <boot flags file name>

Optional. Specifies a file name relative to the release directory (that is, the subdirectory of <release root> where the file and others are located). The contents of this file is appended to the command line when Erlang is started. This makes it easy to start the emulator with different options for different releases.

Notes

As the source code is distributed, it can easily be modified to accept other options. The program must still accept option with the semantics described above for the release handler to work correctly.

The Erlang emulator is found by examining the registry keys for the emulator version specified in the release data file. The new emulator must be properly installed before the upgrade for this to work.

Although the program is located together with files specific to the emulator version, it is not expected to be specific to the emulator version. The release handler does not change option to during emulator restart. Locate the (possibly customized) program so that it is not overwritten during upgrade.

The default options of the program are not sufficient for release handling. The machine started by is be specified as the program and the arguments are to contain followed by the desired options.