[SystemGlobals] Define static initialization order of CSpecialProtocol

The destructor of RarManager uses CSpecialProtocol (a class with only
statics). Therefore we have to make sure that CSpecialProtocol is
destructed after RarManager. The C++ standard guarantees the order of
con/destruction for statics only within the same compilation unit.

xbmc/SystemGlobals.cpp

@@ -35,6 +35,10 @@
 #include "interfaces/python/XBPython.h"
 #endif
 
+// Guarantee that CSpecialProtocol is initialized before and uninitialized after RarManager
+#include "filesystem/SpecialProtocol.h"
+std::map<std::string, std::string> CSpecialProtocol::m_pathMap;
+
 #if defined(HAS_FILESYSTEM_RAR)
 #include "filesystem/RarManager.h"
 #endif

xbmc/filesystem/SpecialProtocol.cpp

@@ -34,8 +34,6 @@
 #include "utils/StringUtils.h"
 #endif
 
-std::map<std::string, std::string> CSpecialProtocol::m_pathMap;
-
 void CSpecialProtocol::SetProfilePath(const std::string &dir)
 {
   SetPath("profile", dir);