ShuriZma
/
pcsx2
mirror of https://github.com/PCSX2/pcsx2.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
pcsx2/3rdparty/svn_readme.txt

26 lines
1.2 KiB
Plaintext
Raw Normal View History

Oops, hit OK instead of cancel on my last commit. Here's the second part I missed. Removed Commandline dialog from Release builds (it's meant for giving debug-style commands to homebrew diagnostic ELFs used for testing Pcsx2/Ps2 compatibility). Removed the compatibility list, which was just a local copy of the online resource. Replaced it with a link to Pcsx2 website. :) git-svn-id: http://pcsx2.googlecode.com/svn/trunk@589 96395faa-99c1-11dd-bbfe-3dabce05a288
2009-02-24 13:10:54 +00:00
Folder: /3rdparty
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). I'll put up a wiki soon which covers new compilation features and stuff, like how to re-enable revision tagging, and how you can direct compiled exe/dlls to be copied to any destination of your choice (yay!) -- plus many other compiling tips (if I can remember them all! >_<) git-svn-id: http://pcsx2.googlecode.com/svn/trunk@581 96395faa-99c1-11dd-bbfe-3dabce05a288
2009-02-24 02:08:37 +00:00
This folder contains libraries written and (un?)maintained by people or parties
GSopen2: Added GLEW as a static library dependency. We decided it's small enough to merit being packaged with PCSX2's 3rdparty libs, and it fixes GSDX from needing GLEW32.dll. git-svn-id: http://pcsx2.googlecode.com/svn/branches/GSopen2@1856 96395faa-99c1-11dd-bbfe-3dabce05a288
2009-09-18 16:21:33 +00:00
outside the Pcsx2 DevTeam. Libraries or code snippets written by the PCSX2 team
Oops, hit OK instead of cancel on my last commit. Here's the second part I missed. Removed Commandline dialog from Release builds (it's meant for giving debug-style commands to homebrew diagnostic ELFs used for testing Pcsx2/Ps2 compatibility). Removed the compatibility list, which was just a local copy of the online resource. Replaced it with a link to Pcsx2 website. :) git-svn-id: http://pcsx2.googlecode.com/svn/trunk@589 96395faa-99c1-11dd-bbfe-3dabce05a288
2009-02-24 13:10:54 +00:00
are housed in /common instead.
GSopen2: Added GLEW as a static library dependency. We decided it's small enough to merit being packaged with PCSX2's 3rdparty libs, and it fixes GSDX from needing GLEW32.dll. git-svn-id: http://pcsx2.googlecode.com/svn/branches/GSopen2@1856 96395faa-99c1-11dd-bbfe-3dabce05a288
2009-09-18 16:21:33 +00:00
Cross-Compilation:
Most libraries includes in /3rdparty come as either default installations in Linux
distributions, or are easily obtainable. Using the PCSX2 versions included here is
optional in such cases, however using the distro-provided packages is not recommended.
(using PCSX2 included versions may help resolve versioning issues).
Note that wxWidgets includes *only* MSW projects and files. Linux and Mac platforms
are assumed to have wx already available in your distributions.
Modifications:
Oops, hit OK instead of cancel on my last commit. Here's the second part I missed. Removed Commandline dialog from Release builds (it's meant for giving debug-style commands to homebrew diagnostic ELFs used for testing Pcsx2/Ps2 compatibility). Removed the compatibility list, which was just a local copy of the online resource. Replaced it with a link to Pcsx2 website. :) git-svn-id: http://pcsx2.googlecode.com/svn/trunk@589 96395faa-99c1-11dd-bbfe-3dabce05a288
2009-02-24 13:10:54 +00:00
Most of these libs in /3rdparty have been tailored slightly from the original
forms downloaded from the net. So if you want to upgrade to a new version you
will need to do a proper diff merge. Likewise, if you modify anything in a
3rdparty library you should be sure to tag the modification with your sig or
a "pcsx2" or something. Thirdly, you can use Svn Log to check for modifications,
however folder renames or svn homesite changes may not have all relevant history
necessary to make an accurate merge.