On Fri, 15 Jul 2011 22:48:25 -0400, Roger <rogerx.oss@gmail.com> wrote:
On Fri, Jul 15, 2011 at 08:09:57PM -0400, Benjamin Johnson wrote: If the distributions wish to change things, that's their prerogative; I mean, Debian's constitutionally incapable of leaving upstream code unmolested, and I'm sure anyone else who maintains an ebuild/RPM/BSD port can figure out how to patch it back to do things their own way. At least you've made an attempt. It may work, it may not, but it's still better than doing nothing but whine about how no distributions will ship your code because of a trivially avoidable technicality.
I was thinking of providing a --use-static-fltk configure option or something.
This way, when things do get stable, a distro can chose to build with external libs.
I think most projects automatically use the system library if present, and fall back on the included one otherwise. We might take that a step further: use the system library if it's present and a sane version, otherwise fall back on our own. I forgot to mention, I'm running r7725 with a couple of my own patches on Windows (and have been for some time now), without problems. I could probably put together an updated FLTK "release" for the tarball, using that + working file dialogs from an older revision, if anyone's interested. ~Benjamin