esp-idf: Windows IDF_PATH format causes errors [was: project.mk:279: *** multiple target patterns. Stop.] (IDFGH-1738)
After git clone of current esp-idf and attempting to make menuconfig of hello_world_main.c I am getting the following error:
$ make menuconfig
C:/msys32/esp-idf/make/project.mk:279: *** multiple target patterns. Stop.
Replacing project.mk to an older version that I loaded yesterday resolves this issue.
Do I miss some extra configuration that should be done somewhere else?
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Comments: 21 (10 by maintainers)
Commits related to this issue
- build system: Fix Windows case when IDF_PATH contains colons (ie C:/) Closes github #166 https://github.com/espressif/esp-idf/issues/166 — committed to espressif/esp-idf by projectgus 8 years ago
- Merge branch 'bugfix/build_system_tilde' into 'master' Build system: Allow IDF_PATH to contain ~ or C:/ See github issues * https://github.com/espressif/esp-idf/issues/118 * https://github.com... — committed to espressif/esp-idf by projectgus 8 years ago
- build system: Account for Windows behaviour of make wildcard for some dirs See github #166 — committed to espressif/esp-idf by projectgus 7 years ago
- build system: Account for Windows behaviour of make wildcard for some dirs See github #166 — committed to espressif/esp-idf by projectgus 7 years ago
- Eclipse: Process Windows paths correctly using cygpath Includes splitting the Windows Eclipse setup doc into a separate page, as it has so many additional steps. Addresses github #17 and #166 https:... — committed to espressif/esp-idf by projectgus 7 years ago
@guepy We mention in the docs that we don’t support spaces in paths:
https://docs.espressif.com/projects/esp-idf/en/latest/get-started/#step-2-get-esp-idf
I’m afraid there’s no other solution other than to move your ESP-IDF direcotry somewhere else to satisfy this constraint.
I usually never post comments, however I just had to say THANK YOU for posting the solution: I’ve just spent hours with this exact same bug and also fixed it by changing the IDF_PATH.