# Build the TelAF simulation in the docker container 

Source: [https://docs.qualcomm.com/doc/80-41102-1/topic/build-the-telaf-simulation-in-the-docker-container.html](https://docs.qualcomm.com/doc/80-41102-1/topic/build-the-telaf-simulation-in-the-docker-container.html)

Users can compile the TelAF simulation project in their own dev HOST PC. It's fine for
            one proper development environment after some setup steps.

However, it's recommended to do the compilation in TelAF Develop Container. This can make
            sure the environment is consistent.

There are two files that users can be used to simplify the compilation steps.

1. **simulation/.simulation.build**
2. **simulation/workstation/.simula.dev.action.sh**

File **simulation/.simulation.build** includes **make-syntax** and enable different
            options to do the compilation.

For
            example:

    # Content in simulation/.simulation.build
    
    export IMPORT_SDK_SIMULATION = y
    export sdk_rootfs=/path/to/sdk/rootfs
    
    export TELAF_SIMULATION_ENABLE_SMS = y
    export TELAF_SIMULATION_ENABLE_DCS = y
    export TELAF_SIMULATION_ENABLE_SIM = y
    export TELAF_SIMULATION_ENABLE_LOC = y
    export TELAF_SIMULATION_ENABLE_MNGD_CONN = y
    export TELAF_SIMULATION_ENABLE_SOMEIP_GW = yCopy to clipboard

It's the same as (but not recommend):

    make simula-c \
    IMPORT_SDK_SIMULATION=y \
    sdk_rootfs=/path/to/sdk/rootfs  \
    TELAF_SIMULATION_ENABLE_SMS =y \
    TELAF_SIMULATION_ENABLE_DCS=y \
    TELAF_SIMULATION_ENABLE_SIM=y \
    TELAF_SIMULATION_ENABLE_LOC=y \
    TELAF_SIMULATION_ENABLE_MNGD_CONN=y \
    TELAF_SIMULATION_ENABLE_SOMEIP_GW=yCopy to clipboard

File simulation/workstation/.simula.dev.action.sh includes shell
            commands as the shell scripts do something in the develop container.

For
            example:

    # Content in simulation/workstation/.simula.dev.action.sh
     
    make simula-c
     
    # for SDK project: 'cd ../sdk && ./build_sim.sh setup && ./build_sim.sh rootfs'Copy to clipboard

Thus, to build the TelAF simulation project, use following
            commands:

    cd simulation_env/telaf
    
    # create and modify the simulation/.simulation.build as you want
    # example:
    cat >> simulation/.simulation.build << EOF
    export IMPORT_SDK_SIMULATION = y
    export sdk_rootfs=/path/to/sdk/rootfs
    export TELAF_SIMULATION_ENABLE_SMS = y
    export TELAF_SIMULATION_ENABLE_DCS = y
    export TELAF_SIMULATION_ENABLE_SIM = y
    export TELAF_SIMULATION_ENABLE_LOC = y
    export TELAF_SIMULATION_ENABLE_MNGD_CONN = y
    export TELAF_SIMULATION_ENABLE_SOMEIP_GW = y
    EOF
    
    # create and modify the simulation/workstation/.simula.dev.action.sh as you want
    # example:
    echo "make simula-c" > simulation/workstation/.simula.dev.action.sh
    
    # build
    make simula-xCopy to clipboard

Note: Change the `sdk_rootfs=/path/to/sdk/rootfs` to the real path you have
            recorded.

sdk\_rootfs has the following limitations:
- sdk\_rootfs should be an absolute path; relative paths are invalid.
- sdk\_rootfs should be placed under the ‘simulation\_env' path, otherwise it won't
                    work. This is a slight difference that's introduced for using the Docker
                    container for building.

Along with SDK simulation, you need to enable some options for compilation, see
                `simulation.mk` for details.

**Parent Topic:** [Use TelAF simulation](https://docs.qualcomm.com/doc/80-41102-1/topic/use-telaf-simulation.html)

Last Published: Aug 06, 2026

[Previous Topic
Build SDK simulation project](https://docs.qualcomm.com/bundle/publicresource/80-41102-1/topics/build-sdk-simulation-project.md) [Next Topic
Deploy TelAF on the simulation environment](https://docs.qualcomm.com/bundle/publicresource/80-41102-1/topics/deploy-telaf-on-the-simulation-environment.md)