I do, pretty much, after last year’s pain in making rawproc easier for folk to compile.
However, I’d still like the choice as the developer. When I do Windows builds, I want to package them cleanly, and it still makes instinctive sense to statically link everything, rather than collect .dlls for the install directory. I use mxe.cc to do my cross-compiling, and I use the static targets for such+. Maybe I’m just old and set in my ways…
Imaging applications collect dependencies, knowing how do do all of it is just too much for one person. Integrating it all requires a certain amount of control to limit the undesired possibilities. libpng is a good place to illustrate that: IMHO, until recent OS versions it was hard to write fully functional libpng code without worrying the available versions across all the distros. There’s still churn regarding their new eXIf chunk. Lensfun is another one in a state of change; hard to aim function calls to a changing API, add to that the evolution of the database format.
I’d rather statically link such, avoid having to deal with the large possibility space. For a while librtprocess will be another such moving target, until the api stabilizes…