12-14-2008, 03:16 AM
Compile Guide
|
O'k. I do сompilation on newly installed debian/Lenny, so I could made small guide.
1) Packages, need to be installed (complete list, with exact names, don't miss it): subversion libbz-dev libglew1.5-dev libxxf86vm-dev nvidia-cg-toolkit libasound2-dev joystick libsdl1.2-dev libgtk2.0-dev autoconf automake All other packages was already here, so probably you got them all to. 2) Obtain both pcsx2 and pcsx2-playground svn checkout http://pcsx2-playground.googlecode.com/svn/trunk/ pcsx2-playground-read-only svn checkout http://pcsx2.googlecode.com/svn/trunk/ pcsx2-read-only 3) Copy build.sh from pcsx2 and pluggins to pcsx2-playground. It's easiest way to build every pluggins and binary at the same time. Do not copy svn-specific files, other wise you repository at playground directory would be breaking. 4) And run sh build.sh all. If you want to rebuild all, there is several issues: 1) some slight changes, you could use build.sh install 2) To rebuild only playground bilary, run build.sh in pcsx2 directory 3) If somebody change files in pcsx2/Linux directory, than you should made dist-clean before compilation.
12-14-2008, 01:56 PM
As an addition to the Linux compilation guide posted, in the build.sh file, you will see a line that reads something along the line of:
export PCSX2OPTIONS="--enable-sse3 --prefix `pwd`" This is where the options get passed when compiling. If you want to tweak your build a bit, this is where to do it. Here are the main options. --enable-sse3 - tells pcsx2 that you have sse3, and to use code that takes advantage of it. --enable-sse4 - same for sse4. Not very well tested. --enable-debug - builds just that, a debugging build with no optimization, and all the symbols in the code to make it easy to debug. You would mainly use this if you wanted, for example, to know exactly where a game was crashing. --enable-devbuild - Similar to the last option, this turns on various logging for pcsx2, to give you a lot more info about what pcsx2 is doing. --disable-recbuild - Turns off the recompiler, which is where a lot of pcsx2's speed comes from. You almost never want to do this. --disable-nls - Gets rid of locale support. Doubt you'll ever need to touch this. Options that are currently in SVN, but not in the official build. --enable-local-inis - I may have mentioned this one before, though I forgot that it was only in svn. This is actually from a patch from the Gentoo people, to change where the ini files were located, for people that don't want all the pcsx2 files in one folder. If you define LOCAL_PLUGIN_INIS in Linux/Linux.h in the official release, you'd get the same effect. --enable-customcflags - Also for the Gentoo folk. It just simply makes sure that it uses any system-wide CFLAGS you have set up, in addition to the ones it needs. I may just put this permanently on at some point. Other notable flags: --prefix `pwd` - This tells it that the bin folder to install in is in the current directory. Otherwise, it goes straight to /usr/bin, IIRC. --enable-vmbuild - This actually was broken badly, and I found no evidence that it had ever worked on Linux. So it's been removed for the moment. Oh, and while current svn still doesn't have the plugins, there is now a bin folder in there you can use.
12-16-2008, 12:01 PM
Yo, i followed the steps exactly, compiled with visual C++ 2008 express edition, but don't get an exe file generated anywhere, however i do get a Release directory generated with heaps of language files in them. I've searched the bin directory yet at no avail.
(12-13-2008, 11:44 AM)Blackclaw Wrote: Windows Based Guide (I'm no Linux user... bug arcum about that ^^)
12-16-2008, 12:22 PM
(12-16-2008, 12:01 PM)thebozo1 Wrote: Yo, i followed the steps exactly, compiled with visual C++ 2008 express edition, but don't get an exe file generated anywhere, however i do get a Release directory generated with heaps of language files in them. I've searched the bin directory yet at no avail. Visual Studio Express cannot compile Pcsx2. It does not include the MFC/ATL libraries necessary to build and link the resource files for the Pcsx2 GUI. There is no (easy) way to install MFC/ATL for Express either, as Microsoft went to great lengths to make sure that it was next to impossible to do so. If you want to compile Pcsx2 for yourself you must download the full version of Visual Studio, available from the link posted in that very message you quoted, as a 90-day trial.
Jake Stine (Air) - Programmer - PCSX2 Dev Team
12-16-2008, 12:37 PM
how can I compile pcsx2 playground by using VS2005 (missing project files) ?
12-16-2008, 12:38 PM
You can't anymore,VS 2005 support was recently removed (it IS outdated anyway).You can get the VS 2008 90 day trial to compile it
you CAN compile PCSX2 with 2008 Express - it'll complain about "afxres.h", so just change that to "afxresmw.h".
Everything will compile perfectly.
12-17-2008, 06:24 AM
I got problems building it in linux.
I have installed all the dependences, and then copied the plugins directory and the build.sh from the pcsx2 to the pcsx2playgroud, but this is the error : Building Graphics Synthesizer plugins... ---------------------------------------- ---------------------- Building ZeroGS OpenGL ---------------------- make: *** No se especificó ningún objetivo y no se encontró ningún makefile. Alto. Its in spanish, it says, No object was specified and no makefile found. Stop. |
« Next Oldest | Next Newest »
|
Users browsing this thread: 2 Guest(s)