LDF: refresh lib dependency after recursive search #4941
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.
LDF might mistakenly remove recursive dependency libs from a graph, usually platform bundled ones
Full description of and issue is in #4940
What I have found is that
ConfigureProjectLibBuilder::_correct_found_libs
method could exclude lib dependencies that it found duringlb.search_deps_recursive
run.With some debugging added it looks like this:
then resulting dependency graph looks like this
it misses valid bundled libs from platfrom
libraries/Update'
andlibraries/Ticker
and build process failswith this PR applied it looks differently
and it builds fine.
I'm not sure that this the right way to do, I only narrowed it down to this place. Hope this will help to understand the issue better.
Thanks!