Open Bas-vE opened 2 months ago
Oh! I'll take a look. You're right @Bas-vE, it's not by design.
CC: @nate-moehring
When I allow VIPM to scan for dependencies, this is all that comes up:
@jimkring, I'm guessing you or I mistakenly added Caraya to the package dependencies manually, though I don't know why. You did create that VI Tree in the src folder, which does have a static call to run_tests.vi, but neither is included in the package source files list.
I think we just need to remove it from package dependency list and rebuild it.
@nate-moehring @Bas-vE I’ll take a look into this one later this weekend and see if I can do a clean rebuild of the package and what the final dependencies look like.
The VI Tree references run_tests.vi
, which pulls Caraya as a dependency.
version 2.1.0 has a dependency to caraya which can also be seen on VIPM https://www.vipm.io/package/jki_lib_json_serialization/ It feels like this is not by design.