Next Generation Emulation banner
1 - 11 of 11 Posts

·
EmuAddict-_-;;
Joined
·
2,831 Posts
Discussion Starter · #1 ·
What software did u used to assemble pcsx2 source? visual c++? borland c? Visual basic? Can anyone tell me? I'll learn it by myself. Just tell me the what software needed. Thanks.
 

·
Registered
Joined
·
12 Posts
My guess would be C++.

I have another question though would it not have been faster and more efective if they used the .net architecture ?
 

·
PCSX2 Coder
Joined
·
10,122 Posts
well i thought the fact it had .vcproj files would be a give away, if you dont know that the you really have no business trying to compile it.
 

·
Registered
Joined
·
128 Posts
It is developed by Visual C++ 7.0 of Visual Studion 2003 and Visual C++ 8.0 of Visual Studio 2005 Beta ; don,t know if they are using Beta 1or 2 version;They are doing the best as illustrated in shots they are post from time to another on pcsx2 site :)
 

·
Registered
Joined
·
78 Posts
I guess the latest source available is the source from last public release, so unless you want to learn/develop.. the source will be useless if you are compiling to get the latest version..
 

·
PCSX2 Coder
Joined
·
10,122 Posts
AbbasJin said:
I guess the latest source available is the source from last public release, so unless you want to learn/develop.. the source will be useless if you are compiling to get the latest version..
the sources are updated daily (near enough) so in theory the CVS is the latest build of 0.8, just dont expect it to be very stable.
 

·
Premium Member
Joined
·
5,309 Posts
If you knew how to compile, it would ;)

This said, given that the CVS build is not supported on this forum these questions are useless.
 

·
Registered
Joined
·
6 Posts
I know it's offtopic but still...

Why there is no official nightly or weekly build?

It's not hard to build it myself, but just that I repeat the work that was already done by someone (betatesters DO have beta :).

Now when I'm intrested in trying out how new changes affected emulation and I try to compile it usualy it doesn't compile. Then I make it to, but usualy notice smth interesting, read the code, try to compile with different settings or on win64 with VS.net and beta1. Usualy smth else pops up (like when you can't find graphics drivers for your notebook and have to make standard ones to work yourself - I hate ATI and NVIDIA for that).
And so the problem is... when I'm ready to test smth it's usualy well past my sleeping time (or it's smth more like 3-4 hours till I have to get up).

And so I have to refrain from testing pcsx2 for almos a month now as don't have the time for the compiling :/

REalm

P.S. Don't be angry :)
 

·
Premium Member
Joined
·
5,309 Posts
There are MANY reasons why no 'daily' / 'weeky' compile is done: In no particular order:

  • The CVS can end up completely broken, where Nothing would work.
  • We have enough people moaning about final builds / reporting bugs, if there where tonnes of builds floating around, imagine the sheer number of people complaing and how hard it would get tracking what bug related to what build.
  • Sometimes there is no work for a couple of weeks
  • CVS sometimes changes super rapidly, and the beta from that morning is now totally irrelivent.
  • We don't need 100's of wannabe beta testers, 'we' need a small dedicated and experienced team.
  • Plugin Specs change frequently, so the plugin authors would have to release matching plugins, this would cause to much confusion, and too much hassle, you'd get piles of mis-matched GSdx betas with miss-matched USB / DEV9 / PCSX2 builds...etc...need not add more confusion!!

etc etc etc...
 

·
wtfbbq
Joined
·
559 Posts
CKemu said:
There are MANY reasons why no 'daily' / 'weeky' compile is done: In no particular order:

  • The CVS can end up completely broken, where Nothing would work.
  • We have enough people moaning about final builds / reporting bugs, if there where tonnes of builds floating around, imagine the sheer number of people complaing and how hard it would get tracking what bug related to what build.
  • Sometimes there is no work for a couple of weeks
  • CVS sometimes changes super rapidly, and the beta from that morning is now totally irrelivent.
  • We don't need 100's of wannabe beta testers, 'we' need a small dedicated and experienced team.
  • Plugin Specs change frequently, so the plugin authors would have to release matching plugins, this would cause to much confusion, and too much hassle, you'd get piles of mis-matched GSdx betas with miss-matched USB / DEV9 / PCSX2 builds...etc...need not add more confusion!!

etc etc etc...
Nuff Said... :hdbash:
 
1 - 11 of 11 Posts
Top