Table of Contents

Products, services and company names referenced in this document may be either trademarks or registered trademarks of their respective owners.

Copyright © 2017–2020 EVL Tool, s.r.o.

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, with no Front-Cover Texts, and with no Back-Cover Texts.


EVL installation resides (usually) in


To initiate EVL for current user, run

/opt/EVL-2.4/bin/evl init

which add an .evlrc file into your $HOME folder and add sourcing it into $HOME/.bashrc.

Then one can check, add or modify some settings in .evlrc, for example variable EVL_ENV. These settings are top level settings for given user. (Later there are project.sh files in each project, to set project-wide variables.)

After that EVL is ready to use. Good to start is to create new project with some sample data, jobs and workflows:

evl project sample my_first_sample


Mappings are compiled either by GCC or Clang. It depends on environment variable EVL_COMPILER, these two values are possible:


If this variable is not set, then on Linux systems is GCC by default, and on Windows and Mac it is Clang.

GCC must be at least in the version 7.4 and Clang at least 6.0.

When Clang would be the option, one can replace gcc/c++ packages by clang above in installation instructions.


EVL project is a directory with EVL jobs, workflow, data structure definitions, mappings, etc. Each project is intended for a group of jobs and workflows which are grouped somehow from the business point of view. So completely unrelated processings, which share nothing, would be good to place in separate projects.


Each project has project.sh file inside. This file contains project-wide settings. If the project is created by evl project new or by evl project sample command, then project.sh would contain a good set of variables to start with.

Path to log and tmp folders are handled by environment variables:


path to folder where log files are stored,


path to folder where temporary files are stored.

By default are these variables set to:


These values can be override in project.sh file.

Project directory structure

In each project directory, there would be these files and folders:


contains subdirectories of compiled components of each job (one subfolder equals to one evl file).


generated and/or custom documentation of the project.


EVL custom component definition files.


EVL data definition files.


EVL job structure files (job definition itself, sometimes called a graph of ETL process).


EVL mapping files for components Aggreg, Join and Map.


EVL workflow structure files.


files, called by evl run command, which specify the variables for the job structure, i.e. it contains parameters of the job described by evs file.


EVL workflow parameter files for ews files.


This file is interpreted as bash shell script at the beginning of each job in the project. Usually contains all project wide variables.