Sample Page Title

Beneath is a concise information to get KnitPkg engaged on Linux: first set up, then configuration.

1. Putting in KnitPkg on Linux (by way of Wine)

1.1. Stipulations

Earlier than putting in KnitPkg on Linux, you want: 

• Wine with a working MetaTrader 5 and/or MetaTrader 4 put in inside a Wine prefix
  (in case you adopted any normal “MetaTrader 5 on Linux by way of Wine” information, you must have already got this).
• Git shopper put in and in your PATH.

1.2. Obtain the Linux binary

Obtain the newest Linux  kp  binary from the KnitPkg GitHub Releases web page and place it in a folder you management, for instance: 

mkdir -p ~/bin/knitpkg
mv /path/to/downloaded/kp ~/bin/knitpkg/
chmod +x ~/bin/knitpkg/kp

1.3. Set atmosphere variables

Add these traces to your shell profile (e.g.  ~/.bashrc ,  ~/.zshrc ): 

export WINEPREFIX=/residence/<person>/.mt5
export PATH="$PATH:/residence/<person>/bin/knitpkg"

• WINEPREFIX  should level to the Wine prefix the place MetaTrader is put in.
• Add the folder containing  kp  to  PATH  so you may name  kp  from any terminal.

Reload your shell:

supply ~/.bashrc # or supply ~/.zshrc

Run:

If the command runs and prints a model, your Linux KnitPkg binary is accurately put in.

You may also set up by way of PyPI ( pip set up knitpkg-mt ) on Linux, however the Wine + MetaEditor configuration nonetheless applies when compiling. 

2. Configuring KnitPkg on Linux

KnitPkg must know the place your MetaEditor compiler is and the place your MetaTrader information folder is. There are three configuration layers, in descending order of precedence: 

1. Atmosphere variables
2. Venture‑particular config ( .knitpkg/config.yaml  inside your challenge)
3. World config ( ~/.knitpkg/config.yaml  in your house listing)

If one thing isn’t configured, KnitPkg falls again to default values and a few auto‑detection, however for Linux+Wine it’s higher to configure issues explicitly.

2.1. What have to be configured

At minimal, configure: 

• MQL5 compiler path (MetaEditor executable)
• MQL5 information folder (MetaTrader 5 information folder, containing the  MQL5  listing / Customary Library)

The identical applies for MQL4 if you’re utilizing MT4 tasks.

On Linux, the defaults seem like this (inside your Wine prefix): 

In case your set up paths differ, you have to override them.

Essential: on Linux, all the time use POSIX paths (with ahead slashes) when configuring KnitPkg, even for paths contained in the Wine prefix. 

2.2. Venture‑particular configuration ( kp config )

From inside a KnitPkg challenge listing, you may configure settings only for that challenge:

kp config --mql5-compiler-path "/residence/<person>/.mt5/drive_c/Program Recordsdata/MetaTrader 5/MetaEditor64.exe"
kp config --mql5-data-folder-path "/residence/<person>/.mt5/drive_c/Program Recordsdata/MetaTrader 5"

• Completely different tasks use totally different MetaTrader installations or variants.
• You need challenge‑degree isolation of configuration.

2.3. World configuration ( kp globalconfig )

To configure defaults for all KnitPkg tasks in your system, use:

kp globalconfig --mql5-compiler-path "/residence/<person>/.mt5/drive_c/Program Recordsdata/MetaTrader 5/MetaEditor64.exe"
kp globalconfig --mql5-data-folder-path "/residence/<person>/.mt5/drive_c/Program Recordsdata/MetaTrader 5"

kp globalconfig --mql4-compiler-path "/residence/<person>/.mt4/drive_c/Program Recordsdata/MetaTrader 4/metaeditor.exe"
kp globalconfig --mql4-data-folder-path "/residence/<person>/.mt4/drive_c/Program Recordsdata/MetaTrader 4"

export MQL5_COMPILER_PATH="/residence/<person>/.mt5/drive_c/Program Recordsdata/MetaTrader 5/MetaEditor64.exe"
export MQL5_DATA_FOLDER_PATH="/residence/<person>/.mt5/drive_c/Program Recordsdata/MetaTrader 5"

# Allow telemetry globally
kp telemetry on

3. Abstract

• kp  now runs natively on Linux; Wine is simply used to invoke MetaEditor for MQL compilation. 
• Set up on Linux consists of:
  • Having Wine + MetaTrader put in in a Wine prefix.
  • Downloading the Linux  kp  binary, making it executable, and including it to your  PATH .
  • Setting  WINEPREFIX  so KnitPkg is aware of which Wine atmosphere to make use of.
• Configuration is finished by means of:
  • kp config  (per‑challenge)
  • kp globalconfig  (world defaults)
  • Atmosphere variables (highest precedence)

As soon as that is arrange, you may work in your EA/indicator/utility tasks on Linux virtually precisely as on Home windows:

kp init
kp set up
kp compile