How can I add library search paths for libraries, which exist in a root directory as well as a child directory of that root directory? If I add a root directory to the library search paths, and then add another directory that is descended from that root directory I get an error “A parent directory of … is already on the search path. Remove the parent directory before adding a subdirectory.”
If I just keep the parent directory, user libraries are not found, and I don’t think user library entries appear to be able to reference nested paths within a root search path. I end up with the error “The library file … was not found on the library search path.” and “Library file(s) … could not be found on the library search path.” when selecting a user library that is in a subdirectory of a search path
What is the search path for a Plecs model? Is it different from the demo models available in the documentation? - #2 by Oliver_Schwartz discusses recursive search paths for thermal descriptions, but I don’t see anything related to recursion for model libraries
We are trying to maintain our models in version control and have lots of shared components across projects in our monorepo, so it’s pretty common to have all sorts of sub- and supersets of directories which have model libraries in them (as well as lots of other source code directly related, indirectly related, or unrelated to PLECS as well)