-
Notifications
You must be signed in to change notification settings - Fork 7.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot build i2s_basic demos on Windows (IDFGH-13912) #14751
Comments
This is due to the reference address in Window. I fixed this by replacing the $ENV{IDF_PATH} in main/CMakeLists.txt with the real address in my computer. It works but I think that this way is just a temporary solution to run the example once. idf_component_register(SRCS "${srcs}" replace $ENV{IDF_PATH} with the address in computer |
Hi @xobs, thanks for your feedback! Indeed, the absolute include path has slash & backslash issue on windows. It will be fixed by making the common dependencies an example common component. cc @dothanhdat1413 , thanks for your answer! |
Closes #14751 Make the common I2S dependencies as an example common component, so that to avoid slash & backslash issue on windows when use absolute include path.
Closes #14751 Make the common I2S dependencies as an example common component, so that to avoid slash & backslash issue on windows when use absolute include path.
Closes #14751 Make the common I2S dependencies as an example common component, so that to avoid slash & backslash issue on windows when use absolute include path.
Closes #14751 Make the common I2S dependencies as an example common component, so that to avoid slash & backslash issue on windows when use absolute include path.
Answers checklist.
IDF version.
v5.4-dev-3602-ga97a7b0962
Operating System used.
Windows
How did you build your project?
Command line with idf.py
If you are using Windows, please specify command line type.
PowerShell
What is the expected behavior?
I should be able to build and run commands like
idf.py menuconfig
What is the actual behavior?
Steps to reproduce.
Build or installation Logs.
No response
More Information.
This is likely caused by importing
$ENV{IDF_PATH}
directly intoINCLUDE_DIRS
, which makes the variable as follows:It's complaining about
C:\U
The text was updated successfully, but these errors were encountered: