ok - I understood that, but generally most libraries are released based on a tag, and hence, no changes will be made.
I know this is an edge case – so I won’t dwell too long here. The idea was for library development. If I have a library I am developing, I want to be able to pull in the changes to the project locally to do some testing of the library. The way to ensure this is to delete the library in the
libdeps folder, correct? I was incorrectly thinking that the library manager would look for changes in the repository itself and pull in the changes.
If anyone doing library development has some tips on how they do development and can share them here, that would be great! I think I’m going with keeping a completely separate repo for the library, and point
lib_deps to the local repo. Then delete the
libdeps folder on each build.
I’ve been doing it a much more clunky way (but it still works) by either developing within a project folder, or hard/softlinking to the library folder. Either way, I wasn’t using