Skip to content
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

kconfig path- slashes wrong (IDFGH-2573) #4658

Closed
Emiel84 opened this issue Jan 23, 2020 · 8 comments
Closed

kconfig path- slashes wrong (IDFGH-2573) #4658

Emiel84 opened this issue Jan 23, 2020 · 8 comments

Comments

@Emiel84
Copy link

Emiel84 commented Jan 23, 2020

I'm trying to build the AT-command set including classic bt support.
But when running a make the paths are wrong for some\all esd-idf references used.

IOError: C:/esp/esp-idf/Kconfig:59: Could not open 'C:espesp-idfcomponentsapp_updateKconfig.projbuild' (ENOENT: No such file or directory). Perhaps the $srctree environment variable (which was unset) is set incorrectly. Note that the current value of $srctree is saved when the Kconfig instance is created (for consistency and to cleanly separate instances). Also note that e.g. $FOO in a 'source' statement does not refer to the environment variable FOO, but rather to the Kconfig Symbol FOO (which would commonly have 'option env="FOO"' in its definition).
make: *** [/c/esp/esp-idf/components/esp32/Makefile.projbuild:51: /c/esp/esp-at/build/esp32/esp32.project.ld] Error 1

I'm using the 'released' branch of the AT-command set for ESP32 (Branch_Branch_v2.0.0.0_esp32).

During a investigation I did see the following in the auto.conf.cmd file.
(This file is generated\updated when I perform the steps to 'make' the AT library, therefore manually fixing it in this file didn't solve it)

deps_config :=
/c/esp/esp-at/main/interface/sdio/Kconfig
/c/esp/esp-at/main/interface/socket/Kconfig
/c/esp/esp-at/main/interface/hspi/Kconfig
/c/esp/esp-at/main/interface/uart/Kconfig
C:\esp\esp-idf\components\app_trace\Kconfig
C:\esp\esp-idf\components\aws_iot\Kconfig
C:\esp\esp-idf\components\bt\Kconfig
C:\esp\esp-idf\components\driver\Kconfig \

It seems that somewhere the slashed are 'windows' formatted, but only for the esp-idf references.
Can someone point me into the direction to solve this issue ?

@github-actions github-actions bot changed the title kconfig path- slashes wrong kconfig path- slashes wrong (IDFGH-2573) Jan 23, 2020
@dobairoland
Copy link
Collaborator

Hi @Emiel84. I hope I got you right and you use this project: https://github.com/espressif/esp-at.
There seem to be a lot of similar issues reported there: espressif/esp-at#232, espressif/esp-at#230, espressif/esp-at#203, espressif/esp-at#157. Please take a look at those issues and see if they help you. Currently I know just a little about that project but reading through them I think maybe you have a wrong IDF version which is not supported by the AT project.

I assume you cannot reproduce the issue with the examples of ESP-IDF. Am I right?

@Emiel84
Copy link
Author

Emiel84 commented Jan 23, 2020

You are correct about the project. Will look at the links you are referring to.
I was using branch V3.3 as mentioned in the steps to allow compiling the ESP set.

You are correct about that I'm not able to reproduce the issue with the Hello world example.

@Emiel84
Copy link
Author

Emiel84 commented Jan 23, 2020

@dobairoland

espressif/esp-at#230 solved the issue.
Replaced the ldgen.mk file with the one in the ticked.

I expect it would help to mention\refer to this file in the 'step by step' for building the AT command set.

@Emiel84
Copy link
Author

Emiel84 commented Jan 23, 2020

Question regarding the AT command set to enable BT classic moved to:
espressif/esp-at#330

@dobairoland
Copy link
Collaborator

Thanks @Emiel84 for the feedback. We will track down the issue and see if some fix should be added into IDF or not.

I suggest to open a new issue for your second (unrelated) problem for better tracking. Thanks!

@Emiel84
Copy link
Author

Emiel84 commented Jan 23, 2020

Thanks for the help @dobairoland !

@xcguang
Copy link
Contributor

xcguang commented Feb 4, 2020

Hi,
Please try it using the last master branch. This issue should be fixed on master branch.

@Alvin1Zhang
Copy link
Collaborator

Thanks for reporting, feel free to reopen if the issue still happens. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants