-
Notifications
You must be signed in to change notification settings - Fork 7.1k
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 retative path includes (IDFGH-1857) #4064
Comments
Hi @no1seman. We will update ASAP to upstream Could you define an environment variable, e.g. MY_PROJECT and then use it for sourcing Kconfigs as follows?
|
thank you for answer. |
Since node is a component can't it have its own Kconfig.projbuild? https://github.com/espressif/esp-idf/tree/master/examples/common_components/protocol_examples_common |
@negativekelvin, |
Hi @no1seman. The |
@dobairoland, |
@no1seman The "rsource" option is now available in the master branch from https://github.com/ulfalizer/Kconfiglib. There is one limitiation: it is not yet available from MSYS2 Mingw32 terminal. Please see the documentation of the upstream |
@dobairoland, |
Dear @dobairoland , Despite What I would like to ask, is that is there a way to set environment variable, like ESP_IDF: v4.1-rc CMakelists.txt (Project level)
$PROJ_PATH/componenets/mycomp/Kconfig.projbuild (Component level)
|
I'm linking https://www.esp32.com/viewtopic.php?f=13&t=18249&p=68052#p68052. I'll answer there. |
Co-authored-by: Me No Dev <me-no-dev@users.noreply.github.com>
Special thanks to @ulfalizer for the helpful suggestions regarding kconfiglib. "rsource" option is available for relative path includes Closes espressif/esp-idf#4064
Problem Description
Simplified project folder structure:
[PROJECT ROOT]
[components]
[node]
Kconfig.in
[main]
Kconfig.projbuild
Contents of Kconfig.projbuild:
When running 'idf.py menuconfig' from [PROJECT ROOT] config menu successfully built, but when i'm running 'idf.py build' I've got the following error:
IOError: /home/user/esp/beacon.new/main/Kconfig.projbuild:55: Could not open '../components/node/Kconfig.in' (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).
If there any way to use [PROJECT ROOT] relative paths in Kconfig? I'm using the same set of my own components in different projects and wanna use them without changing paths in Kconfig.* files.
The text was updated successfully, but these errors were encountered: