DISCLAIMER: This is also not intended to offend...
I dispise having to fiddle-fart around downloading and compiling a damn library. Its such a waste of time.
If you're not happy with this situation, then prior to the 1.0.0 when I'll likely doing binary packages, you may provide pre-compiled versions for the good of the community. Do note though that you'll need to prepare and test at least six different versions for Win32.
People spend more time "getting it compiled" than trying to "learn and use it".
I can download the source release package and the dependency packages for any given config, change absolutely nothing, and have it compiled in under 10 minutes. If you think it's possible to learn this in less time than that, you're sadly mistaken
IF ITS A LIBRARY THEN MAKE IT ONE!
IT IS ALREADY LIBRARY. IT'S CURRENTLY PACKAGED AS SOURCE.
If you want MORE people to use your library, MAKE IT EASY FOR THEM.. This is just simple business smarts and common sense.
If somebody has tremendous trouble simply downloading and compiling the lib, then there's probably not much hope that they'll be able to do much with it afterwards; and to be brutally honest, I really don't need any more newbies on here who seem to have trouble just working thier compiler.
I am not saying do NOT offer the code. But most of use don't want to spend time "setting up" and compiling it.
The whole point of having code-only at the moment stems from the fact that in 90% of cases people are going to either want to, or need to, tweak the code anyway. So this is the best option, at least for the time being.
I'm not in any way opposed to doing binary releases, but it would be another thing taking my limited time; currently I am trying to get new features into the system, though I don't seem to have gotten anything done for weeks
. Once things are a bit further along, the likelyhood of binary releases will increase.