On Thu, Feb 5, 2009 at 11:44 PM, Tim Ansell <[email protected]> wrote: > As I sent in an email to you, we now have a win32 compiled version of > tpserver-cpp. I think we should just distribute it as part of the client > package.
The GP has it on his Windows machine and we're set to test it when we both have a moment. I also still need to get the win32 daneel-ai package ready. I may be able to do both this weekend if the GP is available. Recall that the final package will need to install the XML file for the server. On win32, libtpclient-py looks at the registry key HKLM\Software\Thousand Parsec\SinglePlayer, and adds all values it finds there to the search path for XML files (so that, e.g., tpserver-cpp can install its XML file in its own Program Files directory or whatever). Note that the 'servers' and 'aiclients' subdirectories are still observed on win32. On Unix systems it looks in a standard list of places (see SinglePlayer.py). This information is on the wiki [1]. Distributing tpserver-cpp as part of the client package makes sense. I am considering adding a 'singleplayer' USE flag (default on) to the Gentoo ebuild as well which would pull it in as a dependency. > No libtprl or tpadmin-cpp, but then they are not really needed for the > single player mode right? No, libtpclient-py (and the information in the XML file) handles all configuration of the server automatically. [1] http://thousandparsec.net/wiki/Single_Player#Adding_Single-Player_Support -- Aaron Mavrinac www.mavrinac.com PGP Public Key: http://www.mavrinac.com/pgp.asc _______________________________________________ tp-devel mailing list [email protected] http://www.thousandparsec.net/tp/mailman.php/listinfo/tp-devel
