Sometimes I revert some changes, or do more modifications to a validated feature. I think you will just waste your time always trying to stick to the latest source
That's what branches are designed for in SVN. Yes, the trunk is the development branch and is *potentially* unstable, but by no means should it be unstable on purpose. When you're testing a feature or doing experimentation, you do this on a branch. When you're comfortable with the feature-set and stability, you merge it to the trunk. This is how SVN was designed.
In any case, I'm not trying to change the way you work. Your library is great, and free, so I am no where near the point of complaining or being dissatisfied. Given the unstable condition of the trunk (I had assumed it was somewhat stable), I'll remove the external link and use a release build.
Also, another reason why I link to your subversion development branch is to save space on my own SVN server. I do the same with the boost library (which is, needless to say, substantially larger in terms of bytes than SFML).
I'm definitively not going to do that. Gathering every module in one library is exactly what I want to avoid ![Wink ;)](https://www.sfml-dev.org/forums/Smileys/default/wink.gif)
I completely agree. In fact, now that I look back on it, I can't believe I even suggested it. Bad me, bad! I suppose I was just desperate.
In any case, building the SFML solution via a pre-build event in my project worked out beautifully. However, there are no "custom clean events" in Visual Studio 9 (nor any earlier version), so I can't really clean the project when I clean my solution. However that is negligible.
Thanks for your feedback!