pcsx2/common/include
Jake.Stine 8ab8adabf1 Improved handling of jNO_DEFAULT so that it performs a sanity check in Devel builds [currently applies to Pcsx2 only since we don't have a standard define macro for devbuild in the plugins].
Cleaned up and abbreviated logging for the new IOP HwRead/Write handlers.

git-svn-id: http://pcsx2.googlecode.com/svn/trunk@1131 96395faa-99c1-11dd-bbfe-3dabce05a288
2009-05-04 14:12:21 +00:00
..
api Forgot to remove a couple debug lines. 2009-03-29 06:48:18 +00:00
PS2Edefs.h Get rid of duplicated code in PS2Etypes.h. :) 2009-04-29 11:47:05 +00:00
PS2Etypes.h Get rid of duplicated code in PS2Etypes.h. :) 2009-04-29 11:47:05 +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 Removed VU-Skip [helps simplify the frameskipper logic] -- Use the VU Cycle Stealer hack instead for better, faster, more stable speedups of the VU1 unit. 2009-05-02 09:04:47 +00:00
Pcsx2Defs.h Improved handling of jNO_DEFAULT so that it performs a sanity check in Devel builds [currently applies to Pcsx2 only since we don't have a standard define macro for devbuild in the plugins]. 2009-05-04 14:12:21 +00:00
Pcsx2Types.h Get rid of duplicated code in PS2Etypes.h. :) 2009-04-29 11:47:05 +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