Having tried to compile the source myself (unsuccessfully so far though I havent given up) and read a few of the posts in this forum, I\'d like to suggest that tarballs of the CS, CEL etc get included in the CVS once you have finished CB and are working on comprehensive build instructions.
I know that it is preferrable to use current distributions of support code, but building PS involves so many extra libraries that are also under continuing development that it would encourage, I think, more developers to work on PS if they did not have so many problems just trying to get the source compiled.
This would have the added advantage that you could provide a jamfile to compile PS and all support libs within the context of a tested and verified source tree that included both the game\'s source and the libs source.
So far, most of the problems I have come across in getting the source to compile have been related to ensuring that libraries and header files are actually being found and this has been a problem even when I have followed Andrew Craigs nice, clear instructions on how to build the source.
One other problem that I have come across is that Somewhere in the compilation process there is an attempt to include the file leakguard.h and it is simply not there. I susupect that the reason for this is that I am using a different version of CS or CEL than the one in use by the dev team.
That is admittedly a problem that I might have caused for myself by dowloading the released source for each of those libraries, rather than getting the source from their CVS.
Even so, it would be nice to know that I was using source code and librabries that were consistent with the ones in use by the PS dev team, if only because writing and debugging a project like PS is complex enough on its own without facing extraneous bugs such as could be caused by different devs using different versions of the support libs.
