Esp-idf: No rule to make phy_init_data (IDFGH-1168)

[KaeLL]

Anyone else gets this error from time to time as well?
make: *** No rule to make target '~/Documents/IDF/esp-idf/components/esp32/phy_init_data.h', needed by '~Documents/VSCode/esp32_learning/build/phy_init_data.o'. Stop.

I was getting this when I first tried to build the app this morning. I replaced my esp-idf with the latest snapshot of the master branch right after, and I'm still getting this.

sdkconfig

[igrr]

What is the IDF_PATH set to? (echo $IDF_PATH). If it starts with ~, try using $HOME when setting it, instead: export IDF_PATH=$HOME/Documents/IDF/esp-idf.

[KaeLL]

nvmd@nvmd-W35xSS-370SS:~$ printenv IDF_PATH
/home/nvmd/Documents/IDF/esp-idf
nvmd@nvmd-W35xSS-370SS:~$ cat .profile | grep IDF_PATH
export IDF_PATH="$HOME/Documents/IDF/esp-idf"

[KaeLL]

So I found the problem.
It appears to be an issue with the CONFIG_ESP32_PHY_INIT_DATA_IN_PARTITION option in the sdkconfig.
To reproduce it, just enable it, and compile your app against the master branch of esp-idf. And yes, I do have an phy partition in my partition table, which is why I think this might be a real issue.

Here's the partitions file

# Name
nvs,data,nvs,0x9000,0x4000
otadata,data,ota,0xd000,0x2000
phy_init,data,phy,0xf000,0x1000
ota_0,app,ota_0,0x10000,1600K
ota_1,app,ota_1,,1600K

[KaeLL]

Any update on this issue?

[suda-morris]

@KaeLL Thank you, we're fixing this bug, will push to master ASAP.

Since we've split the esp_wifi from esp32 component, and the path of phy_init_data.h has got changed. Sorry for causing you inconvenience.

[adam-esp]

What should I do to make the compilation successful? When will you fix it? A lot of confusion has arisen with these changes.

[KaeLL]

What should I do to make the compilation successful? When will you fix it? A lot of confusion has arisen with these changes.

Disable it

[adam-esp]

Thanks, now he's compiling. What consequences have the ability to disable this setting?