/Zc:threadSafeInit, enabled by default, uses compiler-supported thread
local storage, which doesn't work on Windows XP in (dynamically-loaded)
DLLs. As WinSparkle's use is out of our control and the code doesn't
rely on C++11 semantics of static variables being thread-safely
initiliazed, play it safe and disable the option.
See e.g. http://trac.wxwidgets.org/ticket/17403
Update old docs and examples to use https:// everywhere, as production
use should. This is merely a precaution to put beginners on the right
track, it doesn't change anything about WinSparkle's behavior.
See #94.
Project files are now generated using Bakefile 1.x. This has a number of
advantages:
- Cleaner build of dependencies
- Support for all compilers from the same source
- Added support for Visual Studio 2012
As an alternative to win_sparkle_set_appcast_url(), it is possible to
specify the feed in win32 resources. This isn't as convenient as
Info.plist on OS X, but at least it still has the advantage of being
externally readable.
The resource has to be named "FeedURL" and have type set to "APPCAST".
The PSDK example now uses it.
This sample app is written with raw Platform SDK API, no GUI
toolkit is used. In addition to demonstrating simple WinSparkle use,
it also shows how the app can use different CRT from the DLL.
Václav Slavík