Commit Graph

16 Commits

Author SHA1 Message Date
Jakub Kocka
5b0cf8824a fix(export): Operator syntax fix for all versions of PowerShell 2024-06-28 08:01:30 +02:00
Jakub Kocka
8f383060dd feat: Added pre-commit hook of PowerShell scrip checker 2024-06-20 08:26:46 +02:00
Ivan Grokhotkov
93d1d996b7 feat(tools): add espsecure.py to the Windows export scripts
This is not needed on Linux/macOS where the path to esptool directory
is added to PATH.
2023-07-28 15:35:50 +02:00
Ivan Grokhotkov
01d4c4740a change(tools): export.ps1: define functions for helper python tools
Follows the approach used in Initialise-Idf.ps1 created by the tools
installer. This is the closes equivalent of "alias" used in export.bat

Closes https://github.com/espressif/esp-idf/issues/9849
2023-07-28 15:34:59 +02:00
Roland Dobai
7473fd3f0f Tools: don't add the esptool directory with wrappers to the PATH
Esptool.py is available from the esptool package which is installed in
every ESP-IDF v5.0+ shells. Therefore, the path to the legacy wrapper
scripts is not needed to be in the PATH. In some cases like
https://github.com/espressif/esp-idf/issues/10926 it even cases problem
because the wrapper doesn't have a shebang line and is not executable.

Note that the wrapper is kept only for invoking esptool as "python
$IDF_PATH/..../esptool.py" which was previously used mostly in CMake
files. There should be no other use-case where the esptool wrappers are
still needed.
2023-03-22 11:18:24 +01:00
Ivan Grokhotkov
89d132fe42
tools: fix {install,export}.ps1 for IDF_PATH with spaces
Usage of IDF_PATH has to be quoted in case it contains spaces.
2022-09-09 20:30:16 +02:00
Marek Fiala
a4b0560014 tools: Remove tools that are not used by active ESP-IDF version.
Or remove unused archives from tools - older version, or unused tool archive
2022-02-20 19:48:50 +01:00
Roland Dobai
a93e372364 Tools: Fix silent failure about the incompatible Python 2022-02-16 18:44:13 +01:00
Roland Dobai
b28d7e6850 Tools: Improve the Python package system
Introduce features into the Python package management system & manage
package versions outside of ESP-IDF repo.
2022-01-17 16:54:36 +01:00
Roland Dobai
ccabacec32 Tools: Make clear the used platform in the PowerShell export script 2021-11-09 11:28:48 +01:00
Chris Mumford
969a511612 Define $IsWindows if not defined.
The `$IsWindows` PowerShell variable was added in PowerShell Core 6 and
PowerShell 7, and is not present in earlier PowerShell versions. Set to
true if undefined. This fixes https://github.com/espressif/esp-idf/issues/7820.

The first version to run on non-Windows platforms was PowerShell Core
6.0[^1] which means that IsWindows is guaranteed to be defined on all
non-Windows systems. So, if undefined this indicates a Windows platform.

[^1]: https://docs.microsoft.com/en-us/powershell/scripting/install/powershell-support-lifecycle?view=powershell-7.2#release-history

Closes https://github.com/espressif/esp-idf/pull/7858

Closes https://github.com/espressif/esp-idf/issues/7820
2021-11-09 11:25:15 +01:00
Chris Mumford
8081945405 Initialize $envvars_array to an empty list.
With strict debugging, i.e. `Set-PSDebug -strict`, execution of export.ps1 will
report the following error:

```
The variable '$envars_array' cannot be retrieved because it has not been set.
At C:\path\to\export.ps1:15 char:1
+ $envars_array # will be filled like:
+ ~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (envars_array:String) [], RuntimeException
    + FullyQualifiedErrorId : VariableIsUndefined
```

Closes https://github.com/espressif/esp-idf/pull/7819
2021-11-09 11:23:43 +01:00
Andrei Gramakov
d23989aee2 win_installer: add PowerShell shortcut
add idf_cmd_init.ps1
update git vesion
2021-01-18 11:12:25 +01:00
Andrei Gramakov
f2c6a64191 scripts: updates export.ps1 to export tools' paths 2020-07-27 11:55:04 +02:00
Andrei Gramakov
bc42073a8b fixes for powershell on unix 2020-05-15 14:05:03 +02:00
Andrei Gramakov
79dd142ab8 tools: add install.ps1, export.ps1
Closes IDF-855
2019-08-27 13:45:50 +08:00