[win32] update and clean exclude.txt used in BuildSetup
[win32] installer: remove language checkbox and just install all languages
[win32] installer: remove unused code
[win32] installer: move addon copy
[win32] installer: remove outdated code
[win32] remove unused build  .bat files
ActiveAE: increase timeout for MakeStream
AE: remove audioSinkBufferDurationMsec from advances settings, it does more harm than any good
[pydocs] don't add core code comments to pydocs
Merge pull request #3172 from MartijnKaijser/win32_installer_cleanup

[win32] update and clean windows installer
[win32] installer: fix setting wrong output path after 0a16a920f8235b9b0adec746a1be472f3cb52767
configure: add initial support for CC_FOR_BUILD, CXX_FOR_BUILD, CFLAGS_FOR_BUILD, CXXFLAGS_FOR_BUILD, LDFLAGS_FOR_BUILD
configure/depends: rename 'USE_TEXTUREPACKER_NATIVE_ROOT' to 'NATIVE_ROOT' for general usage to use with other hostbuilt tools. Add $NATIVE_ROOT/lib to LDFLAGS_FOR_BUILD and $NATIVE_ROOT/include to CFLAGS_FOR_BUILD and CXXFLAGS_FOR_BUILD
libsquish: rework to support native builds with *_FOR_BUILD
Texturepacker: rework to support native builds with *_FOR_BUILD, Texturepacker builds always against libsquish-native.so, which is ok because CXX_FOR_BUILD=CXX, CXXFLAGS_FOR_BUILD=CXXFLAGS and LDFLAGS_FOR_BUILD=LDFLAGS on non crosscompiled builds, sothere libsquish-native is the same like libsquish
configure: cleanup, we dont need 'use_texturepacker_native' anymore and dont need to force 'use_texturepacker' (its enabled by default).
[pydocs] set pydocs version equal to xbmc.python addon version
ActiveAE: nail sampling rate to 48khz for transcode
[settings] Fix memory corruption caused by resolution sorting

This is possibly the most subtle bug I've seen.
What I've seen over last couple of weeks is random memory corruption
failures when browsing the settings/video output window.

I tracked it down to the sort function in CWinSystemBase::ScreenResolutions.
But why? Everything looked fine.

Eventually spotted it. The compare function doesn't obey strict weak ordering.
std::sort considers a reasonable response to that is to corrupt memory.

Here's a description from someone else who hit a similar bug:
http://schneide.wordpress.com/2010/11/01/bug-hunting-fun-with-stdsort/
Merge pull request #3188 from popcornmix/sort_crash

[settings] Fix memory corruption caused by resolution sorting