-
Notifications
You must be signed in to change notification settings - Fork 3
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
An error on the file 'config-static-bmc-reboot.json' generation #10
Comments
Looks like a bug. Can you supply a fix? |
Ah it looks like we probably haven't hit this case (most likely started happening during the meson migration) because at Google, we just override the json itself (take a look at "dummy-gbmc-update"): https://github.com/openbmc/openbmc/tree/master/meta-google/recipes-phosphor/flash It seems like the simple fix is to, either take out the "" around the Do you mind making the change to test it with your use case by any chance? |
Maybe taking out the "" around the @STATIC_HANDLER_STAGED_NAME@ is the right way.
Thanks. |
Ah yes, that makes sense. Thanks Fred - please feel free to take the "" around the jsons and push the code for review on Gerrit if possible. If you're unable to, I can push the change for review as well - just let me konw. |
I build the source code by meson with "-Dupdate-type=static-layout". But that file will embed error values like the following.
I found that the line "conf_data.set_quoted('STATIC_HANDLER_STAGED_NAME', get_option('static-handler-staged-name'))" in meson will quote the string and define STATIC_HANDLER_STAGED_NAME in header. It will be used in config-static-bmc-reboot.json.in to generate config-static-bmc-reboot.json file.
The line in config-static-bmc-reboot.json.in will give the string more than one quote.
Is it a bug or not?
Please help, thanks.
The text was updated successfully, but these errors were encountered: