Welcome to the Embedthis Ejscript™ installation release notes. This document provides release-specific information for Ejscript.
This software is copyrighted and distributed under license. It is available under a GPLv2 open source license and an optional commercial license. Please read the LICENSE.md for details.
Ejscript includes support for several external packages such as OpenSSL and SQLite. These packages have their own licenses. Make sure you check the packages license details to ensure you are complying with their licenses.
Binary releases are supplied for the following operating systems.
- Windows (Windows-7,8)
- MAC OS X (Lion x64)
The following operating systems may be supported by recompiling Ejscript from source.
- Linux 2.4 and 2.6
- VxWorks 6.X
- Windows 7 and later
- Mac OSX 10.9 and later
The following CPU architectures are supported: arm, mips, ppc, xscale, x86, x64, sparc.
Run-time System Requirements
To install Ejscript on a development system and run Ejscript programs, your system will need at least the following:
- 40 MB Disk
- 1 GB RAM
To deploy Ejscript in an embedded environment, you will need at least the following:
- 1-2 MB Disk / ROM space
- 2-4 MB RAM
To rebuild Ejscript from source code, you will need at least
- 60 MB disk space
Build and Tool Requirements
If you are building the software from source or using Expansive to render web applications you may require:
- MakeMe version 0.8.6 or later to build with MakeMe.
- Pak version 0.10.0 or later to install packages.
- Expansive version 0.5.0 or later to render web sites.
Development Environment Hardware Platform Support
If you wish to build Ejscript from source code, you will need to use a C compiler and associated development tools. Several development environments are supported. You may choose any of the following to compile and build samples and source code.
- UNIX/Linux GNU tools
- Mac Xcode 6.4 and later.
- Windows Visual Studio 2013 and later.
- WindRiver Tornado Development Tools.
Debug Trace and Logging
Ejscript has a debug logging and trace facility that can help when debugging configuration issues or developing your application code that uses Ejscript. You can see each script statement as it is executed and what byte codes the VM is executing. You can vary the level of logging via the --log logfile command line switch for the ejs command. The log command line switch has the format
ejs --log logFile:logLevel
The log level can be from 0 to 9, with 9 being the most verbose level. If compiling your scripts with debug enabled via the --debug switch, a log level setting of 5 will trace each source statement and assembly byte code to the log file.