I've trawled the archive and the Wiki for Linux info and while I've got a grounding in whats needed to compile the SDK for Linux, I've still some outstanding questions.
I'm not a Linux guru but have some experience from running a NOC with a bunch of Linux boxes so I'm comfortable in the command-line and compiling stuff where I've not had to make too many config changes. In short, we're using the currently release SDK build, the one that works with AppID 215, etc. and has the VS2005 solution files. I've set-up a Fedora Core 6 box under VMWare Workstation which is up and running and working fine and I've installed versions of GCC, GLIBC and Xerces which I *think* are compatible with the SDK - notes on that here: http://developer.valvesoftware.com/wiki/User:Wunderboy/Sandbox Theres a couple of "generic" questions and a few relating directly to the Makefile so i'll try and keep these brief. 1) Because I'm running Linux under a VM I'm having problems running HLDS due to the NAT/Network issues. Do I need a working copy of HLDS on the build machine for the compile or can I get away without it? Forget testing for now, I just wonder if anything in HLDS is needed to make the compile work. 2) I'm aware theres some diff/patch files floating around to fix a lot of bugs in the SDK. Is there one for the current SDK and a "pure" HL2DM project? 3) How relevant is the known issues list on the Wiki for the current SDK build? Makefile questions... 4) We're using VS2005 for this, but I noticed that default Makefile points to the VS2003 vcproj file. Any issues/problems if I just make this point to the VS2005 one instead? 5) I dont seem to have libgcc_eh.a anywhere on my system - any idea what package it might be in? I think thats it! - Jed _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
