Searched refs:PATH (Results 1 – 25 of 55) sorted by relevance
123
| /hal_espressif-3.4.0/docs/zh_CN/get-started-legacy/ |
| D | linux-setup.rst | 58 …为了正常使用工具链，您必须更新 ``~/.profile`` 文件中的 ``PATH`` 环境变量。此外，您还可以在 ``~/.profile`` 文件中增加以下代码，这样一来，所有终端窗口均可以…
60 export PATH="$HOME/esp/xtensa-esp32-elf/bin:$PATH"
64 alias get_esp32='export PATH="$HOME/esp/xtensa-esp32-elf/bin:$PATH"'
66 这样，您可以在终端输入 ``get_esp32`` 命令将工具链添加至您的 ``PATH``，从而使用工具链。
72 3. 退出并重新登录以使 ``.profile`` 更改生效。运行以下命令来检查 ``PATH`` 设置是否正确 ::
74 printenv PATH
78 $ printenv PATH
|
| D | macos-setup.rst | 36 为了正常使用工具链，您必须更新 ``~/.profile`` 文件中的 ``PATH`` 环境变量。此外，您还可以在 ``~/.profile`` 文件中增加以下代码，这样一来，所有终端窗口均可以使…
38 export PATH=$HOME/esp/xtensa-esp32-elf/bin:$PATH
42 alias get_esp32="export PATH=$HOME/esp/xtensa-esp32-elf/bin:$PATH"
44 这样，您可以在终端输入 ``get_esp32`` 命令将工具链添加至您的 ``PATH``，从而使用工具链。
|
| D | eclipse-setup.rst | 51 …PATH`` 环境变量。保留当前值，并将该路径增加至 Xtensa 工具链安装路径后，作为 IDF 设置的一部分（如已增加至 PATH，则可忽略）。工具链的常见路径为 ``/home/user-n…
|
| /hal_espressif-3.4.0/docs/zh_CN/get-started/ |
| D | linux-setup-scratch.rst | 77 添加工具链到 PATH 环境变量
80 需要将自定义工具链复制到一个二进制目录中，并将其添加到 ``PATH`` 中。例如，您可以将编译好的工具链复制到 ``~/esp/{IDF_TARGET_TOOLCHAIN_PREFIX}/`` 目…
82 为了正常使用工具链，您需要更新 ``~/.profile`` 文件中 ``PATH`` 环境变量。此外，您还可以在 ``~/.profile`` 文件中增加以下代码。这样，所有终端窗口均可以使用 `…
84 export PATH="$HOME/esp/{IDF_TARGET_TOOLCHAIN_PREFIX}/bin:$PATH"
90 退出并重新登录以使 ``.profile`` 的更改生效。运行以下命令来检查 ``PATH`` 设置是否正确::
92 printenv PATH
96 $ printenv PATH
|
| D | windows-setup-update.rst | 24 使用“导出脚本”将 ESP-IDF 工具添加至 PATH 环境变量
29 有些情况下，您正在使用的命令提示符窗口并不是通过快捷方式打开的，此时如果想要在该窗口使用 ESP-IDF，您可以根据下方步骤将 ESP-IDF 工具添加至 PATH 环境变量。
|
| D | windows-setup-scratch.rst | 51 …安装器询问“安装选项”时，选择 "Add CMake to the system PATH for all users"（为所有用户的系统路径添加 CMake）或 "Add CMake to th…
|
| D | windows-setup.rst | 101 …捷方式。本快捷方式可以打开 Windows 命令提示符（即 cmd.exe），并运行 ``export.bat`` 脚本以设置各环境变量（比如 ``PATH``，``IDF_PATH`` 等）。此…
107 2. 或者，您可以运行 ``cmd.exe``，并切换至您希望使用的 ESP-IDF 目录，然后运行 ``export.bat``。注意，这种方法要求 ``PATH`` 中存在 Python 和 G…
|
| /hal_espressif-3.4.0/ |
| D | export.sh | 85 old_path="$PATH"
108 export PATH="${IDF_ADD_PATHS_EXTRAS}:${PATH}"
112 path_prefix=${PATH%%${old_path}}
129 __verbose " ${PATH}"
|
| D | export.fish | 9 set oldpath = $PATH
14 echo "Adding ESP-IDF tools to PATH..."
30 set -x PATH "$IDF_ADD_PATHS_EXTRAS":"$PATH"
33 for entry in $PATH;
39 echo "Added the following directories to PATH:"
|
| D | export.bat | 28 set "OLD_PATH=%PATH%"
29 echo Adding ESP-IDF tools to PATH...
41 :: This removes OLD_PATH substring from PATH, leaving only the paths which have been added,
43 call set PATH_ADDITIONS=%%PATH:%OLD_PATH%=%%
67 echo No directories added to PATH:
69 echo %PATH%
|
| D | add_path.sh | 16 export PATH="${IDF_ADD_PATHS_EXTRAS}:${PATH}"
|
| /hal_espressif-3.4.0/docs/en/get-started-legacy/ |
| D | macos-setup.rst | 36 To use it, you will need to update your ``PATH`` environment variable in ``~/.profile`` file. To ma…
38 export PATH=$HOME/esp/xtensa-esp32-elf/bin:$PATH
42 alias get_esp32="export PATH=$HOME/esp/xtensa-esp32-elf/bin:$PATH"
44 …in you can type ``get_esp32`` on the command line and the toolchain will be added to your ``PATH``.
|
| D | linux-setup.rst | 58 …To use it, you will need to update your ``PATH`` environment variable in ``~/.profile`` file. To m…
60 export PATH="$HOME/esp/xtensa-esp32-elf/bin:$PATH"
64 alias get_esp32='export PATH="$HOME/esp/xtensa-esp32-elf/bin:$PATH"'
66 …in you can type ``get_esp32`` on the command line and the toolchain will be added to your ``PATH``.
72 … ``.profile`` changes effective. Run the following command to verify if ``PATH`` is correctly set::
74 printenv PATH
78 $ printenv PATH
|
| D | eclipse-setup.rst | 51 …PATH`` environment variable. Keep the current value, and append the path to the Xtensa toolchain i…
|
| /hal_espressif-3.4.0/docs/en/get-started/ |
| D | linux-setup-scratch.rst | 77 Add Toolchain to PATH
80 The custom toolchain needs to be copied to a binary directory and added to the ``PATH``. Choose a d…
82 To use it, you will need to update your ``PATH`` environment variable in ``~/.profile`` file. To ma…
84 export PATH="$HOME/esp/{IDF_TARGET_TOOLCHAIN_PREFIX}/bin:$PATH"
90 … ``.profile`` changes effective. Run the following command to verify if ``PATH`` is correctly set::
92 printenv PATH
96 $ printenv PATH
|
| D | windows-setup-update.rst | 24 Add ESP-IDF tools to PATH using an export script
29 …ing that shortcut. If this is the case, follow the instructions below to add ESP-IDF tools to PATH.
|
| /hal_espressif-3.4.0/docs/en/api-guides/tools/ |
| D | idf-tools.rst | 68 …ed to be set to use the installed tools. For most of the tools, setting ``PATH`` environment varia…
76 export PATH="/home/user/.espressif/tools/tool/v1.0.0/bin:$PATH"
82 set "PATH=C:\Users\user\.espressif\tools\v1.0.0\bin;%PATH%"
96 PATH=/home/user/.espressif/tools/tool/v1.0.0:$PATH
122 Since the installed tools are not permanently added into the user or system ``PATH`` environment va…
134 …calling ``idf_tools.py``, these scripts list the directories which have been added to the ``PATH``.
148 …m expects that all the necessary tools are installed somewhere, and made available in the ``PATH``.
|
| D | idf-windows-installer.rst | 9 * ``/CONFIG=[PATH]`` - Path to ``ini`` configuration file to override default configuration of the …
12 * ``/GITREPO=[URL|PATH]`` - URL of repository to clone ESP-IDF. Default: https://github.com/espress…
15 * ``/IDFDIR=[PATH]`` - Path to directory where it will be installed. Default: ``{userdesktop}\esp-i…
18 * ``/LOG=[PATH]`` - Store installation log file in specific directory. Default: empty.
|
| /hal_espressif-3.4.0/components/xtensa/trax/test/ |
| D | README.txt | 5 - Add ESP32 toolchain to PATH, and check that GDB has been built with Python support
6 - Add OpenOCD to PATH and set OPENOCD_SCRIPTS
|
| /hal_espressif-3.4.0/components/mdns/test_afl_fuzz_host/ |
| D | README.md | 35 export PATH="/usr/local/opt/llvm/bin:$PATH"
60 export PATH="$AFL_PATH:$PATH"
|
| /hal_espressif-3.4.0/components/lwip/test_afl_host/ |
| D | README.md | 35 export PATH="/usr/local/opt/llvm/bin:$PATH"
60 export PATH="$AFL_PATH:$PATH"
|
| /hal_espressif-3.4.0/tools/ci/ |
| D | test_build_system_cmake.sh | 36 export PATH="$IDF_PATH/tools:$PATH" # for idf.py
536 OLDPATH="$PATH"
545 export PATH="$(pwd):$PATH"
547 export PATH="$OLDPATH"
605 …(export PATH=$PWD:$PATH && idf.py --ccache reconfigure | grep "ccache will be used") || failure "c…
607 (export PATH=$PWD:$PATH && idf.py reconfigure| grep -c "ccache will be used" | grep -wq 0) \
609 …(export PATH=$PWD:$PATH && idf.py --no-ccache reconfigure| grep -c "ccache will be used" | grep -w…
|
| D | find_apps_build_apps.sh | 30 export PATH="$IDF_PATH/tools/ci:$IDF_PATH/tools:$PATH"
|
| D | test_build_system.sh | 234 OLD_PATH=$PATH
235 export PATH="$PWD:$PATH"
241 export PATH=$OLD_PATH
|
| /hal_espressif-3.4.0/components/esptool_py/esptool/flasher_stub/ |
| D | README.md | 23 …s for ESP32 and later chips (xtensa-esp32-elf-, riscv32-esp-elf-) on your PATH. If you are develop…
33 …akes care of most of these steps (only the ESP8266 gcc toolchain has to be manually added to PATH).
|
123
