Command line interfaces

sdk.exe

The sdk.exe executable is a wrapper around epoc.exe and is intended for web content developers to easily test their content on the emulator or on a mobile device. It supports options and commands that you use in message content development. If you are developing message or browser content, you are more likely to use sdk.exe on the command line because with this executable you can work within a shell and arrange to have one instance of the SDK send a message to another instance. Options and commands that sdk.exe does not support cause the entire command to fail, and an error message to be posted.

sdk.exe is located in <S60_SDK_installation_directory>\epoc32\release\winscw\udeb.

The SDK command line interface (sdk.exe) enables web content developers to easily test their content on the emulator or on a device. This interface can be used to:

• Launch the emulator, view particular content in an already running emulator (for example an image) or launch a URL in the emulator.

• Send a URL to a mobile device and launch the browser with the URL. This command line interface relies on the Device Connectivity Tool for S60 SDK to provide connectivity between the PC and the mobile device.

sdk.exe will automatically launch the Device Connectivity Tool for S60 SDK - if it is not already running - for all the operation is in the device (see Introduction to diagnostics and tracing).

For syntax and arguments, see Sdk.exe syntax and arguments.

emulator.exe

Typically, an IDE that supports MIDlet development automatically uses emulator.exe when it uses the SDK as a device. A developer of MIDlets is unlikely to use emulator.exe on the command line to monitor the behavior of a MIDlet. The SDK ignores options and commands that emulator.exe does not support.

emulator.exe is the implementation of the Unified Emulator Interface Specification (UEI) 1.0.2.

emulator.exe is located in <S60_SDK_installation_directory>\bin\.

For syntax and arguments, see Emulator.exe syntax and arguments.