it is no big deal if the package dependency for a library just got swept up in the upgrade cycle. if the needed function call didn’t change, no problems. else you just get a linker error.
If it would be that easy. The problem I had was, that I installed a dependency using my package manager, but to compile my originally wanted software I had to provide a cmake file (of the dependency I installed via my package manager) to the compiler, which I of course did not have.
pfft. ln -s new_library.4.4.7 old_library.4.2.8
all done!
I wish Lemmy was able to have emoji reactions to comments just so I could react with a horrified face to this comment.
In lieu of that, I’ll just have to put it here: 😱
it is no big deal if the package dependency for a library just got swept up in the upgrade cycle. if the needed function call didn’t change, no problems. else you just get a linker error.
If it would be that easy. The problem I had was, that I installed a dependency using my package manager, but to compile my originally wanted software I had to provide a cmake file (of the dependency I installed via my package manager) to the compiler, which I of course did not have.
yeah that’s different