Jake.Stine d9f367f03f wxGui Branch: [Linux] Fixes for various warnings and errors. ... git-svn-id: http://pcsx2.googlecode.com/svn/branches/wxgui@1078 96395faa-99c1-11dd-bbfe-3dabce05a288		2009-04-27 22:00:56 +00:00
..
api	Forgot to remove a couple debug lines.	2009-03-29 06:48:18 +00:00
PS2Edefs.h	LilyPad, Plugin APIs: Slightly changed how multitap API additions work. Now enabling is handled completely by the pad plugin. If anyone ever really feels like adding support for more memcards, can move it over to PCSX2 itself.	2009-03-29 06:14:59 +00:00
PS2Etypes.h	Emitter: Fixed a small bug in the ModSib emitter logic which caused some forms of ESP to encode incorrectly. Implemented CALL/BSF/BSR [x86], MOVQ, MOVD, and MOVSS [mmx/xmm]. Renamed ix86_mmx.cpp and i86_sse.cpp to ix86_legacy_mmx.cpp and i8x_legacy_sse.cpp.	2009-04-19 02:14:50 +00:00
Pcsx2Api.h	General cleanup in Gif.cpp && IPU.cpp. Did a bit of refactoring in Gif.cpp. Moved the path3hack to patches.	2009-03-28 06:53:18 +00:00
Pcsx2Config.h	wxGui branch: Holy crap! I converted it to unicode! This was an absolutely maddening experience. [also: Merged with /trunk]	2009-04-27 02:04:31 +00:00
Pcsx2Defs.h	Linux: Make some of the assembly look a bit better. Change the PCSX2_ALIGNED_EXTERN defs a bit.	2009-03-19 11:11:30 +00:00
Pcsx2Types.h	wxGui Branch: [Linux] Fixes for various warnings and errors.	2009-04-27 22:00:56 +00:00
PluginCallbacks.h	LilyPad, Plugin APIs: Slightly changed how multitap API additions work. Now enabling is handled completely by the pad plugin. If anyone ever really feels like adding support for more memcards, can move it over to PCSX2 itself.	2009-03-29 06:14:59 +00:00
afxresmw.h	Restructured the build system from the ground up. 3rdparty libs have been moved back into a /3rdparty folder, and are compiled as libraries. Most relevant plugins are part of the pcsx2_suite_2008.sln. Revision tagging of filenames is still there, but is now disabled by default. Pathnames with spaces shouldn't break the buildscripts anymore. Removed tons and tons of files in an effort to simplify the repository and build system management. So if a solution file you're used to using is missing, it's missing for a good reason (means the project can be built either from the Suite solution, or by double-clicking the project file from explorer, from which MSVC creates a new solution for you).	2009-02-24 02:08:37 +00:00