### Install Application Executable

Source: https://github.com/hiddify/hiddify-next/blob/main/windows/CMakeLists.txt

Installs the main application executable to the specified runtime destination.

```cmake
install(TARGETS ${BINARY_NAME} RUNTIME DESTINATION "${CMAKE_INSTALL_PREFIX}"
  COMPONENT Runtime)
```

--------------------------------

### Install Git on Fedora

Source: https://github.com/hiddify/hiddify-next/wiki/How-to-contribute-to-this-project

Use this command to install the git-all package on Fedora Linux.

```bash
dnf install git-all
```

--------------------------------

### Install Git on Arch Linux

Source: https://github.com/hiddify/hiddify-next/wiki/How-to-contribute-to-this-project

Use this command to install the git-all package on Arch Linux.

```bash
pacman -Syu git-all
```

--------------------------------

### Install Hiddify-Core Shared Library

Source: https://github.com/hiddify/hiddify-next/blob/main/linux/CMakeLists.txt

Installs the Hiddify-Core shared library (`.so` file) into the library directory of the installation bundle. This is part of the Runtime component.

```cmake
install(FILES "../hiddify-core/bin/lib/hiddify-core.so" DESTINATION "${INSTALL_BUNDLE_LIB_DIR}"
  COMPONENT Runtime)
```

--------------------------------

### Define Installation Directories

Source: https://github.com/hiddify/hiddify-next/blob/main/windows/CMakeLists.txt

Sets the destination directories for installing data files and libraries within the application bundle.

```cmake
set(INSTALL_BUNDLE_DATA_DIR "${CMAKE_INSTALL_PREFIX}/data")
set(INSTALL_BUNDLE_LIB_DIR "${CMAKE_INSTALL_PREFIX}")
```

--------------------------------

### Install Git on Debian/Ubuntu

Source: https://github.com/hiddify/hiddify-next/wiki/How-to-contribute-to-this-project

Use this command to install the git-all package on Debian-based Linux distributions.

```bash
sudo apt-get install git-all
```

--------------------------------

### Install Bundled Plugin Libraries

Source: https://github.com/hiddify/hiddify-next/blob/main/linux/CMakeLists.txt

Iterates through a list of bundled plugin libraries and installs each one into the library directory of the installation bundle. This ensures all necessary plugin dependencies are included.

```cmake
foreach(bundled_library ${PLUGIN_BUNDLED_LIBRARIES})
  install(FILES "${bundled_library}"
    DESTINATION "${INSTALL_BUNDLE_LIB_DIR}"
    COMPONENT Runtime)
endforeach(bundled_library)
```

--------------------------------

### Install HiddifyCli Executable

Source: https://github.com/hiddify/hiddify-next/blob/main/linux/CMakeLists.txt

Installs the HiddifyCli executable to the root of the installation prefix. Specific file permissions are set to ensure proper execution.

```cmake
install(
  FILES "../hiddify-core/bin/HiddifyCli" 
  DESTINATION "${CMAKE_INSTALL_PREFIX}"
  PERMISSIONS OWNER_EXECUTE OWNER_WRITE OWNER_READ GROUP_EXECUTE GROUP_READ WORLD_EXECUTE WORLD_READ
  COMPONENT Runtime
)
```

--------------------------------

### Define Installation Paths for Bundle Data and Libraries

Source: https://github.com/hiddify/hiddify-next/blob/main/linux/CMakeLists.txt

Sets variables for the installation paths of data and library files within the application bundle. These paths are used in subsequent install commands.

```cmake
set(INSTALL_BUNDLE_DATA_DIR "${CMAKE_INSTALL_PREFIX}/data")
set(INSTALL_BUNDLE_LIB_DIR "${CMAKE_INSTALL_PREFIX}/lib")
```

--------------------------------

### Vless Proxy Configuration Example

Source: https://github.com/hiddify/hiddify-next/wiki/URL-Scheme

Example of a Vless proxy configuration using TLS and WebSocket.

```Proxy
# Vless
vless://25da296e-1d96-48ae-9867-4342796cd742@172.67.149.95:443?encryption=none&fp=chrome&host=vless.229feb8b52a0e7e117ea76f8b591bcb3.workers.dev&path=%2F%3Fed%3D2048&security=tls&sni=vless.229feb8b52a0e7e117ea76f8b591bcb3.workers.dev&type=ws#رایگان | VLESS | @Helix_Servers | US🇺🇸 | 0️⃣1️⃣
```

--------------------------------

### Set Installation Bundle Directory

Source: https://github.com/hiddify/hiddify-next/blob/main/linux/CMakeLists.txt

Defines the base directory for the application bundle during installation. If the installation prefix is default, it's set to the build bundle directory.

```cmake
set(BUILD_BUNDLE_DIR "${PROJECT_BINARY_DIR}/bundle")
if(CMAKE_INSTALL_PREFIX_INITIALIZED_TO_DEFAULT)
  set(CMAKE_INSTALL_PREFIX "${BUILD_BUNDLE_DIR}" CACHE PATH "..." FORCE)
endif()
```

--------------------------------

### Import Singbox Configuration

Source: https://github.com/hiddify/hiddify-next/wiki/URL-Scheme

Example of importing a Singbox configuration file from a URL.

```URL
hiddify://import/https://raw.githubusercontent.com/yebekhe/TelegramV2rayCollector/fe3637db4ece53e56ac99ea09dbefa34466f280f/singbox/sfasfi/mixLite.json
```

--------------------------------

### Example Deeplink for Import

Source: https://github.com/hiddify/hiddify-next/wiki/URL-Scheme

Demonstrates how to use the URL scheme for importing configurations directly via a deeplink.

```URL
hiddify://import/https://hiddify.com/autosub#name
```

```URL
hiddify://import/trojan://your_password@aws-ar-buenosaires-1.f1cflineb.com:443#name
```

--------------------------------

### Import Clash Configuration

Source: https://github.com/hiddify/hiddify-next/wiki/URL-Scheme

Example of importing a Clash configuration file from a URL.

```URL
hiddify://import/https://raw.githubusercontent.com/yebekhe/TelegramV2rayCollector/d6ce7b907eeb58abf503c283af192e7bc915d143/clash/mix.yml
```

--------------------------------

### VLESS Proxy Configuration Example

Source: https://github.com/hiddify/hiddify-next/wiki/URL-Scheme

Example of a VLESS proxy configuration, including security, TLS, and WebSocket settings.

```Proxy
# http_WS_direct_vless تست 
vless://64177752-4266-4e00-94e3-1b8ececc6623@ip.sslip.io:80?security=none&sni=ip.sslip.io&type=ws&alpn=http/1.1&path=/2LBLzR6NsjNkCN830caotU&host=ip.sslip.io&encryption=none&fp=chrome&headerType=None#http_WS_direct_vless_تست
```

--------------------------------

### VMess Proxy Configuration Example

Source: https://github.com/hiddify/hiddify-next/wiki/URL-Scheme

Example of a VMess proxy configuration with base64 encoded parameters.

```Proxy
# Vmess
vmess://eyJhZGQiOiI1MS4xNjEuMTMwLjE3MyIsImFpZCI6IjAiLCJhbHBuIjoiIiwiZnAiOiIiLCJob3N0IjoiIiwiaWQiOiJkNDNlZTVlMy0xYjA3LTU2ZDctYjJlYS04ZDIyYzQ0ZmRjNjYiLCJuZXQiOiJ0Y3AiLCJwYXRoIjoiIiwicG9ydCI6IjgwODAiLCJzY3kiOiJjaGFjaGEyMC1wb2x5MTMwNSIsInNuaSI6IiIsInRscyI6IiIsInR5cGUiOiJub25lIiwidiI6IjIiLCJwcyI6Ilx1MDYzMVx1MDYyN1x1MDZjY1x1MDZhZlx1MDYyN1x1MDY0NiB8IFZNRVNTIHwgQFdhdGFzaGlfVlBOIHwgQVVcdWQ4M2NcdWRkZTZcdWQ4M2NcdWRkZmEgfCAwXHVmZTBmXHUyMGUzMVx1ZmUwZlx1MjBlMyJ9
```

--------------------------------

### Install AOT Library (Non-Debug Builds)

Source: https://github.com/hiddify/hiddify-next/blob/main/linux/CMakeLists.txt

Conditionally installs the AOT (Ahead-Of-Time) library to the installation bundle. This is only performed for builds that are not of type 'Debug'.

```cmake
if(NOT CMAKE_BUILD_TYPE MATCHES "Debug")
  install(FILES "${AOT_LIBRARY}" DESTINATION "${INSTALL_BUNDLE_LIB_DIR}"
    COMPONENT Runtime)
endif()
```

--------------------------------

### Profile Information Example

Source: https://github.com/hiddify/hiddify-next/wiki/URL-Scheme

An example demonstrating how profile information like name, usage, total data, remaining days, and web page link are displayed. This format is used for user-facing profile details.

```text
پروفایل یک = <name>
usage=<download>+<upload> (if more than 80% of total :yellow,  more than 100% :red)
total=<total>
روزباقیمانه=relative date of <expire> (if less than 7 days: yellow, less than zero: red)
مشاهده= open browser with <profile-web-page-url>
```

--------------------------------

### Clean Build Bundle Directory on Install

Source: https://github.com/hiddify/hiddify-next/blob/main/linux/CMakeLists.txt

Ensures that the build bundle directory is clean before installation by recursively removing its contents. This is executed as a code component during the installation process.

```cmake
install(CODE "
  file(REMOVE_RECURSE \"${BUILD_BUNDLE_DIR}/\")
  " COMPONENT Runtime)
```

--------------------------------

### Deprecated URL Schemes for Installation

Source: https://github.com/hiddify/hiddify-next/wiki/URL-Scheme

These are deprecated methods for installing configurations or proxies via URL Scheme. They are provided for historical reference.

```URL
hiddify://install-sub?url=<encoded v2ray config URI>#<name>
```

```URL
hiddify://install-config?url=<encoded v2ray config URI>#<name>
```

```URL
hiddify://install-proxy?url=<encoded v2ray proxy share link>#<name>
```

--------------------------------

### Install Flutter Library

Source: https://github.com/hiddify/hiddify-next/blob/main/windows/CMakeLists.txt

Installs the main Flutter library file to the root of the application bundle's runtime destination.

```cmake
install(FILES "${FLUTTER_LIBRARY}" DESTINATION "${INSTALL_BUNDLE_LIB_DIR}"
  COMPONENT Runtime)
```

--------------------------------

### Install Bundled Plugin Libraries

Source: https://github.com/hiddify/hiddify-next/blob/main/windows/CMakeLists.txt

Installs any additional libraries bundled with plugins to the application's library directory.

```cmake
if(PLUGIN_BUNDLED_LIBRARIES)
  install(FILES "${PLUGIN_BUNDLED_LIBRARIES}"
    DESTINATION "${INSTALL_BUNDLE_LIB_DIR}"
    COMPONENT Runtime)
endif()
```

--------------------------------

### SSH Proxy Configuration Example

Source: https://github.com/hiddify/hiddify-next/wiki/URL-Scheme

Example of an SSH proxy configuration including user, password, server, and public/host keys.

```Proxy
# SSH
ssh://user:pass@server:22/?pk=pk&hk=hk
```

--------------------------------

### Install Cronet DLL

Source: https://github.com/hiddify/hiddify-next/blob/main/windows/CMakeLists.txt

Installs the libcronet.dll from the hiddify-core/bin directory to the application's library directory, renaming it explicitly.

```cmake
install(FILES "../hiddify-core/bin/libcronet.dll" DESTINATION "${INSTALL_BUNDLE_LIB_DIR}"
COMPONENT Runtime RENAME libcronet.dll)
```

--------------------------------

### Shadowsocks (ss) Proxy Configuration Example

Source: https://github.com/hiddify/hiddify-next/wiki/URL-Scheme

Example of a Shadowsocks proxy configuration with base64 encoded credentials and server details.

```Proxy
# ss
ss://Y2hhY2hhMjAtaWV0Zi1wb2x5MTMwNTp0T3dPeXZsWGlZNUFUSkFVT3BYTlBO@5.35.34.107:55990#%D8%B1%D8%A7%DB%8C%DA%AF%D8%A7%D9%86+%7C+SS+%7C+%40iP_CF+%7C+RU%F0%9F%87%B7%F0%9F%87%BA+%7C+0%EF%B8%8F%E2%83%A31%EF%B8%8F%E2%83%A3
```

--------------------------------

### VLESS Reality Proxy Configuration Example

Source: https://github.com/hiddify/hiddify-next/wiki/URL-Scheme

Example of a VLESS proxy configuration using the REALITY security protocol.

```Proxy
# Reality
vless://409f106a-b2f2-4416-b186-5429c9979cd9@54.38.144.4:2053?encryption=none&flow=&fp=chrome&pbk=SbVKOEMjK0sIlbwg4akyBg5mL5KZwwB-ed4eEE7YnRc&security=reality&serviceName=xyz&sid=&sni=discordapp.com&type=grpc#رایگان | REALITY | @EliV2ray | FR🇫🇷 | 0️⃣1️⃣
```

--------------------------------

### WireGuard Proxy Configuration Example

Source: https://github.com/hiddify/hiddify-next/wiki/URL-Scheme

Example of a WireGuard proxy configuration with private key, peer public key, and MTU settings.

```Proxy
#Wireguard
wg://[server]:222/?pk=[private_key]&local_address=10.0.0.2/24&peer_pk=[peer_public_key]&pre_shared_key=[pre_shared_key]&workers=[workers]&mtu=[mtu]&reserved=0,0,0
```

--------------------------------

### Trojan Proxy Configuration Example

Source: https://github.com/hiddify/hiddify-next/wiki/URL-Scheme

Example of a Trojan proxy configuration with TLS, WebSocket, and host settings.

```Proxy
# Trojan
trojan://your_password@aws-ar-buenosaires-1.f1cflineb.com:443?host=aws-ar-buenosaires-1.f1cflineb.com&path=%2Ff1rocket&security=tls&sni=aws-ar-buenosaires-1.f1cflineb.com&type=ws#رایگان | TROJAN | @VmessProtocol | RELAY🚩 | 0️⃣1️⃣
```

--------------------------------

### Install Hiddify Core DLL

Source: https://github.com/hiddify/hiddify-next/blob/main/windows/CMakeLists.txt

Installs the hiddify-core.dll from the hiddify-core/bin directory to the application's library directory, renaming it explicitly.

```cmake
install(FILES "../hiddify-core/bin/hiddify-core.dll" DESTINATION "${INSTALL_BUNDLE_LIB_DIR}"
COMPONENT Runtime RENAME hiddify-core.dll)
```

--------------------------------

### Install Native Assets

Source: https://github.com/hiddify/hiddify-next/blob/main/linux/CMakeLists.txt

Copies native assets from the build directory to the installation bundle. This ensures that necessary native libraries are available at runtime.

```cmake
set(NATIVE_ASSETS_DIR "${PROJECT_BUILD_DIR}native_assets/linux/")
install(DIRECTORY "${NATIVE_ASSETS_DIR}"
   DESTINATION "${INSTALL_BUNDLE_LIB_DIR}"
   COMPONENT Runtime)
```

--------------------------------

### VMESS Proxy Configuration Example

Source: https://github.com/hiddify/hiddify-next/wiki/URL-Scheme

Example of a VMESS proxy configuration with various parameters including security, network type, and path.

```Proxy
# http_WS_direct_vmess تست 
vmess://64177752-4266-4e00-94e3-1b8ececc6623@ip.sslip.io:80?security=none&sni=ip.sslip.io&type=ws&alpn=http/1.1&path=/2LBLzR6NsjNkCN830caotU&host=ip.sslip.io&encryption=none&fp=chrome&headerType=None#http_WS_direct_vless_تست
```

--------------------------------

### Set Installation Prefix for Bundle

Source: https://github.com/hiddify/hiddify-next/blob/main/windows/CMakeLists.txt

Configures the installation prefix to be next to the executable, allowing the application to run in place. This is crucial for Visual Studio builds.

```cmake
set(BUILD_BUNDLE_DIR "$<TARGET_FILE_DIR:${BINARY_NAME}>")
set(CMAKE_VS_INCLUDE_INSTALL_TO_DEFAULT_BUILD 1)
if(CMAKE_INSTALL_PREFIX_INITIALIZED_TO_DEFAULT)
  set(CMAKE_INSTALL_PREFIX "${BUILD_BUNDLE_DIR}" CACHE PATH "..." FORCE)
endif()
```

--------------------------------

### Install Hiddify CLI Executable

Source: https://github.com/hiddify/hiddify-next/blob/main/windows/CMakeLists.txt

Installs the HiddifyCli.exe from the hiddify-core/bin directory to the application's root directory, renaming it explicitly.

```cmake
install(FILES "../hiddify-core/bin/HiddifyCli.exe" DESTINATION "${CMAKE_INSTALL_PREFIX}"
COMPONENT Runtime RENAME HiddifyCli.exe)
```

--------------------------------

### SSConfig Proxy Configuration Example

Source: https://github.com/hiddify/hiddify-next/wiki/URL-Scheme

Example of an SSConfig proxy configuration pointing to a JSON file on AWS S3.

```Proxy
# ssconfig
ssconf://s3.amazonaws.com/beedynconprd/ng4lf90ip01zstlyle4r0t56x1qli4cvmt2ws6nh0kdz1jpgzyedogxt3mpxfbxi.json#BeePass
```

--------------------------------

### Install AOT Library

Source: https://github.com/hiddify/hiddify-next/blob/main/windows/CMakeLists.txt

Installs the Ahead-Of-Time (AOT) compiled library to the data directory, but only for Profile and Release build configurations.

```cmake
install(FILES "${AOT_LIBRARY}" DESTINATION "${INSTALL_BUNDLE_DATA_DIR}"
  CONFIGURATIONS Profile;Release
  COMPONENT Runtime)
```

--------------------------------

### Install ICU Data File

Source: https://github.com/hiddify/hiddify-next/blob/main/windows/CMakeLists.txt

Installs the ICU data file to the data directory within the application bundle.

```cmake
install(FILES "${FLUTTER_ICU_DATA_FILE}" DESTINATION "${INSTALL_BUNDLE_DATA_DIR}"
  COMPONENT Runtime)
```

--------------------------------

### Hysteria1 Proxy Configuration Example

Source: https://github.com/hiddify/hiddify-next/wiki/URL-Scheme

Example of a Hysteria1 proxy configuration specifying protocol, authentication, and bandwidth limits.

```Proxy
# Hysteria1
hysteria://host:443?protocol=udp&auth=123456&peer=sni.domain&insecure=1&upmbps=100&downmbps=100&alpn=hysteria&obfs=xplus&obfsParam=123456#remarks
```

--------------------------------

### Example: Bale Messenger UDP Turn Relay Configuration

Source: https://github.com/hiddify/hiddify-next/wiki/How-to-use-UDP-Turn-Relay

An example of how to format the UDP Turn Relay parameters for the Bale messenger. This includes the username, password, host, port, and realm.

```text
relay=urlencoded(turn://balelivekit:GygZPHQSgAV7L5L8@meet-turn.bale.sh:443?realm=bale.ai)
```

--------------------------------

### Install Flutter Assets

Source: https://github.com/hiddify/hiddify-next/blob/main/windows/CMakeLists.txt

Removes the existing Flutter assets directory and then installs the current build's assets to the application's data directory.

```cmake
set(FLUTTER_ASSET_DIR_NAME "flutter_assets")
install(CODE "
  file(REMOVE_RECURSE \"${INSTALL_BUNDLE_DATA_DIR}/${FLUTTER_ASSET_DIR_NAME}\")
  " COMPONENT Runtime)
install(DIRECTORY "${PROJECT_BUILD_DIR}/${FLUTTER_ASSET_DIR_NAME}"
  DESTINATION "${INSTALL_BUNDLE_DATA_DIR}" COMPONENT Runtime)
```

--------------------------------

### TUIC Proxy Configuration Example

Source: https://github.com/hiddify/hiddify-next/wiki/URL-Scheme

Example of a TUIC proxy configuration with various parameters including UDP relay mode and SNI.

```Proxy
# TUIC
tuic://3618921b-adeb-4bd3-a2a0-f98b72a674b1:dongtaiwang@108.181.24.7:23450?allow_insecure=1&alpn=h3&congestion_control=bbr&sni=www.google.com&udp_relay_mode=native#رایگان | TUIC | @V2rayCollector | CA🇨🇦 | 0️⃣1️⃣
```

--------------------------------

### Example Hysteria2 Configuration

Source: https://github.com/hiddify/hiddify-next/wiki/How-to-use-UDP-Turn-Relay

A sample Hysteria2 configuration link that can be modified to include UDP Turn Relay parameters.

```text
hysteria2://87543215-15ac-54f6-3895-34e4e931f5b4@45.120.34.46:11464?hiddify=1&obfs=salamander&obfs-password=bdgf!huy678559j89GrTu&sni=www.speedtest.net&insecure=1#test
```

--------------------------------

### Import V2Ray Sublink (Normal Format)

Source: https://github.com/hiddify/hiddify-next/wiki/URL-Scheme

Example of importing a V2Ray subscription link in its normal format.

```URL
hiddify://import/https://raw.githubusercontent.com/yebekhe/TelegramV2rayCollector/fe3637db4ece53e56ac99ea09dbefa34466f280f/sub/normal/mix
```

--------------------------------

### Check Git Version

Source: https://github.com/hiddify/hiddify-next/wiki/How-to-contribute-to-this-project

Run this command in your terminal to verify the installed Git version.

```bash
git version
```

--------------------------------

### Import V2Ray Sublink (Base64 Format)

Source: https://github.com/hiddify/hiddify-next/wiki/URL-Scheme

Example of importing a V2Ray subscription link that is Base64 encoded.

```URL
hiddify://import/https://raw.githubusercontent.com/yebekhe/TelegramV2rayCollector/fe3637db4ece53e56ac99ea09dbefa34466f280f/sub/base64/mix
```

--------------------------------

### Flutter Library Setup

Source: https://github.com/hiddify/hiddify-next/blob/main/windows/flutter/CMakeLists.txt

Configures the Flutter library, including its DLL, ICU data file, and header files. It also sets project build directory and AOT library paths.

```cmake
# TODO: Move the rest of this into files in ephemeral. See
# https://github.com/flutter/flutter/issues/57146.
set(WRAPPER_ROOT "${EPHEMERAL_DIR}/cpp_client_wrapper")

# Set fallback configurations for older versions of the flutter tool.
if (NOT DEFINED FLUTTER_TARGET_PLATFORM)
  set(FLUTTER_TARGET_PLATFORM "windows-x64")
endif()

# === Flutter Library ===
set(FLUTTER_LIBRARY "${EPHEMERAL_DIR}/flutter_windows.dll")

# Published to parent scope for install step.
set(FLUTTER_LIBRARY ${FLUTTER_LIBRARY} PARENT_SCOPE)
set(FLUTTER_ICU_DATA_FILE "${EPHEMERAL_DIR}/icudtl.dat" PARENT_SCOPE)
set(PROJECT_BUILD_DIR "${PROJECT_DIR}/build/" PARENT_SCOPE)
set(AOT_LIBRARY "${PROJECT_DIR}/build/windows/app.so" PARENT_SCOPE)

list(APPEND FLUTTER_LIBRARY_HEADERS
  "flutter_export.h"
  "flutter_windows.h"
  "flutter_messenger.h"
  "flutter_plugin_registrar.h"
  "flutter_texture_registrar.h"
)
list(TRANSFORM FLUTTER_LIBRARY_HEADERS PREPEND "${EPHEMERAL_DIR}/")
add_library(flutter INTERFACE)
target_include_directories(flutter INTERFACE
  "${EPHEMERAL_DIR}"
)
target_link_libraries(flutter INTERFACE "${FLUTTER_LIBRARY}.lib")
add_dependencies(flutter flutter_assemble)
```

--------------------------------

### Check Flutter Version

Source: https://github.com/hiddify/hiddify-next/blob/main/CONTRIBUTING.md

Use this command to verify your installed Flutter version. Ensure it matches the project's requirements.

```shell
$ flutter --version

# example response
Flutter 3.13.4 • channel stable • https://github.com/flutter/flutter.git
Framework • revision 367f9ea16b (4 weeks ago) • 2023-09-12 23:27:53 -0500
Engine • revision 9064459a8b
Tools • Dart 3.1.2 • DevTools 2.25.0
```

--------------------------------

### Profile Update Interval Header

Source: https://github.com/hiddify/hiddify-next/wiki/URL-Scheme

Sets the automatic update interval for the configuration file in hours. This example sets the interval to 12 hours.

```text
profile-update-interval: 12
```

--------------------------------

### Build Hiddify-Core Libraries from Source

Source: https://github.com/hiddify/hiddify-next/blob/main/CONTRIBUTING.md

Optional commands to build Hiddify-Core libraries from source after running `make prepare`. Select the command corresponding to your target platform.

```shell
- make build-windows-libs
- make build-linux-libs
- make build-macos-libs
- make build-ios-libs
- make build-android-libs
```

--------------------------------

### Prepare Environment for Hiddify-Core

Source: https://github.com/hiddify/hiddify-next/blob/main/CONTRIBUTING.md

Execute these make commands to prepare your environment for Hiddify-Core development, especially if not using existing releases. Run commands based on your target platform.

```shell
- make windows-prepare
- make linux-prepare
- make macos-prepare
- make ios-prepare
- make android-prepare
```

--------------------------------

### Build Release Versions

Source: https://github.com/hiddify/hiddify-next/blob/main/CONTRIBUTING.md

Use these make commands to build the release version of the application for various operating systems. Ensure your environment is set up correctly before running these commands.

```bash
make windows-release
```

```bash
make linux-release
```

```bash
make macos-release
```

```bash
make android-release
```

```bash
make ios-release
```

--------------------------------

### Import Configuration via URL Scheme

Source: https://github.com/hiddify/hiddify-next/wiki/URL-Scheme

Use this scheme to quickly import configuration files. The sublink can be a clash link, singbox link, v2ray sublink, or a single proxy link.

```URL
hiddify://import/<sublink>#name
```

--------------------------------

### Hysteria2 Proxy Configuration Example

Source: https://github.com/hiddify/hiddify-next/wiki/URL-Scheme

Example of a Hysteria2 proxy configuration with insecure option, obfuscation, and SHA256 pin.

```Proxy
# Hysteria2
hysteria2://letmein@example.com/?insecure=1&obfs=salamander&obfs-password=gawrgura&pinSHA256=deadbeef&sni=real.example.com
```

--------------------------------

### Run Release Build on Device

Source: https://github.com/hiddify/hiddify-next/blob/main/CONTRIBUTING.md

Execute this command to build and run the release version of the app on a connected device. You can specify a device ID if multiple devices are connected.

```shell
flutter run
# or
flutter run --device-id=35492ae2
```

--------------------------------

### Modern CMake Policy and Install RPATH

Source: https://github.com/hiddify/hiddify-next/blob/main/linux/CMakeLists.txt

Explicitly opts into modern CMake behaviors and sets the installation runtime path for bundled libraries.

```cmake
# Explicitly opt in to modern CMake behaviors to avoid warnings with recent
# versions of CMake.
cmake_policy(SET CMP0063 NEW)

# Load bundled libraries from the lib/ directory relative to the binary.
set(CMAKE_INSTALL_RPATH "$ORIGIN/lib")
```

--------------------------------

### Apply Standard Build Settings

Source: https://github.com/hiddify/hiddify-next/blob/main/windows/runner/CMakeLists.txt

Applies a predefined set of standard build settings to the application target. This can be customized for projects requiring different build configurations.

```cmake
apply_standard_settings(${BINARY_NAME})
```

--------------------------------

### Enable Unicode Support

Source: https://github.com/hiddify/hiddify-next/blob/main/windows/CMakeLists.txt

Adds preprocessor definitions to enable Unicode support for all projects.

```cmake
add_definitions(-DUNICODE -D_UNICODE)
```

--------------------------------

### Profile-Title Header (ASCII Encoded)

Source: https://github.com/hiddify/hiddify-next/wiki/URL-Scheme

Use an ASCII name for the profile title. This example shows a simple text-based profile title.

```text
Profile-Title: I love hiddify
```

--------------------------------

### Create and Checkout New Branch

Source: https://github.com/hiddify/hiddify-next/wiki/How-to-contribute-to-this-project

Create a new branch for your development work and switch to it. Replace 'Hiddify-develop' with your desired branch name.

```bash
git branch Hiddify-develop
git checkout Hiddify-develop
```