[Build] Create vconf related to .NET as a file in RO location #5679
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
JongHeonChoi
force-pushed
the
write_vconf_to_file
branch
from
2688f95 to
4c400f3
Compare
JongHeonChoi
force-pushed
the
write_vconf_to_file
branch
from
4c400f3 to
bbd174d
Compare
HJLeee
approved these changes
Oct 31, 2023
|
Do we still need vconf set for the legacy? |
dongsug-song
pushed a commit
that referenced
this pull request
Nov 6, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Guided by Appfw, vconf daemon does not run at mic stage. So,
vconf_get_*api does not work normally. Therefore, it provides a second chance to read the file whenvconf_get_*is null. So, Create vconf related to .NET as a file in RO location.