double quoted strings in env.txt files
Hi all, I currently try to convert some boards to the new env.txt files and this works quite well so far. But I encountered one problem which I am not sure how to solve it.
If I have some string in a Kconfig file defined like: config KM_DEF_NETDEV string "Default Netdevice" default "eth0"
When I use this config now in one of the env.txt files: netdev=CONFIG_KM_DEF_NETDEV
I end up with: netdev="eth0" formerly in the environment I had: netdev=eth0
So in this case I would like to strip away the double quoted string and I don't see that there is a way to do so. Surely there would be some workarounds to solve this but as I have this at several places and I can imagine that this will hit others too, it might be good to think about a general way to solve this. For example we could add a tag around these CONFIG options in such cases which then can be parsed in the script processing the env.txt to strip away the double quotes.
Any ideas about this? Or is there already a way to solve this problem which I miss?
Best regards Holger
Hi Holger,
On Thu, 3 Nov 2022 at 02:18, Holger Brunck holger.brunck@hitachienergy.com wrote:
Hi all, I currently try to convert some boards to the new env.txt files and this works quite well so far. But I encountered one problem which I am not sure how to solve it.
If I have some string in a Kconfig file defined like: config KM_DEF_NETDEV string "Default Netdevice" default "eth0"
When I use this config now in one of the env.txt files: netdev=CONFIG_KM_DEF_NETDEV
I end up with: netdev="eth0" formerly in the environment I had: netdev=eth0
So in this case I would like to strip away the double quoted string and I don't see that there is a way to do so. Surely there would be some workarounds to solve this but as I have this at several places and I can imagine that this will hit others too, it might be good to think about a general way to solve this. For example we could add a tag around these CONFIG options in such cases which then can be parsed in the script processing the env.txt to strip away the double quotes.
Any ideas about this? Or is there already a way to solve this problem which I miss?
I am not sure how to solve this in general, since sometimes we need the quotes. But I will send a patch that can solve it for this particular case.
Regards, SImon
Hi Simon,
On Thu, 3 Nov 2022 at 02:18, Holger Brunck holger.brunck@hitachienergy.com wrote:
Hi all, I currently try to convert some boards to the new env.txt files and this works
quite well so far.
But I encountered one problem which I am not sure how to solve it.
If I have some string in a Kconfig file defined like: config KM_DEF_NETDEV string "Default Netdevice" default "eth0"
When I use this config now in one of the env.txt files: netdev=CONFIG_KM_DEF_NETDEV
I end up with: netdev="eth0" formerly in the environment I had: netdev=eth0
So in this case I would like to strip away the double quoted string and I don't see that there is a way to do so. Surely there would be some workarounds to solve this but as I have this at several places and I can imagine that this will hit others too, it might be good to think about a
general way to solve this.
For example we could add a tag around these CONFIG options in such cases which then can be parsed in the script processing the env.txt to strip away the double quotes.
Any ideas about this? Or is there already a way to solve this problem which I
miss?
I am not sure how to solve this in general, since sometimes we need the quotes.
yes I agree that it is good that we can explicitly have them in the text file.
But I will send a patch that can solve it for this particular case.
ok great, I will give it a try then.
Best regards Holger
participants (2)
-
Holger Brunck -
Simon Glass