pcsx2/common/include
refraction 756127d096 Fixed recently discovered bug from VIF which could have potentially happened anywhere jNODEFAULT is used (nobody noticed lol)
git-svn-id: http://pcsx2.googlecode.com/svn/trunk@946 96395faa-99c1-11dd-bbfe-3dabce05a288
2009-04-10 13:29:20 +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 Fixed recently discovered bug from VIF which could have potentially happened anywhere jNODEFAULT is used (nobody noticed lol) 2009-04-10 13:29:20 +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 Reverted the emitter back to a c/cpp form from inl files (probably wasn't necessary, but I don't like having code in header/inl files when I can help it). Also: 2009-04-07 21:54:50 +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 Forgot two files. 2009-03-13 07:27:52 +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