Description
"AF Debug.lvlib" and "Actor Framework.lvlib" are known to have a circular dependency. Creating a project that contains both of them and their respective PPLs build specifications along with a vi that calls both libraries along with its corresponding EXE build specification and then building the project with the LabVIEW Solution Builder, results in a build failure and the missed detection of the circular dependency.
Steps to reproduce
- Create a new project
- Add "AF Debug.lvlib" and create the corresponding PPL build specification activating the exclusion of the dependent packed project libraries.
- Do the same for "Actor Framework.lvlib".
- Create a VI that calls some code from both libraries and create the corresponding EXE build specification activating the exclusion of the dependent packed project libraries.
- Execute the LabVIEW Solution Builder, point to the just prepare project and click build
Expected Behavior
The build process stops and raises a” Unable to continue because a circular dependency exists.”
Actual Behavior
The build doesn't detect the circular dependency and fails while building the EXE. See screenshot below:
Source triggering the bug:
Test AF Circular Dependency.zip
Environment
LabVIEW 2019 SP1
Description
"AF Debug.lvlib" and "Actor Framework.lvlib" are known to have a circular dependency. Creating a project that contains both of them and their respective PPLs build specifications along with a vi that calls both libraries along with its corresponding EXE build specification and then building the project with the LabVIEW Solution Builder, results in a build failure and the missed detection of the circular dependency.
Steps to reproduce
Expected Behavior
The build process stops and raises a” Unable to continue because a circular dependency exists.”
Actual Behavior
The build doesn't detect the circular dependency and fails while building the EXE. See screenshot below:
Source triggering the bug:
Test AF Circular Dependency.zip
Environment
LabVIEW 2019 SP1