Environment Setup

Before building with PARA or running the runtime, source the para-env-setup.sh script at the SDK root into your current shell to configure the environment.

Usage

The script must be sourced (not executed). If you run it without sourcing, the script aborts on its own.

cd /path/to/para-sdk
. ./para-env-setup.sh

It is written to work in sh/bash/zsh. If you invoke it the wrong way (such as running it directly like ./para-env-setup.sh), it aborts with the message Error: This script must be sourced. Please run it as '. ...'.

On success, the following notice is printed.

PARA environment setup completed. You may proceed with the following:
- Build the PARA Adaptive Application project
- Ensure $PARA_CONF, $PARA_DATA, and $PARA_APPL are set correctly
- Run PARA with 'EM'

Environment Variables That Are Set

The script determines PARA_SDK based on its own location, then sets the variables needed to run the runtime.

Variable	Value	Purpose
PARA_SDK	SDK root	SDK location
PARA_CORE	SDK root	Runtime core root
PARA_CONF	$PARA_CORE/etc	Configuration / manifest directory
PARA_DATA	$PARA_CORE/var	Runtime mutable data
PARA_APPL	$PARA_CORE/opt	Deployed applications
PATH	$PARA_CORE/bin appended	Daemon and tool execution path
PKG_CONFIG_PATH	$PARA_SDK/external/lib/pkgconfig appended	Third-party pkg-config

Note that in a freshly extracted SDK, etc/ and opt/ do not yet contain machine/app manifests, so launching EM directly does nothing meaningful. First build and install the example Machine, then launch the runtime with the generated para-exec.sh wrapper — see Build with CMake.

Verifying the Environment

You can verify that the configuration was applied with the following.

echo "$PARA_SDK"      # SDK root path is printed if correct
command -v EM         # check that EM in bin/ is visible on PATH