Help compile please.
#11
Okayy..

I've just followed the wiki I linked to you and it worked, I had the last pcsx2-rev603 compiled. Follow the instructions like displayed, it's probable that you will have to log out / log in in order for the modification to be taken into account - I didn't have to for my case I have Vista x64.

Just specify your /bin directory as new environment variable like shown in the Wiki screenshot, save, log out / log in from Windows if necessary, and reopen PCSX2 project and try to recompile it. If you have already a pcsx2.exe in your bin directory you should have the following compilation message :

1>The file cannot be copied onto itself.
1> 0 file(s) copied.
1> 1 file(s) copied.

The "1 file(s) copied." is the one you want, with the rev extension Wink
Core 2 Quad Q9550 @ 3.7Ghz - Geforce GTX 280 1Go OCed @ 640/1400/1200 Mhz - 4Go RAM Corsair Dominator PC2-8500 - Sound Blaster X-Fi Fatal1ty Pro Series - Windows Vista Ultimate x64
Reply

Sponsored links

#12
Just specifying, the revision number only changes if that revision touched a particular file....
If, say, commit 700 is gsdx, and you compil pcsx2, it will NOT be named 700, but 699 or whatever was the last revision where pcsx2 changed...
Reply
#13
(02-25-2009, 10:01 PM)Krakatos Wrote: Just specifying, the revision number only changes if that revision touched a particular file....
If, say, commit 700 is gsdx, and you compil pcsx2, it will NOT be named 700, but 699 or whatever was the last revision where pcsx2 changed...

Oh thanks for the info, I was wondering why sometimes when I compile I didn't have the rev number which I updated my project to. I know why now Smile
Core 2 Quad Q9550 @ 3.7Ghz - Geforce GTX 280 1Go OCed @ 640/1400/1200 Mhz - 4Go RAM Corsair Dominator PC2-8500 - Sound Blaster X-Fi Fatal1ty Pro Series - Windows Vista Ultimate x64
Reply




Users browsing this thread: 1 Guest(s)