-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Petr Gadorek
committed
Aug 21, 2024
1 parent
6179002
commit f2c7bb4
Showing
7 changed files
with
106 additions
and
17 deletions.
There are no files selected for viewing
Binary file not shown.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,38 @@ | ||
Configuration | ||
=============================== | ||
Configuration can be done in several ways. The priority order is as follows: configuration files are overridden by environment variables, which in turn can be overridden by command-line arguments. If you go through the wizard, the choices you make there will take the highest precedence. | ||
|
||
Wizard | ||
------------------------- | ||
To start the wizard, simply run eim without any parameters. The wizard will guide you through the installation process. Generally, you can use the arrow keys to navigate between options, the spacebar to select options, and the Enter key to confirm your selections. | ||
|
||
As the final step, the wizard will allow you to save your installation choices as a configuration file. This file can be shared or reused in future installations to replicate the same setup. | ||
|
||
|
||
Command line arguments | ||
--------------------------------- | ||
The easiest way to see all possible command-line arguments is to run eim --help, which will display the following help screen: | ||
|
||
.. figure:: ../_static/help.png | ||
|
||
Config File | ||
--------------------------------- | ||
The installer can use a TOML configuration file. By default, it looks for this file at ./config/default.toml, but you can specify a different path using the `--config` command-line argument. | ||
|
||
Here is an example of what a configuration file might look like: | ||
.. code:: | ||
path = "/tmp/esp-new/" | ||
idf_path = "/tmp/esp-new/v5.3/esp-idf" | ||
tool_download_folder_name = "dist" | ||
tool_install_folder_name = "tools" | ||
target = ["all"] | ||
idf_versions = ["v5.3"] | ||
tools_json_file = "tools/tools.json" | ||
idf_tools_path = "./tools/idf_tools.py" | ||
mirror = "https://github.com" | ||
idf_mirror = "https://github.com" | ||
Env variables | ||
--------------------------------- | ||
You can override any of the configuration settings by exporting environment variables prefixed with `ESP_`. For example, to override the `target` setting, you would use `ESP_TARGET`. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,2 +1,3 @@ | ||
FAQs | ||
=============================== | ||
Till day of release of this documentation, no question were asked about the eim. Next version of this documentation will include answears to all the question asked before it's release. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,16 +1,18 @@ | ||
Installation | ||
Installation of IDF | ||
=============================== | ||
Installing the ESP-IDF using EIM is straightforward. Simply open your preferred shell (we recommend PowerShell for Windows users) and run EIM, providing your installation preferences using any of the configuration <configuration> methods you choose. If you haven't provided all the necessary options, an interactive wizard will guide you through the remaining steps. | ||
|
||
After Installation | ||
=============================== | ||
Installation process goes here. | ||
|
||
Windows | ||
------------------------- | ||
Windows process goes here. | ||
|
||
On Windows, the installer creates an icon on your desktop labeled IDF_PowerShell. Clicking this icon will launch PowerShell with the environment set up, allowing you to start using ESP-IDF immediately. If you've installed multiple versions of ESP-IDF, you will have multiple icons, one for each version. | ||
|
||
macOS | ||
macOS & Linux | ||
--------------------------------- | ||
macOS process goes here. | ||
In the installation directory you selected, there will be a .sh script that, when sourced, activates the ESP-IDF environment in your current shell. It's important to note that this script should be sourced, not executed directly. If you've installed multiple versions of ESP-IDF, there will be a separate script for each version. | ||
|
||
Linux | ||
--------------------------------- | ||
Linux specific documentation here. | ||
.. note:: | ||
|
||
The script should be really sourced and not executed |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,6 +1,49 @@ | ||
Prerequisites | ||
=============================== | ||
The minimum requirements for running the ESP-IDF Installation Manager are below. | ||
Below are the minimum requirements for running the ESP-IDF Installation Manager. | ||
|
||
Windows | ||
---------------- | ||
|
||
- git | ||
- cmake | ||
- ninja | ||
- python with pip capable of creating virtual environment and doing SSL requests | ||
|
||
.. note:: | ||
|
||
If any of these prerequisites are missing, the installer will prompt you to install them. If you agree, the installer will automatically install and configure everything required to run ESP-IDF. | ||
|
||
MacOs | ||
---------------- | ||
|
||
- dfu-util | ||
- cmake | ||
- ninja | ||
- python with pip capable of creating virtual environment and doing SSL requests | ||
|
||
.. note:: | ||
|
||
On POSIX systems, the installer will check for the required prerequisites. If they are not met, the installation will not proceed. | ||
|
||
Linux | ||
---------------- | ||
|
||
- git | ||
- cmake | ||
- ninja | ||
- wget | ||
- flex | ||
- bison | ||
- gperf | ||
- ccache | ||
- libffi-dev | ||
- libssl-dev | ||
- dfu-util | ||
- libusb-1.0-0 | ||
- python with pip capable of creating virtual environment and doing SSL requests | ||
|
||
.. note:: | ||
|
||
On POSIX systems, the installer will check for the required prerequisites. If they are not met, the installation will not proceed. | ||
|
||
- requirements 1 | ||
- requirements 2 |