Soren Jorvang d2910912a4 XInitThreads() must be the very first Xlib function called or else ... some X state will have initialized mutexes and some won't, leading to unpredictable results depending on the feature set compiled into wxWidgets and so on. wxGTK starts by calling Xlib functions indirectly through gdk very early on, so we must hook into wxApp::Initialize(). I believe this should properly fix issue 1540. In case of problems, please reopen that issue. If you see XLockMutex in a backtrace, that's a pretty good indication. git-svn-id: https://dolphin-emu.googlecode.com/svn/trunk@7205 8ced0084-cf51-0410-be5f-012b33b47a6e		2011-02-19 21:53:53 +00:00
..
Core	XInitThreads() must be the very first Xlib function called or else	2011-02-19 21:53:53 +00:00
DSPSpy	drop vs2008 projects in favor of vs2010	2011-02-11 15:43:05 +00:00
DSPTool	drop vs2008 projects in favor of vs2010	2011-02-11 15:43:05 +00:00
Plugins	XInitThreads() must be the very first Xlib function called or else	2011-02-19 21:53:53 +00:00
TestSuite	drop vs2008 projects in favor of vs2010	2011-02-11 15:43:05 +00:00
UnitTests	LTCG (link time code gen) was off in some projects, so turn it off in all of them so that the linker doesn't have to restart halfway through.	2011-02-05 20:14:23 +00:00
VSProps	vs2010: add debugfast configs for wxw (now debugfast links faster!). clean up wxw projects a lot.	2011-02-10 06:31:12 +00:00
CMakeLists.txt	Add an experimental CMake build system as a possible replacement for SCons. Only tested on Linux, should work on OS X and Windows in the future as well though.	2010-11-01 15:47:02 +00:00
Dolphin_2010.sln	windows: buildfix for non-release configs	2011-02-11 22:27:50 +00:00