archive-gh-me/jerryscript
1
0
Fork 0
mirror of https://github.com/jerryscript-project/jerryscript.git synced 2025-12-15 16:29:21 +00:00
Code Issues Projects Releases Wiki Activity
jerryscript/01.GETTING-STARTED.md
Istvan Kadar c0978d1a42 Updated content on the JerryScript GitHub Pages site 
- API refenrece is updated.
- API examples are updated.
- How To page renamed to Getting Started.
- Fixes in Internlas.

JerryScript-DCO-1.0-Signed-off-by: István Kádár ikadar@inf.u-szeged.hu
2016-07-13 13:33:46 +02:00

1.5 KiB
Raw Blame History

layout title permalink
page Getting Started /getting-started/
  • toc {:toc}

Setting Up Prerequisites

Currently, only Ubuntu 14.04+ is officially supported as primary development environment.

There are several dependencies, that should be installed manually. The following list is required for building:

  • gcc higher than 4.8.2
    • native
    • arm-none-eabi
  • cmake higher than 2.8.12.2
  • make higher than 3.81
  • bash higher than 4.3.11
  • cppcheck higher than 1.61
  • vera++ higher than 1.2.1
sudo apt-get install gcc g++ gcc-arm-none-eabi cmake cppcheck vera++

To make our scripts run correctly, several shell utilities should be available on the system:

  • find
  • bc
  • awk
  • sed
  • sha256sum
  • wget

Upon first build, make would try to setup prerequisites, required for further development and pre-commit testing:

  • STM32F3 and STM32F4 libraries
make prerequisites -j

It may take time, so go grab some coffee:

Setting up prerequisites... (log file: ./build/prerequisites/prerequisites.log)

Building Debug Version

To build debug version for Linux:

make debug.linux -j

To build debug version for Linux without LTO (Link Time Optimization):

LTO=OFF make debug.linux -j

Checking Patch

make precommit -j

If some style guidelines, build or test runs fail during precommit, then this is indicated with a message like this:

Build failed. See ./build/bin/unittests/make.log for details.