idf.py should consider value of -C option when looking for idf_ext.py (IDFGH-1276) #3571
Comments
github-actions
bot
changed the title
|
Hi @bpietsch, it just so happens that we currently have some changes that should solve this that are currently under review. |
trombik
pushed a commit
to trombik/esp-idf
that referenced
this issue
Aug 9, 2019
Changes argument parsing mechanism from argparse to a new one, that provides better support for extensions and options that are only applicable to specific subcommands, Breaking changes: 1. All global options should go before subcommands, i.e. `idf.py build -C ~/some/project` will not work anymore, only `idf.py -C ~/some/project build` is acceptable 2. To provide multiple values to an option like `--define-cache-entry` it's necessary to repeat option many times, i.e. `idf.py -D entry1 entry2 entry3` will not work, right way is: `idf.py -D entry1 -D entry2 -D entry3` At the moment there are 3 options like this: `--define-cache-entry` in base list and `--test-components` and `--test-exclude-components` in the unit test extensions 3. Drops `defconfig` and `bootloader-clean` subcommands Closes espressif#3570 Closes espressif#3571
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If I want to use the -T option for unit-test-app, I must have my current working directory be the unit-test-app directory, but then what good is the -C option to specify the project directory for this case? I'd like to run idf.py from my project directory when building unit-test-app so I don't have to switch back and forth. So, idf.py should look for idf_ext.py in the directory specified by -C if it has been set, and only fall back to cwd if it has not.
The text was updated successfully, but these errors were encountered: